chore: introspect-v2 migration incomplete on `development` — 28 deprecated docs/introspections records + write-target contradiction (needs operator)

[domattioli]

Problem

introspect-v2 (DomI #296) migrates session introspections from the repo-local docs/introspections/ to DomI's central corpus .introspect/CHILmesh/. PR #212 deleted docs/introspections/ on main and archived 32 CHILmesh records upstream. The migration is incomplete, in two compounding ways:

1. development still carries 28 deprecated records that main deleted. Merging the rolling development → main PR (chore: rolling development → main (DomI pin a9b240f + docstring dedup) #213) would re-add them to main. They are already archived in DomI .introspect/CHILmesh/ (32 records), so this is the "v2 follow-up sweep" PR chore: migrate introspections to DomI central corpus (.introspect/) #212 explicitly deferred.

2. main itself re-grew 5 records (development_2b6923e, 83f6229, ae77ee1, f06a0ad, fef9cf9) — created on development after chore: migrate introspections to DomI central corpus (.introspect/) #212 and carried into main by rolling PR chore: spec-010 v3 — DomI-managed workflow copies, label-sync dedup #210. So the dir is still actively written to.

Root cause — write-target contradiction

The reason it keeps re-growing: sessions still write introspections to docs/introspections/ because:

• DomI CLAUDE.md (authority) says introspections go to .introspect/<RepoName>/ (central corpus) — but that path lives in the DomI repo.
• CHILmesh is a pull-only consumer (DomI sync contract: "DomI never edits downstream; downstream never edits DomI").
• The rotation invariant is one repo per session, no cross-repo writes (only the DomI slot edits DomI).
• The overhaul rotation instructions say "introspection → own repo corpus" — which for CHILmesh can only mean docs/introspections/.

So a CHILmesh routine session has no compliant way to write to DomI's .introspect/CHILmesh/, and falls back to the deprecated dir. The migration cannot complete from autonomous CHILmesh sessions alone.

What's needed (operator / DomI-governance decision)

1. Decide the durable write path for downstream-repo introspections under introspect-v2 (e.g. a DomI-side collector workflow that ingests from a downstream surface, or an explicit "downstream repos keep a local corpus" carve-out). Until decided, downstream sessions keep regrowing the deprecated dir.
2. Sweep development: delete the 28 deprecated docs/introspections/* (and .planning/introspections/) once confirmed all are archived upstream, so chore: rolling development → main (DomI pin a9b240f + docstring dedup) #213 doesn't re-add them to main.
3. Update CHILmesh CLAUDE.md + the rotation instructions to state the agreed write path unambiguously.

Filed by the hour-18 CHILmesh rotation session (maintenance track). Not auto-reconciled — CLAUDE.md warns against autonomous bulk reconciliation, and item 1 is a governance decision, not a code fix.

[repo: CHILmesh · session: 2026-06-15T18Z-rotation · refs: DomI#296, #212, #210, #213]

[domattioli]

development swept — operator-directed (this session)

Operator directly instructed this session that introspections "should not be written to chilmesh at all" and flagged them in docs/. Done on development (9952f6e, rides rolling PR #227 → deletes from main on merge):

• Removed docs/introspections/ (6 records). This is the #296 item-7 "CHILmesh dev-residue" sweep that the main-based migration PR chore: migrate introspections to DomI central corpus (.introspect/) #212 deferred. 4/6 were already archived in DomI .introspect/CHILmesh/; the 2 unarchived (development_2b6923e, development_c7a581c, both 2026-06-15, postdate the chore: migrate introspections to DomI central corpus (.introspect/) #212 archive snapshot) remain recoverable from CHILmesh git history.
• Removed docs/superpowers/ (2 docs). Separate leak — DomI superpowers plan+spec copied in by feat: adopt DomI release-integrity skill + drop bespoke gate [BLOCKED on DomI#313] #226 (release-integrity adoption), not introspect-related; same de-vendor class.
• .gitignore guard added for docs/introspections/ + .introspect/ so a session that still follows the stale routine-doc directive can't re-commit them here.

Root cause is upstream, and narrower than this issue framed it

The recurrence engine is not (only) the deposit-mechanism gap — it's a doc drift in DomI: introspect SKILL.md flipped to the central .introspect/<repo>/ corpus (introspect-v2, #296 item 1), but DomI/.claude/claude_routine_instructions.md was never updated — it still directs docs/introspections/<session_id>.md at L382, L383, L401. Consumer routine sessions read that doc (via the DomI raw URL) and, on the manual-fallback path, write the corpus right back into docs/introspections/. CHILmesh carries a stale tracked copy of the same doc. So even after the skill flip + the #212 main sweep, the dir kept re-growing.

Filed upstream as a DomI bug (link below). The two still-open governance items remain DomI-side and unblocked by this sweep:

1. #296 item 2 — the consumer→DomI corpus deposit mechanism (operator/architecture call).
2. Update the routine doc + any CHILmesh-local copy to the v2 path once (1) is decided.

Leaving this open pending the upstream doc fix + deposit decision.

[model: claude-opus-4-8, repo: CHILmesh, session: 2026-06-24T18Z-rotation, refs: #296, #212, #226, DomI routine-doc drift]

---

Generated by Claude Code