DreamGraph v12.4.0 - Hippodamus

DreamGraph v12.4.0 - Hippodamus

DreamGraph v12.4.0 keeps the v12 major release title as Hippodamus and aligns every release-bearing surface on the current v12 line.

Highlights

• Token economy and preamble compiler for the new architect when using native api adapters.
• EXPERIMENTAL Architect CLI. Not recommended for serious work just yet.
• Native API tool loop continuity and report fixes on the web architect.
• Bumped the daemon, MCP server, dashboard, CLI, Explorer, VS Code extension, root package, workspace packages, generated lockfiles, documentation, guide references, and README release surface to 12.4.0 / v12.4.0.
• Preserved the major-line title rule: the v12 release line remains Hippodamus, so this release is titled v12.4.0 - Hippodamus.
• Refreshed the root README and release-note index so users see the current release first.
• Kept the release pass bound to the authoritative seven-stage release_workflow; the release is complete only after version alignment, documentation refresh, artifact packaging, release notes, commit/tag/push, GitHub release publication, and website update each have completion evidence.

Release-Bearing Surfaces

• Root daemon/package manifest and package lock
• MCP client/version strings used by CLI calls
• dg CLI visible version output
• Explorer dashboard package manifest and lockfile
• VS Code extension package manifest and lockfile
• Workspace packages: @dreamgraph/host, @dreamgraph/sdk, and @dreamgraph/token-economy
• Root README, release-note index, and guide-facing release documentation

Verification

• npm run build:server
• npm run build
• Release artifact packaging for root package, workspace packages, and VS Code extension

Operational Notes

This release should be published from the v12.4.0 git tag with the GitHub release title DreamGraph v12.4.0 - Hippodamus. Website release content must use the same title and link to the published tag.

v12.3.0

DreamGraph v12.3.0 - Strict Policy Inheritance and Release Discipline

DreamGraph v12.3.0 fixes the ENVOY-reproduced normalization drift where an instance configured as strict could still normalize in non-strict mode, report a mixed receipt, and convert weak rejected dreams into durable tension inventory.

Highlights

• Normalization now inherits the active instance policy by default unless a caller explicitly overrides strictness.
• Effective-policy receipts now report the strictness and runtime thresholds that were actually applied, including bootstrap-adjusted promotion gates.
• Weak insufficient-evidence rejected dreams no longer auto-create persistent weak_connection tensions by default.
• Automatic dream-cycle and scheduler-triggered normalization now share the same governed strictness resolution and rejected-dream tension gating.
• The release pass remains bound to the authoritative seven-stage release_workflow; v12.3.0 is not considered released until version alignment, documentation refresh, artifact packaging, release notes, commit/tag/push, GitHub release publication, and website update each have real completion evidence.

Runtime and Verification Impact

• Active-profile strictness is now the default normalization mode across tool, scheduler, and dream-cycle paths.
• Receipts distinguish requested override state from the effective gates actually enforced at runtime.
• Rejected-dream handling now separates low-signal insufficient evidence from truly interesting contradiction or recurrence signals.

Verification

• npx vitest run tests/cognitive-producers.test.ts
• npm run build

Operational Notes

Stages 1 through 4 of the governed release workflow are repository-local and can be evidenced from this repo. Stages 5 through 7 require authoritative completion evidence from source control publication, GitHub release creation, and the related ../dreamgraph-website/ repository before v12.3.0 can be truthfully marked released.

DreamGraph v12.2.0

DreamGraph v12.2.0 - Trust Calibration and Reviewable Cognition

DreamGraph v12.2.0 sharpens the standalone Architect and cognitive projection surfaces around trust calibration, reviewability, provenance, lifecycle visibility, and bounded creativeness.

Highlights

