chore(forgeplan): reconcile markdown status + tidy pre-release worktree - #171
Merged
Merged
Conversation
Bring the .forgeplan markdown in sync with the index and clear the working-tree clutter left after the Pillar-B/C + iso arcs. - Fix markdown<->index desync (RED LINE #4): PRD-038 + RFC-035 were activated in the Lance index during the Pillar C (#169) close-out but their status never landed in the committed markdown, so a scan-import would silently revert them to draft. Restore status: active + the session's score/link updates on the Pillar-B/C evidence chain. - Commit EVID-098 (RFC-035 chat-panel-v2 verification) — it was never captured by any prior commit. - Add the three reference docs (CLAUDE-PLUGINS, MAP-PACK v0.2.0 findings, proactive hints rules). - gitignore transient forgeplan/local paths (anomalies-journal.jsonl, map/.work/, .local/). - Remove stray scratch (pnpm-lock.yaml — project is npm; plus dev-run yml/md droppings). No source/behaviour change; markdown is now the durable source of truth (ADR-003) that matches the derived index. Refs: PRD-038 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 tasks
explosivebit
added a commit
that referenced
this pull request
Jul 9, 2026
…oarding, 3D-iso) (#172) ## Summary Release **v0.3.0** (MINOR) — cuts the entire IDEF0 composed-map program from `develop` to `main`. 152 commits since `v0.2.4`, no breaking changes. Headline features landed since v0.2.4: - **Composed-map (T4)** — the 9th "Map" graph view: curated zoned composition with render-proof against the `forgeplan.map/v1` contract (PRD-036 / SPEC-006 / RFC-030). - **Recursive drill-down** — descend/climb/breadcrumb into zones, prefer map-pack-emitted per-zone layers with client-derived fallback (PRD-037 / RFC-031). - **Onboarding tour (Pillar B)** — `/onboard` route + deterministic zone-walk camera tour (#167). - **Live local-agent guide (Pillar C)** — daemon + Agent SDK + two-tier chat (Tier-0 map-grounded, Tier-1 live), floatable/dockable chat panel v2 (#169, PRD-038 / RFC-034 / RFC-035 / ADR-010). - **3D isometric Map-corner minimap** — Threlte v8 lazy chunk, bidirectional 3D↔2D drill sync, dist cap raised 3→3.5 MiB (#170, PRD-039 / RFC-036 / ADR-011). ## Version bump - `package.json` + `template/package.json`: `0.2.4` → `0.3.0`. ## Release checklist - [x] Version bumped in both package manifests - [ ] CI matrix (ubuntu / macos / windows) green on this PR - [ ] Merge to `main` (merge commit) - [ ] Annotated tag `v0.3.0` on `main` + push - [ ] GitHub Release published (fires `release.yml` → npm with provenance) - [ ] Back-merge `release/v0.3.0` → `develop` ## Test plan Full CI matrix on this PR must pass. No new code beyond the version bump; all feature work was already CI-verified on `develop` (each of #167/#169/#170/#171 merged green). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pre-release housekeeping on
develop— no source or runtime behaviour change.PRD-038+RFC-035wereactivated in the Lance index during the Pillar C (feat(idef0): Pillar C — live onboarding agent (daemon + Agent SDK + camera chat) #169) close-out, but their
status: activenever landed in the committed markdown. Aforgeplan scan-importon develop would have silently reverted them todraftand"unactivated" the Pillar C chain. Restored
status: active(+ the session'sscore/link updates on the Pillar-B/C evidence chain). Verified: after
scan-import, both stayactive.EVID-098(RFC-035 chat-panel-v2 verification) — it existed onlyin the working tree, captured by no prior commit.
docs/CLAUDE-PLUGINS.md,docs/MAP-PACK-v0.2.0-FINDINGS.md,docs/hints-rules.md..forgeplan/anomalies-journal.jsonl,.forgeplan/map/.work/,.local/.pnpm-lock.yaml(project is npm —package-lock.jsonis the lockfile) + dev-run
*.yml/*.mddroppings.Why
Bring
developto a clean, durable state before cutting thev0.3.0releasebranch. The markdown is the source of truth (ADR-003); it must match the derived
index so a fresh clone +
scan-importreproduces the activated Pillar C chain.Test plan
forgeplan scan-import→PRD-038+RFC-035remain active (desync cured).template/source touched → existing CI (svelte-check + vitest + buildmatrix) unaffected; this is a docs/metadata-only change.
git diff --cachedverified: no scratch, no gitignored paths, no screenshots staged.Refs: PRD-038
🤖 Generated with Claude Code