Adopt CC 2.1.169 — prompt extraction + extractor

[dividedby]

Extracts the 2.1.169 system prompts (data/prompts/prompts-2.1.169.json) and teaches tools/promptExtractor.js to name the 6 new/restructured 2.1.169 prompts and exclude 2 @internal comment blobs. Seeded by fuzzy carry-over from the leaf's own prompts-2.1.168.json (no external source).

Verification

• tools/versionBumpReport.js 2.1.168 2.1.169 --strict: 0 blocking · 0 removed ids · 0 anonymous (exit 0); pnpm test → 323 pass / 5 skip.
• Integration gate (dividedby/tweakcc-maint) Four-zeros against installed 2.1.169: pass: true, bootVerifyPassed: true, empty failedPatches / missingSystemPrompts / orphanVariables, clean Restore drill. Record:

{
  "pass": true,
  "versions": [
    {
      "ccVersion": "2.1.169",
      "fourZeros": {
        "pass": true,
        "failedPatches": [],
        "missingSystemPrompts": [],
        "orphanVariables": [],
        "orphanSource": "boot-verify-fallback",
        "advisoryOrphans": [
          "IS_TRUTHY_FN",
          "PROCESS_OBJECT",
          "CRON_DURABLE_FLAG",
          "CONDITIONAL_WHAT_HAPPENS_NOTE"
        ],
        "bootVerifyPassed": true
      },
      "restoreDrill": { "pass": true, "status": "pass", "backupExists": true, "restored": true, "cleanStock": true }
    }
  ]
}

The gate record was produced with the lobotomized overrides isolated, to validate the patcher on its own terms (see caveat). advisoryOrphans are the Piebald-AI#26 override names — advisory-only, not part of the Four-zeros verdict.

Scope / caveat

This validates the patcher (binary patches + prompt extraction). It does not touch lobotomized-claude-code. That repo's overrides have a pre-existing slot-name drift — references like ${PROMPT_VAR_0} and ${CRON_DURABLE_FLAG} that match neither 2.1.168 nor 2.1.169 (the overrides are pinned at old ccVersions whose prompts were since restructured/renamed). Tracked as dividedby/tweakcc-maint#26, independent of this bump.

Sequencing: the identifierMap-union / skip-unresolved-placeholder detector (PR #4 / dividedby/tweakcc-maint#45) is the runtime guard for exactly that unresolved-placeholder case; recommend landing #4 as well, though these files are disjoint and this PR does not depend on it.

Refs dividedby/tweakcc-maint#58.

[skrabe]

Thanks for this @dividedby — the extractor work is spot-on. I verified it independently: our own extractor flags the exact same 6 gaps this PR fills (3 fuzzy-misses: schedule / communicating-with-user / the non-storybook package adapter, + 3 net-new: code-review Efficiency / operating-autonomously / EnterWorktree) and the same 2 @internal blobs to exclude. The re-pins land on our vocabulary and the schedule identifierMap is byte-identical to ours. The promptExtractor.js changes are adopted as-is.

One finding on the committed JSON, which I've fixed in a commit pushed on top (e335fb9): agent-prompt-worker-fork mis-bound two override placeholders — WORKER_DIRECTIVE (slot1 → should be slot2) and ADDITIONAL_CONTEXT (slot2 → should be slot3). 2.1.169 inserted AGENT_TOOL_NAME at slot1, shifting both down one. Because the override binds by human-name, it would silently resolve to a valid-but-wrong var — no crash, passes smoke + four-zeros; only the mis-bind audit catches it.

Root cause is just that the JSON was generated without TWEAKCC_UPSTREAM_JSON set, so worker-fork kept the .168 carryover map instead of adopting upstream's authoritative slot binding (our fork-only step from 38daf92). Your promptExtractor.js is correct — run through the pipeline with that env var it produces a clean 0-mis-bind JSON, which is exactly what the fix commit regenerated. Heads-up: since your tweakcc-maint lineage doesn't have that adoption step, this same worker-fork mis-bind is probably present there too — worth a regen.

(Note: PR #4's skip-unresolved guard wouldn't have caught this one — it's wrong-but-valid, not an unresolved ${VAR}. Different class.)

Verified after the fix: tools/auditMisbinds.mjs → 0 mis-binds; version-bump report 2.1.168→2.1.169 → 0 blocking / 0 anonymous / 0 UNKNOWN / fresh-extraction-matches-committed; 389 named (no regression, +41 vs Piebald). Merging. 🙏