• Added a shared cognitive trust-state contract for accepted facts, validated insights, advisory candidates, latent/speculative links, rejected links, expired artifacts, and human-reviewed decisions.
• Added evidence-ledger projections for dream playback candidates and promoted edges, grouped by source class with semantic anchors first.
• Added precision categories for tension clustering: duplicate edge, insufficient evidence, missing fact-graph entity, stale/expired artifact, and actionable architecture gap.
• Added lifecycle transition projections for superseded futures, retired/resolved/expired tensions, and expired insight or narrative-style cognitive artifacts.
• Added a repeatable Architect calibration evaluation endpoint at GET /api/architect/v1/calibration/evaluation.
• Updated product vocabulary to position DreamGraph as a governed architecture cognition layer rather than a generic memory product.

Architect API Additions

• GET /api/architect/v1/lifecycle returns lifecycle transition chains with prior state, new state, timestamp/source, authority, triggering evidence, superseding artifact, and remaining uncertainty.
• GET /api/architect/v1/calibration/evaluation reports trust-state distribution, evidence completeness, stale/expired artifact rate, uncertainty labeling, lifecycle explainability, operator review outcomes, and speculative reviewability.

Verification

• npx vitest run tests/architect-pulse.test.ts tests/living-dreamgraph-projections.test.ts
• npm run build:server
• npm run build:explorer

Rejected, retired, expired, and superseded artifacts remain inspectable historical context. Dream output remains advisory until backed by source, tests, ADRs, governed workflow evidence, daemon validation, or explicit human review.

DreamGraph v12.1.0 - Living DreamGraph

DreamGraph v12.1.0 - Living DreamGraph

v12.1.0 Living DreamGraph makes the standalone browser architect more visibly connected to the daemon's cognitive state while preserving governed DreamGraph MCP authority for repository facts and mutations.

Highlights

• Added Architect Pulse with cognitive weather, readiness, unresolved-tension pressure, active-plan state, and an explicit dreamgraph_mcp authority boundary.
• Added read-only dream playback projection over existing cognitive stores, including cycle frames, grouped rejection reasons, promoted edges, and tension deltas.
• Added read-only tension clustering to distinguish duplicate-edge pressure, UI registry pressure, derived-hub pressure, evidence gaps, and source-defect candidates.
• Added the daemon-governed Architect desire ledger for ranked explanatory goals without mutation authority.
• Extended living plan state and standalone architect routes for pulse, playback, clusters, desires, and plan projections.

Verification

• npm test
• npm run build
• git diff --check

Distribution Artifacts

• dreamgraph-12.1.0.tgz
• dreamgraph-sdk-12.1.0.tgz
• dreamgraph-host-12.1.0.tgz
• dreamgraph-vscode-12.1.0.vsix

Release Operations

• v12.1.0 git tag on the release commit
• GitHub release titled DreamGraph v12.1.0 - Living DreamGraph

DreamGraph v12.0.0 - Hippodamus

DreamGraph v12.0.0 - Hippodamus

v12.0.0 Hippodamus marks the standalone browser-based architect as beta and aligns the first-party DreamGraph release line to 12.0.0. From this release onward, architect refers to the standalone browser surface; the editor-integrated chat surface is the VS Code architect.

Release focus: architect beta

Architect beta is the daemon-served browser surface for project-bound DreamGraph work. It brings the core Architect workflow out of the editor while keeping DreamGraph daemon authority intact:

• Project chat grounded in DreamGraph MCP tools, graph facts, ADRs, workflows, data models, UI registry entries, and source evidence.
• Selected-plan chat with explicit scope, so plan-bound work does not depend on hidden conversation state.
• Runtime provenance that shows adapter, provider, model, route, autonomy state, pass state, and session identity.
• Auditable tool traces for DreamGraph MCP calls, command verification, source inspection, graph reads, graph mutations, and release work.
• Browser-first access to the same governed source, graph, ADR, documentation, and release workflows used by the rest of DreamGraph.

The beta label is intentional. The browser shell is now positioned as the primary standalone Architect surface, but layout, controls, and some long-running workflow ergonomics will continue to harden across the v12 line.

Naming change

• architect: standalone browser-based Architect beta.
• VS Code architect: Architect chat inside the VS Code extension.
• Historical references to "Standalone Architect" describe the same beta surface now called architect.

Version alignment

This release aligns the first-party versioned surfaces to 12.0.0:

