@oscaner-skills/cdd-engine 4.5.0 → 4.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -270,8 +270,13 @@ export const reviewGuideOf = (key) => {
270
270
  /** The spec-shaped documents' narrative criteria body — the phase-spec line's URC
271
271
  * + its program-conformance clause, the ONE body both spec-shaped target rows
272
272
  * select (the filled rubric is what differs per row). The charter's own criteria
273
- * body is `docCharterAxes` — never a second narrative copy alongside this one. */
274
- const docNarrativeAxes = (guide) => `Follow URC: single-cycle, lens-tagged findings (completeness/consistency/clarity) + the writing-plans self-check + verification evidence — the reviewer runs the repository's typecheck and test commands and self-reports the dual evidence + Claimed→pin: every behavior claim (usage-line attribution · semantic contract · byte face) must cite a colocated pin (path:line + the assertion face) — the review checks every claim against its pin, claim by claim; a pinless claim is a lens-tagged finding + program conformance — judge the phase against its parent overall at \`INPUT_OVERALL\` (the charter its \`program:\` names): the phase must sit inside the scope the overall's Phase inventory registered for it, and a phase that reaches beyond it is a completeness finding. ${guide}`;
273
+ * body is `docCharterAxes` — never a second narrative copy alongside this one.
274
+ * The `Claimed→pin` clause names the three claim SHAPES a spec may state (a symbol,
275
+ * a guarded count, a condition that must hold) instead of accepting whatever shape
276
+ * today's tree happens to have: a line number is not a pin, a prose count is the
277
+ * guard's business, and a present-tense description of today's shape belongs to the
278
+ * plan. Nothing gates the writing moment — the review is where a violation surfaces. */
279
+ const docNarrativeAxes = (guide) => `Follow URC: single-cycle, lens-tagged findings (completeness/consistency/clarity) + the writing-plans self-check + verification evidence — the reviewer runs the repository's typecheck and test commands and self-reports the dual evidence + Claimed→pin: every behavior claim (usage-line attribution · semantic contract · byte face) must cite a colocated pin by module path + symbol name — a line number is not a pin; a count ("N places" · "N rows" · "N modules") must be stated as pinned by the named guard or test; a present-tense description of today's shape belongs to the plan — in a design spec a measurement input is a lens-tagged finding unless restated as a condition that must hold — the review checks every claim against its pin, claim by claim; a pinless claim is a lens-tagged finding + program conformance — judge the phase against its parent overall at \`INPUT_OVERALL\` (the charter its \`program:\` names): the phase must sit inside the scope the overall's Phase inventory registered for it, and a phase that reaches beyond it is a completeness finding. ${guide}`;
275
280
  /** The charter's criteria body — the six things a program charter owns, and only
276
281
  * those. It carries none of the implementation-face evidence duty the narrative
277
282
  * body carries (running the repository's commands, pinning every claim): a charter
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@oscaner-skills/cdd-engine",
3
- "version": "4.5.0",
3
+ "version": "4.6.0",
4
4
  "description": "CDD engine CLIs: task runner, docs reviewer, branch reviewer, harness selector.",
5
5
  "type": "module",
6
6
  "engines": {