@henols/c64-re-tools 0.2.3 → 0.2.4

package/bin/cli.mjs

@@ -30,7 +30,9 @@ const PKG_ROOT = dirname(HERE);
 const SKILLS_SRC = join(PKG_ROOT, "skills");
 
 // The single version-resolution seam this repo maintains is
-// `src/mcp/vice/version.ts` (quick-260819-tsz, D-5). This package
+// `src/mcp/vice/version.ts` -- one algorithm for resolving a VERSION
+// template against a published version, kept in exactly one place after
+// this repo once carried several independent copies of it. This package
 // deliberately does NOT import it: it ships without the seam file (its
 // `files[]` is `bin/`, `skills/`, `README.md`) and targets node >= 18, which
 // cannot type-strip the seam's `.ts` the way the vice-mcp package's own
@@ -42,12 +44,13 @@ const SKILLS_SRC = join(PKG_ROOT, "skills");
 // only ever published with a concrete version already stamped in. That
 // number is PRODUCED elsewhere: `scripts/version.mjs stamp` writes the
 // working-tree placeholder, and CI's `npm version` writes the real one at
-// publish time. Do not reimplement D-2's template-resolution rules here.
+// publish time. Do not reimplement the seam's own VERSION-template
+// parsing and prefix-resolution rules here.
 const SELF = readJson(join(PKG_ROOT, "package.json")) ?? {};
 const SELF_VERSION = typeof SELF.version === "string" ? SELF.version : "0.0.0";
 const MCP_PKG = "@henols/vice-mcp";
 // The dev placeholder every derived, publishable version string carries in
-// the working tree (R-2, quick-260819-tsz). Defined authoritatively as
+// the working tree outside a stamped release. Defined authoritatively as
 // `DEV_PLACEHOLDER` in `src/mcp/vice/version.ts` -- repeated here as a
 // literal, NOT imported, because this package deliberately ships without
 // that seam file (see the comment above) and targets node >= 18, which
@@ -57,7 +60,7 @@ const MCP_PKG = "@henols/vice-mcp";
 // so a future edit to the seam's placeholder is not missed.
 const MCP_DEV_PLACEHOLDER = "0.0.0-dev";
 // Wire the project to the exact vice-mcp version this installer was built
-// against -- EXCEPT when run from an unstamped dev checkout (MED-3):
+// against -- EXCEPT when run from an unstamped dev checkout:
 // `installer/package.json`'s dependency pin is the permanent working-tree
 // placeholder outside a CI-stamped publish job, and `@henols/vice-mcp` at
 // that literal version will never exist on the npm registry. Silently

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@henols/c64-re-tools",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Installer that adds the C64 reverse-engineering skills and the VICE emulator MCP server (@henols/vice-mcp) to a project.",
   "type": "module",
   "bin": {
@@ -45,7 +45,7 @@
     "installer"
   ],
   "dependencies": {
-    "@henols/vice-mcp": "0.2.3"
+    "@henols/vice-mcp": "0.2.4"
   },
   "scripts": {
     "sync-skills": "node scripts/sync-skills.mjs",

package/skills/routine-queue-walker/SKILL.md

@@ -89,8 +89,8 @@ line comment. That is the only test; do not guess from the label name.
    list with `anno_get_cross_references` (a generous `max_results` — this is
    also the call that fills in "called from" when the entry is written up in
    Phase 2.2). Every one of these targets is a routine candidate **regardless
-   of whether it carries any label at all**. `docs/phase45-wave0-
-   measurements.md`'s own MEASUREMENT A found that a purely dxa/Ghidra-derived
+   of whether it carries any label at all**. A real measured derivation run
+   (dxa disassemble, then Ghidra import) found that a purely dxa/Ghidra-derived
    store carries ZERO labels of any shape — derivation writes typed ranges and
    cross-references, never names — so a queue built only from Candidate source
    B below finds nothing to do on such a store and silently reports a clean,
@@ -160,7 +160,7 @@ OS variable).
    per that data type's own schema distinction), OR referenced from a code
    range while NOT itself sitting inside one. Every one of these is a symbol
    candidate **regardless of whether it carries any label at all**.
-   `docs/phase45-wave0-measurements.md`'s own MEASUREMENT A found that a
+   The same measured derivation run found that a
    purely dxa/Ghidra-derived store carries ZERO labels of any shape, so
    Candidate source B below finds nothing to do on such a store and silently
    reports a clean, empty queue on a program nothing has been named in yet.

package/skills/routine-queue-walker/scripts/completeness-report.mjs

@@ -75,13 +75,15 @@ export class MissingDisagreementInputError extends Error {
 
 /**
  * The frozen survivor prefix set, MIRRORED from
- * `src/mcp/vice/anno-cli.ts`'s own frozen set -- see
- * docs/phase45-wave0-measurements.md for the MEASURED label population this
- * was frozen against. Exported here, separately from the verb's own copy,
- * because this script's own tests must be able to assert on the predicate in
- * isolation, without a live store or a subprocess -- and because this
- * script's own header forbids it from reading a store directly, so it
- * cannot import the verb's copy through anything but a duplicate literal.
+ * `src/mcp/vice/anno-cli.ts`'s own frozen set -- frozen from a real
+ * derivation run (dxa disassemble, then Ghidra import) that measured ZERO
+ * labels written by import alone, confirming the eleven prefixes had
+ * nothing populated to positively test against rather than contradicting
+ * them. Exported here, separately from the verb's own copy, because this
+ * script's own tests must be able to assert on the predicate in isolation,
+ * without a live store or a subprocess -- and because this script's own
+ * header forbids it from reading a store directly, so it cannot import the
+ * verb's copy through anything but a duplicate literal.
  *
  * WHAT NOT TO DO: if the frozen set in `anno-cli.ts` ever changes, this copy
  * moves in the SAME commit, or the two renderers silently disagree about