• dreamgraph
• @dreamgraph/sdk
• @dreamgraph/host
• dreamgraph-explorer
• dreamgraph-vscode
• root and nested lockfiles
• runtime/client version strings used by the VS Code architect integration
• user guide, installation docs, root README, architecture docs, extension README, and release-note index

Documentation

• Added guide/15-architect-beta.md, a comprehensive user guide for the standalone architect beta.
• Updated guide/README.md to include architect beta in the recommended reading path and daily-use surface model.
• Updated the VS Code extension guide to consistently call the editor-integrated chat the VS Code architect.
• Updated the root README to introduce the v12 architect beta as the release headline.
• Updated installation and troubleshooting examples for dreamgraph-vscode-12.0.0.vsix.

Release artifacts

Expected local distribution artifacts for this release:

• dreamgraph-12.0.0.tgz
• dreamgraph-sdk-12.0.0.tgz
• dreamgraph-host-12.0.0.tgz
• dreamgraph-vscode-12.0.0.vsix

Upgrade notes

After installing v12.0.0:

1. Restart running DreamGraph daemons so the v12 runtime and daemon-served architect beta are active.
2. Reload VS Code windows so the v12 VS Code architect and extension metadata are in memory.
3. Use dg status <instance> to confirm daemon version and HTTP endpoint.
4. Open architect from the daemon-served browser surface and verify the instance, project, scope, and runtime route shown in the UI.

Verification

Release verification should include:

• root TypeScript/build verification
• Explorer build
• VS Code extension build/package verification
• package artifact creation for root, SDK, host, and VS Code extension
• v12.0.0 git tag on the release commit
• GitHub release titled DreamGraph v12.0.0 - Hippodamus

DreamGraph v11.0.1

DreamGraph v11.0.1 Release Notes

DreamGraph v11.0.1 is a maintenance refresh of the v11.0.0 release artifacts.

Fixes

• Refreshes the v11.0.0 release after merge cleanup so packaged artifacts build cleanly from the released source.
• Resolves merge-fallout in the Adaptive Futures Engine integration, including conflict-marker cleanup and duplicate Task Preamble declarations that could block TypeScript builds and installer refreshes.

Additions included in refreshed artifacts

• Includes the scheduler keywords / toolgroups addition so the VS Code extension and tool routing metadata match the intended v11 release surface.

Compatibility

• No intentional breaking changes from v11.0.0.
• Recommended for all v11.0.0 users.

DreamGraph v11.0.0 - Adaptive Future Engine

DreamGraph v11.0.0 — Adaptive Future Engine

Release date: 2026-05-26

v11.0.0 ships the Adaptive Future Engine release line. This release promotes candidate-future ranking, bounded future-fit scoring, and compact audit trails from the v11 plan into the released DreamGraph distribution.

Headline Changes

1. Adaptive Future Engine

• Adds the shared Adaptive Future scaffold in src/cognitive/adaptive-future-scaffold.ts.
• Classifies planning-doc, adapter, graph-tool, and cognitive-workflow task classes.
• Records selected and rejected candidate IDs, score factors, evidence anchors, objections, route/fallback provenance, and validation failures as compact audit metadata.
• Keeps all Adaptive Future output advisory and subordinate to accepted ADRs, workflows, API surface, data-model contracts, graph evidence, and explicit user intent.

2. Runtime Consumers

• enrich_parser_nodes now emits Adaptive Future audit metadata for graph-tool enrichment work.
• solidify_cognitive_insight now carries Adaptive Future audit metadata through cognitive-workflow planning metadata.
• Focused tests cover the scaffold, graph-tool audit consumer, and cognitive-workflow audit consumer.

3. Documentation And Release Alignment

• Adds dedicated Adaptive Future Engine documentation in docs/adaptive-future-engine.md.
• Adds a user-guide page in guide/14-adaptive-future-engine.md.
• Updates package versions, SDK docs, install guide references, VS Code extension metadata, root docs, and release notes to the v11.0.0 release line.

Upgrade Notes

• No instance migration is required for v11.0.0.
• Existing deterministic behavior remains available; Adaptive Future metadata is advisory context, not a hard enforcement mechanism.
• Consumers that do not inspect adaptive_future_audit continue to behave as before.

