sujatagunale 817fdedee8 refactor: settle on pre-flight as the one phase name ...

The hyphen purge split the naming. Rule 11 bans hyphenated compounds in
prose, so `pre-flight` survived only where it sat inside backticks: /audit
kept it, while /architect and /test drifted to "startup checks".

pre-flight is not a compound word to be split. It is a named phase, the same
class of token as gap-fill and whole-repo, which the guard already exempts
because other skills match on them. So it joins PARSED_LITERALS rather than
being backticked at 28 call sites, and now reads naturally in prose and in
headings while load-bearing still fails the build.

One line needed real wording rather than a mechanical swap: whole-repo.md
read "pre-flight classified this clearly established" and now reads
"pre-flight classified the repo as clearly established".

Verified: npm test exits 0, zero dashes, zero prose hyphens, and all three
pinned contract blocks (OUTPUT-STYLE, ROOT-FIELD-CONTRACT, TOOL-CONSENT)
stay byte identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-10 09:37:55 +05:30

..

analyze-token-usage.mjs

feat: add token-usage analyzer script and refine architect documentation for clarity

2026-07-09 09:57:42 +05:30

check-portability.mjs

refactor: settle on pre-flight as the one phase name

2026-07-10 09:37:55 +05:30