Code reference detail
validate-showcase-rq.mts
site/scripts/validate-showcase-rq.mts
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| accurate_rq_snippets_must_parse | done | Every site snippet that demonstrates accurate reqlan must parse against the Langium grammar. In scope: language- " rq " blocks ( landing syntax pairs, the example slice, the hero snippet, showcase `.rq` blocks ). Out of scope: ts / md / py snippets that only show `rq:` comment links. Invalid-on-purpose samples must not be labelled language- " rq ". Enforced by tests plus the content parse gate in ["../../site/scripts/validate-showcase-rq.mts"]. Showcases are a subset per [every_rq_block_must_parse] / [phase_1_parse_gate]. | 0.090 | |
| site | the / site folder contains a static Next. js App Router landing page for reqlan. should align with [brand] Copy modules: [copy] Document head: [meta_tags] | 0.040 | ||
| story_codebase_showcase | done | story, traceability, delivery | Flagship. A story that ships with the code. Write the feature as one idea. Bind source with @ implementation. Bind proof with @ tests. Point back with rq: comments. Click on that name returns the bound files — not a ticket outside the repo. Domain: product delivery. One worked name across every block per [one_worked_example_per_page]. Payoff is click output per [every_showcase_ends_in_a_payoff] and ["../cli/click.rq".click]. Uses [development_core.code_comment_references] and [development_core.testing]. Demonstrates [sub_file_binding] and [bidirectional_comment_links]. | 0.046 |
Reference labels
"../../site/scripts/validate-showcase-rq.mts", ../../site/scripts/validate-showcase-rq.mts