Artifacts

Expected release artifacts:

• dreamgraph-11.0.0.tgz
• dreamgraph-sdk-11.0.0.tgz
• dreamgraph-host-11.0.0.tgz
• dreamgraph-vscode-11.0.0.vsix

Verification

Release verification for this cut should include:

• focused Adaptive Future tests;
• full npm test where practical;
• npm run build;
• package artifact creation with npm pack for root, SDK, and host packages;
• VS Code extension packaging with npm --prefix extensions/vscode run package.

DreamGraph v10.6.0

DreamGraph v10.6.0 — Renata

v10.6.0 continues the Renata line. It introduces the Codex CLI native architect adapter (beta) alongside continued Copilot CLI maturation, and aligns the CLI, daemon, VS Code extension, dashboard, Explorer, SDK, host package, root documentation, docs, and user guide to one published version line.

No breaking changes are intended for existing v10.x installations.

---

Headline changes

1. Codex CLI native architect adapter (beta) — use your ChatGPT subscription

DreamGraph now ships a native Codex CLI adapter for the VS Code Architect. If you already pay for ChatGPT Plus, Pro, or Team, you can now lift that same OpenAI subscription into DreamGraph — no separate OpenAI API key required — and use GPT-class models as a first-class, graph-grounded architect.

This is the feature hundreds of you have been asking for. It is now real.

What you get:

• OAuth via your existing ChatGPT account. Codex CLI authenticates with your ChatGPT subscription. DreamGraph reuses that login. No API billing setup, no separate key management.
• Native Architect adapter, not a wrapper. Codex CLI runs inside the same fail-closed Architect contract as Copilot CLI: DreamGraph MCP is authoritative, every tool call is audited, and transcript-only "phantom" tool claims are rejected.
• Inheritance-proxy MCP bridge. Codex CLI shares the Architect's live DreamGraph session and authoritative tool registry, with an isolated config.toml and read-only sandboxing per run.
• Graph-grounded reasoning. The same bounded context, ADR awareness, workflow grounding, and audit reconciliation that powers the Copilot CLI path is applied to Codex CLI runs.
• Live tool progress. Codex CLI tool activity is streamed from the shared audit NDJSON, not from provider stdout — so what you see is what actually ran.
• Honest diagnostics. Specific failure classes (CODEX_MODEL_UNSUPPORTED, usage-limit, policy-denied, not-logged-in) are classified separately and surfaced cleanly instead of being collapsed into a single opaque error.

Status: beta. The architecture, audit boundary, and fail-closed contract are production-grade and match the Copilot CLI adapter. The "beta" label reflects ongoing hardening against Codex CLI provider/runtime drift (model availability, stderr/event shape changes). It works today. Expect continued polish in v10.7.x.

Pairs perfectly with Copilot CLI. Many teams will want both adapters available: Copilot CLI for your GitHub Copilot account, Codex CLI for your ChatGPT account. Switch providers per run, keep the same graph, keep the same audit guarantees.

2. Copilot CLI architect adapter — per-turn diff view

The Copilot CLI adapter (released in v10.5.0) gains a per-turn diff view: after each Architect turn, you can see exactly what files Copilot CLI changed and how, as a normal diff. Per-tool-call diff granularity is postponed to a later release.

This continues the v10.5.0 hardening line (DreamGraph MCP authority, inheritance-proxy bridge, audited dreamgraph:run_command routing, idle-output timeout, cause-specific cancellation and retry-success verification).

3. Version and documentation alignment

This release aligns all first-party versioned surfaces to 10.6.0:

• Root daemon/CLI package and package lock.
• @dreamgraph/sdk and @dreamgraph/host workspace packages.
• Explorer package and package lock.
• VS Code extension package, package lock, runtime MCP client identity, activation-version marker, and extension README.
• CLI version output and MCP client identity (dg.ts, mcp-call.ts).
• Root README, architecture docs, SDK docs, plugin guide/reference, and user-guide install examples.

---

Upgrade notes

• Node 20+ remains required.
• Re-run the installer (scripts/install.ps1 -Force or bash scripts/install.sh --force) after pulling this release.
• Reload VS Code after installing dreamgraph-vscode-10.6.0.vsix.
• Restart running DreamGraph daemons so the v10.6.0 CLI/daemon/runtime strings and adapter behavior are active.
• To use the Codex CLI adapter: install Codex CLI separately and sign in with your ChatGPT account (codex login). DreamGraph will detect the existing login and use it. No API key required.
• To use the Copilot CLI adapter: install Copilot CLI and sign in with your GitHub Copilot account. Same pattern — DreamGraph reuses the existing CLI login.

Artifacts

This release attaches the generated first-party artifacts:

• dreamgraph-10.6.0.tgz
• dreamgraph-sdk-10.6.0.tgz
• dreamgraph-host-10.6.0.tgz
• dreamgraph-vscode-10.6.0.vsix

Commits since v10.5.0

454ba4d (feature): codex-cli release. lift your existing openai plus/pro subscription into new levels of knowledge. codex times 100. perfect partners. still beta but works.
550ed96 Copilot CLI updated to view the per file diff after each turn (per tool call implementation postponed)

DreamGraph v10.5.0 — Renata

DreamGraph v10.5.0 — Renata

v10.5.0 is the current Renata release. It brings the CLI, daemon, VS Code extension, dashboard, Explorer, SDK, host package, root documentation, docs, and user guide onto one published version line.

No breaking changes are intended for existing v10.x installations.

---

Headline changes

1. Copilot CLI native adapter hardening

The VS Code Architect can now use Copilot CLI as a native DreamGraph-aware provider path with:

• DreamGraph MCP authority checks and fail-closed grounding.
• Inheritance-proxy MCP bridging so Copilot CLI shares the Architect's live DreamGraph session.
• Audited dreamgraph:run_command routing for build/test/verification work.
• Explicit denial and filtering of phantom cli:* shell/write tools.
• Idle-output timeout semantics: productive long runs can continue while stalled runs still terminate quickly.
• Cause-specific cancellation and retry-success verification handling so a recovered retry does not poison the verdict.

2. Native scanner and graph enrichment expansion

The scanner line now includes broader native language extraction and richer graph provenance:

• C and C++ extractors, including pointer/list/container/template shape modeling.
• Rust, Java, Kotlin, Python, C#, Gradle, Go, and Swift extraction slices.
• Autonomous parser-node enrichment via enrich_parser_nodes.
• Canonical promotion provenance gates and source-less fact quarantine.

3. UI registry and Explorer graph citizenship

UI registry entries are now first-class graph citizens when they carry source provenance. The Explorer and graph surfaces can show UI registry nodes directly, and the native UI scanner can populate React/Vue/Svelte/Blazor/WPF component entries without overwriting curated registry data.

4. Version and documentation alignment

This release aligns all first-party versioned surfaces to 10.5.0:

• Root daemon/CLI package and package lock.
• @dreamgraph/sdk and @dreamgraph/host workspace packages.
• Explorer package and package lock.
• VS Code extension package, package lock, runtime MCP client identity, activation-version marker, and extension README.
• CLI version output and MCP client identity.
• Root README, architecture docs, SDK docs, plugin guide/reference, and user-guide install examples.

---

Upgrade notes

• Node 20+ remains required.
• Re-run the installer (scripts/install.ps1 -Force or bash scripts/install.sh --force) after pulling this release.
• Reload VS Code after installing dreamgraph-vscode-10.5.0.vsix.
• Restart running DreamGraph daemons so the v10.5.0 CLI/daemon/runtime strings and adapter behavior are active.

Artifacts

This release attaches the generated first-party artifacts:

• dreamgraph-10.5.0.tgz
• dreamgraph-sdk-10.5.0.tgz
• dreamgraph-host-10.5.0.tgz
• dreamgraph-vscode-10.5.0.vsix

Commits since v10.0.1

