Skip to content

chore(forgeplan): reconcile duplicate EVID IDs to EVID-007/008#15

Merged
explosivebit merged 1 commit into
developfrom
chore/forgeplan-reconcile-after-v0.1.5
May 4, 2026
Merged

chore(forgeplan): reconcile duplicate EVID IDs to EVID-007/008#15
explosivebit merged 1 commit into
developfrom
chore/forgeplan-reconcile-after-v0.1.5

Conversation

@explosivebit
Copy link
Copy Markdown
Contributor

Two ID collisions on disk after merging parallel sessions. forgeplan reindex was silently shadowing 6 of 14 markdown files. Renumbered the user-side dupes to next free IDs preserving links. After this 14 artifacts in index, all links restored, health blind_spots and orphans empty. Refs PRD-001.

…EVID-007/008)

Two ID collisions sat on disk after merging two parallel sessions: EVID-004 had both my claude-md-baseline file and the smoke-update file, EVID-005 had the rule-12-adr-002-protocol file and my safety-hardening file. forgeplan reindex silently took whichever the projection iterator hit first, so the index showed 8 artifacts while the markdown tree had 11 (plus ADR-002, RFC-002, RFC-003, EVID-006 that were also missing because the prior reindex never picked them up).

Rename strategy: my EVID-004 and EVID-005 are already linked into PRD-001 with R_eff = 1.00 — touch them and links break. Renumber the user-side dupes to the next free IDs: smoke-update → EVID-007, rule-12-adr-002-protocol → EVID-008. Frontmatter id: + body heading updated together so the file is internally consistent. State sidecar EVID-005.yaml renamed to EVID-008.yaml.

After this commit and a forgeplan reindex run: 14 artifacts in the index, every markdown file on disk has exactly one row in forgeplan list, four typed links restored (EVID-006 informs RFC-003, EVID-007 informs RFC-002, EVID-008 informs ADR-002, plus existing EVID-001..005 links). Health: blind_spots and orphans both empty.

Refs: PRD-001
@explosivebit explosivebit merged commit 40358b6 into develop May 4, 2026
3 checks passed
@explosivebit explosivebit deleted the chore/forgeplan-reconcile-after-v0.1.5 branch May 4, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant