You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f08fd11
Browse filesBrowse the repository at this point in the historyBrowse files
chore(cli): make the reference standalone, not a demo artifact
Follows the subpath rename through the code. The `sg` and `vale` entries
are reference material too -- they are simply not what the demo command
writes -- so scoping the corpus to "demo" was wrong in the same way the
published name was.
Moves, by what each file is actually about rather than by where it started:
src/rules/demo/reference.ts -> src/rules/reference.ts
src/rules/demo/constraints.ts -> src/rules/constraints.ts
The constraints move furthest and had the least business being there:
they describe what `verify` and `test` enforce on ANY rule. Nothing about
them is demonstration-specific, and filing them under `demo/` implied a
scope they never had.
`src/rules/demo/` keeps `manifest.ts` and `rule.ts`, which really are the
rules the demo command writes.
Identifiers follow: buildDemoReference -> buildReference, DemoReference ->
Reference, DEMO_REFERENCE_* -> REFERENCE_*. Script and task follow too:
`write-demo-reference.ts` -> `write-reference.ts`, and `demo:reference` ->
`reference`. Tests renamed to match the modules they cover.
`demo:manifests` and `print-demo-manifests.ts` keep the prefix, and that is
the line: they exist so CI can stage what the demo command writes, which is
genuinely about the demo.
No behaviour change. The payload is byte-identical -- regenerated after the
move and it matched -- and the asset guard was re-broken to confirm it
still refuses a mis-declared export under the new path.
* disagreement about our validator. Any consumer would have hit it on their
45
45
* first run.
46
46
*/
47
-
exportconstDEMO_REFERENCE_PROTOCOL=[
47
+
exportconstREFERENCE_PROTOCOL=[
48
48
"Generate a rule from `prompt`, using your own pipeline.",
49
49
"Run `taskless verify` over what you generated. It enforces constraints beyond the engine's own schema, listed in `constraints` below, so a rule the engine executes correctly can still be refused. A rule that fails here is not deliverable however well it behaves, and every later step would be measuring the wrong thing. Check `enforcedBy` before concluding anything: some constraints are only decided once the fixtures run.",
50
50
"Run your generated rule against your own cases. It should pass; if it does not, the disagreement is inside your pipeline and nothing below will be informative.",
0 commit comments