09eb4c4 (fix): Copilot CLI most issues now fixed. Now more cancellation on timeout or failed tool calls. DreamGraph tools authorative.
56cbeb0 feat(copilot-cli): inheritance-proxy MCP bridge so Copilot CLI shares the architect's live DreamGraph session (fail-closed)
832fb14 (feature): Copilot-CLI adapter for Architect is now operational. No tool trace yet but works using dreamgraph tools and with your copilot account.
9270006 Update install.ps1
3d19821 v10.4.0
116fb46 feat(explorer): surface ui_registry entries as first-class graph nodes
dd8253d wire semantic-invariants constants into snapshot, _shared, llm-dream prompt
3f3917b v10.4.0: canonical promotion provenance gate + source-less fact quarantine
0b87f8b feat(ui): native UI scanner — slice 2 (v10.3.0)
952092b fix(plugins): enforce model-safe snake_case for plugin tool names; keep dotted UI ids
dc8faeb feat(ui): promote UI registry elements to first-class graph citizens (slice 1)
12cdeec feat(enrichment): autonomous batch enrichment for parser-discovered nodes via new enrich_parser_nodes MCP tool
13e2d0d feat(scanner): Swift extractor (SW-1..SW-3)
658a452 feat(scanner): Go extractor (GO-1..GO-3)
bd6e879 fix(extension): escape inline-code backticks in architect-core prompt template literal
13d4ad2 feat(scanner): Gradle extractor (G-1)
ac7b260 feat(scanner): C# extractor (CS-1..CS-3)
80fbf49 feat(scanner): Python extractor (PY-1..PY-3)
2851b2a feat(scanner): Kotlin extractor (KT-1..KT-3)
25ec897 fix(scanner): repair intermediate-layer coherence
2db76f5 docs(scanner): note Java extractor in Phase 2.6 + source layout
f4811fe feat(scanner): Java extractor (JV-1..JV-3)
ff51bbf docs(scanner): document polyglot native scanner (C/C++/Rust)
08d54fc feat(scanner): Rust extractor (RS-1..RS-3)
2fa724c feat(scan-project): wire native C/C++ extractors into data_model + scan_quality
8625820 feat(scanner/cpp): CPP-4 template parameters + specialisation edges
695f4f2 feat(scanner/cpp): CPP-3 smart pointer + STL container shape edges
bbbee51 feat(scanner/cpp): CPP-2 methods, constructors, destructors, out-of-line defs
b0fcb71 scanner(cpp): CPP-1 namespaces, classes, structs, inheritance, access modifiers
123a136 scanner(c): C-5 intrusive list / array-with-count / opaque handle
fb04159 scanner(c): C-4 singly + doubly linked-list shape detection
93e8065 scanner(c): C-3 cross-file linker
bf6bf7a scanner(c): C-2 pointer modeling
55e0b09 scanner(c): C-1 extractor + fixture + snapshot test
b30eab5 scanner: ontology constants + tree-sitter parser bootstrap

v10.0.1 — Renata stability + per-file diff review

DreamGraph v10.0.1 — Renata

v10.0.1 is a focused stability and UX release on top of the v10.0 "Renata" line. It hardens the architect's continuation behaviour, ships a Copilot-parity per-file diff review surface, fixes provider/model persistence across restarts, and tightens the Linux/PowerShell installers so a botched install can no longer pretend to be a successful one.

No breaking changes. Drop-in upgrade from v10.0.0.

---

Headline changes

1. Per-file diff review surface (Copilot parity)

The "Changed Files" panel is no longer a flat dump. Each agent pass that touches the workspace now produces a collapsible diff bar with:

• Per-file rows with Keep / Undo controls.
• Click the filename to open VS Code's native diff compare against the pre-change snapshot — the same gesture Copilot users already have muscle memory for.
• A backing change-review service (change-review-service.ts) and a reviewable-file filter (reviewable-file-filter.ts) that suppress noise: generated files, lockfiles, build artefacts, and out-of-workspace paths never reach the review surface.
• Architect passes, manual tool calls, and autonomy continuations all funnel through the same review surface — one place to accept or revert, regardless of how the change was produced.

This replaces the v10.0.0 changed-files view, which exposed raw mutations without a reversible gate.

2. Architect continuation: less talk, more action

The continuation loop in v10.0.0 was prone to two failure modes: (a) burning a pass on another "let me look at X" read after the patch target was already anchored, and (b) re-doing locate work across user turns when the user manually re-clicked an action chip. Both are fixed.

• Anchor-stop discipline (847bf46): once a concrete patch anchor is established in a pass, the architect stops researching and applies. No more "I'll just double-check the imports" right before the apply.
• WRITE-bound continuation directive (autonomy-loop.ts): the continuation prompt now emits an explicit WRITE directive when the selected action is a write-class tool or when a patch anchor has been established. The next pass starts already pointed at the edit.
• Cross-turn write-pressure narrowing (chat-panel.ts): when a user begins a new turn after a locate-only pass, with a sticky anchor still present, the effective tool catalog is narrowed to write-and-verify tools. Manual re-clicks of "Patch …" action chips no longer degrade back into read-heavy exploration.
• Hand-off packets on budget exhaustion (6853acf): when a pass exhausts its budget, the architect now emits a structured hand-off packet (intent, anchor, next concrete step) so the following pass picks up mid-stride instead of restarting from the prompt.

3. Per-project provider and model persistence

The chosen provider and model are now persisted per workspace, not globally. Switching repositories no longer silently swaps you onto whichever provider the last project happened to use, and a workspace's provider survives VS Code restarts. (3865009)

4. Web senses: large-output truncation fix

The web fetch / search senses no longer corrupt downstream context when a single response runs into the tens of kilobytes. Long bodies are truncated cleanly with a marker the architect can reason about, instead of overrunning the context window and silently degrading the rest of the pass. (2cfa801)

5. UI: redundant "Show tool trace" entry removed

A duplicate "Show tool trace" affordance that shipped in v10.0.0 has been removed; trace access remains in the canonical location. (6f4f080)

6. Linux + PowerShell installer hardening

The installer cascade exposed by the WSL bring-up flow has been fixed end-to-end:

• Node 20+ required. Both scripts/install.sh and scripts/install.ps1 now fail fast with a clear message on Node 18 (which broke undici@7, vsce@3, and cheerio@1.2). INSTALL.md updated to match. package.json declares "engines": { "node": ">=20.0.0" }.
• Stale tsbuildinfo cleanup. The installer now deletes lingering tsconfig.tsbuildinfo files before building, so tsc -b can no longer skip CLI emit when the incremental cache disagrees with reality.
• Hard build assertion. Immediately after the root build, the installer asserts that dist/cli/dg.js exists. If it doesn't, it dumps dist/ and exits with a directive to re-run npx tsc -b --verbose. Silent CLI-missing failures are gone.
• Verify step actually fails on failure. The post-install verification is no longer swallowed; its captured output is re-printed and the installer aborts on non-zero exit.
• Honest final banner. When the core installs but the VS Code extension fails to build or package, the installer now tracks EXTENSION_INSTALL_FAILED and prints a yellow "core installed — extension FAILED" banner instead of the previous green success.

7. Docs: federation post-office

Initial design document for the federation post-office (federation-post-office-v1.md) landed for review. Internal-only at this stage; no runtime surface yet. (622b8cd, 0176853)

---

Upgrade notes

• Node 20+ is required for fresh installs. Existing v10.0.0 deployments on Node 20 upgrade in place with no action.
• VS Code extension: install the dreamgraph-vscode-10.0.1.vsix attached to this release, or reload after the next workspace install.
• The architect-v2/ quarantine introduced in v10.0.0 is unchanged.

Commits in this release

6f4f080  (fix): Removed redundant Show tool trace
3865009  (fix): per project provider/model settings persistence over restarts
f3f87b3  (feature): Per file diff view, architect improvements, sdk example plugin name fix + UX
f1aabeb  Autonomy improvements
847bf46  (fix): Less talk more action — anchor-stop in architect (token economy)
2cfa801  (fix): Web senses truncation fix on long outputs
0176853  Update federation-post-office-v1.md
622b8cd  Create federation-post-office-v1.md
6853acf  (architect) Continuity fixes and hand-off packets when pass budget is exhausted