@quolu/lattice 0.12.34 → 0.14.0

package/bin/lattice-dashboard.mjs

@@ -5,7 +5,7 @@ import path from 'node:path';
 
 import { readTodoStoreStable } from '../src/todo-store.mjs';
 import { projectTodoStatus } from '../src/todo-status.mjs';
-import { renderTodoGanttForProject } from '../src/todo-cli.mjs';
+import { ganttLiveHeadDigest, renderTodoGanttForProject } from '../src/todo-cli.mjs';
 import {
   readVisibleTodoDashboardProjects,
   writeTodoDashboardDaemonDescriptor,
@@ -89,9 +89,14 @@ async function synchronize() {
         const store = await readCachedStore(entry.repo_root);
         const result = await renderTodoGanttForProject({ repoRoot: entry.repo_root,
           stable: true, displayName, readModel: store });
-        return { html: result.rendered.html, head_digest: result.metadata.manifest_digest };
+        return {
+          html: result.rendered.html,
+          head_digest: await ganttLiveHeadDigest({ repoRoot: entry.repo_root, store }),
+        };
       },
-      readHead: async () => (await readCachedStore(entry.repo_root)).manifest.manifest_digest,
+      readHead: async () => ganttLiveHeadDigest({
+        repoRoot: entry.repo_root, store: await readCachedStore(entry.repo_root),
+      }),
     });
     roots.set(entry.project_id, binding);
   }

package/bin/lattice.mjs

@@ -14,6 +14,11 @@ if (help !== null) {
   process.stdout.write(help);
 } else if (args.length === 1 && args[0] === '--version') {
   process.stdout.write(`${packageJson.version}\n`);
+} else if (args.length === 2 && args[0] === 'session-context' && args[1] === '--json') {
+  const { runSessionContext } = await import('../src/project-cli.mjs');
+  process.exitCode = await runSessionContext({
+    cwd: process.cwd(), stdout: process.stdout, cliVersion: packageJson.version,
+  });
 } else if (args.length === 2 && args[0] === 'status' && args[1] === '--json') {
   const { projectStatusFailure, runProjectStatus } = await import('../src/project-cli.mjs');
   try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quolu/lattice",
-  "version": "0.12.34",
+  "version": "0.14.0",
   "description": "Lattice — phase-aware TODO graph compiler and conflict-aware orchestration runtime",
   "type": "module",
   "license": "MIT",
@@ -60,7 +60,7 @@
     "test": "node scripts/run-product-tests.mjs",
     "test:sensor": "npm --prefix sensor test",
     "precheck": "node --check src/bridge-launch-agent.mjs",
-    "check": "node --check bin/lattice.mjs && node --check bin/lattice-mcp.mjs && node --check bin/lattice-dashboard.mjs && node --check bin/lattice-bridge.mjs && node --check bin/lattice-scripted-adapter.mjs && node --check src/cli-stdio.mjs && node --check src/bridge-address.mjs && node --check src/bridge-registrar.mjs && node --check src/todo-gantt-layout.mjs && node --check src/todo-gantt-scope.mjs && node --check src/bridge-config.mjs && node --check src/bridge-server.mjs && node --check src/bridge-daemon.mjs && node --check src/bridge-cli.mjs && node --check src/project-cli.mjs && node --check src/sensor-cli.mjs && node --check src/sensor-runtime.mjs && node --check src/sensor-adapter.mjs && node --check src/factory-diagnostics.mjs && node --check src/runtime-errors.mjs && node --check src/runtime-contracts.mjs && node --check src/runtime-event-store.mjs && node --check src/runtime-adapter-registry.mjs && node --check src/runtime-scripted-adapter-controller.mjs && node --check src/hash-chain.mjs && node --check src/dag-chain.mjs && node --check src/todo-contracts.mjs && node --check src/todo-chain.mjs && node --check src/todo-store.mjs && node --check src/todo-migration.mjs && node --check src/todo-revision.mjs && node --check src/todo-status.mjs && node --check src/todo-cli.mjs && node --check src/todo-dashboard-registry.mjs && node --check src/todo-gantt-presentation.mjs && node --check src/todo-gantt-live.mjs && node --check src/bounded-seam.mjs && node --check src/todo-narrative-anchor.mjs && node --check src/todo-markdown-renderer.mjs && node --check src/todo-gantt-svg.mjs && node --check src/todo-gantt-html.mjs && node --check src/runtime-projection.mjs && node --check src/runtime-decision-verifier.mjs && node --check src/runtime-front-end.mjs && node --check src/runtime-cli.mjs && node --check src/rc3-dogfood-scaffold.mjs && node --check src/runtime-engine.mjs && node --check src/runtime-scripted-executor.mjs && node --check src/runtime-diff-observer.mjs && node --check src/runtime-worktree-executor.mjs && node --check src/runtime-hold-recompile.mjs && node --check src/rc3-scripted-campaign.mjs && node --check src/rc3-actual-dogfood.mjs && node --check src/rc4-stage1-dogfood.mjs && node --check research/fixtures/dispatch-record/src/dispatch-record.mjs && node --check test/research-dispatch-record.test.mjs",
+    "check": "node --check bin/lattice.mjs && node --check bin/lattice-mcp.mjs && node --check bin/lattice-dashboard.mjs && node --check bin/lattice-bridge.mjs && node --check bin/lattice-scripted-adapter.mjs && node --check src/cli-stdio.mjs && node --check src/bridge-address.mjs && node --check src/bridge-registrar.mjs && node --check src/todo-independence-guidance.mjs && node --check src/todo-independence.mjs && node --check src/todo-independence-contracts.mjs && node --check src/todo-gantt-layout.mjs && node --check src/todo-gantt-scope.mjs && node --check src/bridge-config.mjs && node --check src/bridge-server.mjs && node --check src/bridge-daemon.mjs && node --check src/bridge-cli.mjs && node --check src/project-cli.mjs && node --check src/sensor-cli.mjs && node --check src/sensor-runtime.mjs && node --check src/sensor-adapter.mjs && node --check src/factory-diagnostics.mjs && node --check src/runtime-errors.mjs && node --check src/runtime-contracts.mjs && node --check src/runtime-event-store.mjs && node --check src/runtime-adapter-registry.mjs && node --check src/runtime-scripted-adapter-controller.mjs && node --check src/hash-chain.mjs && node --check src/dag-chain.mjs && node --check src/todo-contracts.mjs && node --check src/todo-chain.mjs && node --check src/todo-store.mjs && node --check src/todo-migration.mjs && node --check src/todo-revision.mjs && node --check src/todo-status.mjs && node --check src/todo-cli.mjs && node --check src/todo-dashboard-registry.mjs && node --check src/todo-gantt-presentation.mjs && node --check src/todo-gantt-live.mjs && node --check src/bounded-seam.mjs && node --check src/todo-narrative-anchor.mjs && node --check src/todo-markdown-renderer.mjs && node --check src/todo-gantt-svg.mjs && node --check src/todo-gantt-html.mjs && node --check src/runtime-projection.mjs && node --check src/runtime-decision-verifier.mjs && node --check src/runtime-front-end.mjs && node --check src/runtime-cli.mjs && node --check src/rc3-dogfood-scaffold.mjs && node --check src/runtime-engine.mjs && node --check src/runtime-scripted-executor.mjs && node --check src/runtime-diff-observer.mjs && node --check src/runtime-worktree-executor.mjs && node --check src/runtime-hold-recompile.mjs && node --check src/rc3-scripted-campaign.mjs && node --check src/rc3-actual-dogfood.mjs && node --check src/rc4-stage1-dogfood.mjs && node --check research/fixtures/dispatch-record/src/dispatch-record.mjs && node --check test/research-dispatch-record.test.mjs",
     "check:project-identity": "node --check src/project-identity.mjs",
     "ci": "npm run test && npm run test:sensor && npm run check && npm run check:project-identity"
   }

package/sensor/dist/mcp/server-instructions.d.ts

@@ -15,7 +15,7 @@
  * burn tokens. ADR 0049 / 0059 require the eight compatibility tools to remain
  * visible by default; provider identity is Lattice regardless of their names.
  */
-export declare const SERVER_INSTRUCTIONS = "# Lattice sensor \u2014 code intelligence over an indexed knowledge graph\n\nProvider identity: lattice. The lattice_sensor_* names below are compatibility tool names served by Lattice's own bundled sensor; they do not call or require the independent Lattice sensor product.\n\nLattice sensor is a SQLite knowledge graph of every symbol, edge, and file in\nthe workspace \u2014 pre-computed structure you would otherwise re-derive by\nreading files (cached intelligence: thousands of parse/trace decisions you\ndon't pay to re-reason each run). Reads are sub-millisecond; the index lags\nwrites by ~1s through the file watcher. Reach for it BEFORE *and* while\nwriting or editing code \u2014 not just for questions: one call returns the\nverbatim source PLUS who calls it and what it affects, so you edit with the\nblast radius in view. More accurate context, in far fewer tokens and\nround-trips than reading files yourself.\n\n## One tool: lattice_sensor_explore \u2014 use it instead of reading files\n\nThere is a single tool, `lattice_sensor_explore`, and it is Read-equivalent. It\ntakes either a natural-language question or a bag of symbol/file names and\nreturns the **verbatim, line-numbered source** of the relevant symbols\ngrouped by file \u2014 the same `<n>\\t<line>` shape `Read` gives you, safe to\n`Edit` from \u2014 PLUS the call path among them (including dynamic-dispatch hops\nlike callbacks, React re-render, and JSX children that grep can't follow) and\na blast-radius summary of what depends on them.\n\nWhether you're answering \"how does X work\" or implementing a change (fixing a\nbug, adding a feature), call `lattice_sensor_explore` before you Read. ONE call\nusually answers the whole question. Lattice sensor IS the pre-built search index \u2014\nso running your own grep + read loop, or delegating the lookup to a separate\nfile-reading sub-task/agent, repeats work lattice sensor already did and costs more\nfor the same answer. A direct lattice sensor answer is typically one to a few\ncalls; a grep/read exploration is dozens.\n\n## How to query\n\n- **Almost any question \u2014 \"how does X work\", architecture, a bug, \"what/where is X\", or surveying an area** \u2192 `lattice_sensor_explore` with a natural-language question or the relevant names. ONE capped call returns the verbatim source grouped by file; most often the ONLY call you need.\n- **\"How does X reach/become Y? / the flow / the path from X to Y\"** \u2192 `lattice_sensor_explore`, naming the symbols that span the flow (e.g. `mutateElement renderScene`) \u2014 it surfaces the call path among them, riding dynamic-dispatch hops, and returns their source.\n- **Reading or editing a file/symbol you can name** \u2192 put its name or file path in the `lattice_sensor_explore` query \u2014 it returns that current line-numbered source (safe to `Edit` from) with the call path and blast radius attached, so you don't Read it separately. For an overloaded name it returns every matching definition's body in one call.\n- **Need more?** Call `lattice_sensor_explore` again with more specific names \u2014 treat the source it returns as already Read.\n\n## Anti-patterns\n\n- **Trust lattice sensor's results \u2014 don't re-verify them with grep.** They come from a full AST parse; re-checking with grep is slower, less accurate, and wastes context.\n- **Don't grep or Read first** to find or understand indexed code \u2014 ONE `lattice_sensor_explore` returns the relevant symbols' source together in a single round-trip. Reach for raw `Read`/`Grep` only to confirm a specific detail lattice sensor didn't cover, or for what lattice sensor doesn't index (configs, docs).\n- **Don't reconstruct a flow by hand** \u2014 name the endpoints in one `lattice_sensor_explore` and it surfaces the path between them, dynamic-dispatch hops included.\n- **After editing, check the staleness banner.** When a tool response starts with \"\u26A0\uFE0F Some files referenced below were edited since the last index sync\u2026\", the listed files are pending re-index \u2014 Read those specific files for accurate content. Every file NOT in that banner is fresh, so still trust lattice sensor. A different, rarer banner \u2014 \"\u26A0\uFE0F LatticeSensor auto-sync is DISABLED\u2026\" \u2014 means live watching stopped entirely (the whole index is frozen, not just a few files); until it's resolved, Read files directly to confirm anything that may have changed.\n\n## Limitations\n\n- If a project isn't indexed (no `.lattice/sensor/`), decide whether building the index will reduce total investigation time and model tokens for the current or expected work. When workspace writes and shell execution are allowed, you may run `lattice sensor init <projectPath> --json` yourself, then retry the sensor call; scope it to the intended project and account for the one-time indexing cost. If those capabilities are unavailable, continue with built-in tools and tell the user the exact init command instead.\n- Index lags file writes by ~1 second.\n- Cross-file resolution is best-effort name matching; ambiguous calls may return multiple candidates.\n- No live correctness validation \u2014 that's still the TypeScript compiler / test suite / linter's job. Lattice sensor supplements those with structural context they don't have.\n";
+export declare const SERVER_INSTRUCTIONS = "# Lattice sensor \u2014 code intelligence over an indexed knowledge graph\n\nProvider identity: lattice. The lattice_sensor_* names below are compatibility tool names served by Lattice's own bundled sensor; they do not call or require the independent Lattice sensor product.\n\nLattice sensor is a SQLite knowledge graph of every symbol, edge, and file in\nthe workspace \u2014 pre-computed structure you would otherwise re-derive by\nreading files (cached intelligence: thousands of parse/trace decisions you\ndon't pay to re-reason each run). Reads are sub-millisecond; the index lags\nwrites by ~1s through the file watcher. Reach for it BEFORE *and* while\nwriting or editing code \u2014 not just for questions: one call returns the\nverbatim source PLUS who calls it and what it affects, so you edit with the\nblast radius in view. More accurate context, in far fewer tokens and\nround-trips than reading files yourself.\n\n## One tool: lattice_sensor_explore \u2014 use it instead of reading files\n\nThere is a single tool, `lattice_sensor_explore`, and it is Read-equivalent. It\ntakes either a natural-language question or a bag of symbol/file names and\nreturns the **verbatim, line-numbered source** of the relevant symbols\ngrouped by file \u2014 the same `<n>\\t<line>` shape `Read` gives you, safe to\n`Edit` from \u2014 PLUS the call path among them (including dynamic-dispatch hops\nlike callbacks, React re-render, and JSX children that grep can't follow) and\na blast-radius summary of what depends on them.\n\nWhether you're answering \"how does X work\" or implementing a change (fixing a\nbug, adding a feature), call `lattice_sensor_explore` before you Read. ONE call\nusually answers the whole question. Lattice sensor IS the pre-built search index \u2014\nso running your own grep + read loop, or delegating the lookup to a separate\nfile-reading sub-task/agent, repeats work lattice sensor already did and costs more\nfor the same answer. A direct lattice sensor answer is typically one to a few\ncalls; a grep/read exploration is dozens.\n\n## How to query\n\n- **Almost any question \u2014 \"how does X work\", architecture, a bug, \"what/where is X\", or surveying an area** \u2192 `lattice_sensor_explore` with a natural-language question or the relevant names. ONE capped call returns the verbatim source grouped by file; most often the ONLY call you need.\n- **\"How does X reach/become Y? / the flow / the path from X to Y\"** \u2192 `lattice_sensor_explore`, naming the symbols that span the flow (e.g. `mutateElement renderScene`) \u2014 it surfaces the call path among them, riding dynamic-dispatch hops, and returns their source.\n- **Reading or editing a file/symbol you can name** \u2192 put its name or file path in the `lattice_sensor_explore` query \u2014 it returns that current line-numbered source (safe to `Edit` from) with the call path and blast radius attached, so you don't Read it separately. For an overloaded name it returns every matching definition's body in one call.\n- **Need more?** Call `lattice_sensor_explore` again with more specific names \u2014 treat the source it returns as already Read.\n\n## Anti-patterns\n\n- **Trust lattice sensor's results \u2014 don't re-verify them with grep.** They come from a full AST parse; re-checking with grep is slower, less accurate, and wastes context.\n- **Don't grep or Read first** to find or understand indexed code \u2014 ONE `lattice_sensor_explore` returns the relevant symbols' source together in a single round-trip. Reach for raw `Read`/`Grep` only to confirm a specific detail lattice sensor didn't cover, or for what lattice sensor doesn't index (configs, docs).\n- **Don't reconstruct a flow by hand** \u2014 name the endpoints in one `lattice_sensor_explore` and it surfaces the path between them, dynamic-dispatch hops included.\n- **After editing, check the staleness banner.** When a tool response starts with \"\u26A0\uFE0F Some files referenced below were edited since the last index sync\u2026\", the listed files are pending re-index \u2014 Read those specific files for accurate content. Every file NOT in that banner is fresh, so still trust lattice sensor. A different, rarer banner \u2014 \"\u26A0\uFE0F LatticeSensor auto-sync is DISABLED\u2026\" \u2014 means live watching stopped entirely (the whole index is frozen, not just a few files); until it's resolved, Read files directly to confirm anything that may have changed.\n\n## Limitations\n\n- If a project isn't indexed (no `.lattice/sensor/`), decide whether building the index will reduce total investigation time and model tokens for the current or expected work. When workspace writes and shell execution are allowed, you may run `lattice sensor init <projectPath> --json` yourself, then retry the sensor call; scope it to the intended project and account for the one-time indexing cost. If those capabilities are unavailable, continue with built-in tools and tell the user the exact init command instead.\n- Index lags file writes by ~1 second.\n- Cross-file resolution is best-effort name matching; ambiguous calls may return multiple candidates.\n- No live correctness validation \u2014 that's still the TypeScript compiler / test suite / linter's job. Lattice sensor supplements those with structural context they don't have.\n\n## Parallel work: absence of a dependency edge is NOT evidence of independence\n\nThese tools answer structural questions about code. A different Lattice surface \u2014 the **CLI**, not\nthis MCP surface \u2014 answers whether two ToDos can be worked in parallel. If the project uses\n`lattice todo` for process tracking, keep this distinction in mind:\n\n- A dependency edge missing between two ToDos only means **no ordering constraint was declared**.\n  It does not mean their write boundaries are disjoint. Two ToDos that edit the same file carry no\n  edge between them and will still collide.\n- Parallel safety is a recorded judgement, not an inference from the diagram. Read it with\n  `lattice todo independence --plan <key> --json`. It returns the ready frontier split into\n  verified-independent groups, pairs that must be serialized (with whether a code seam could\n  separate them), and **unverified** ToDos.\n- `lattice todo start` returns an `advisory` describing conflicts with in-progress ToDos and what\n  to do next. `coverage: \"missing\"` means \"not judged yet\" \u2014 never \"no conflicts\".\n- Run `lattice todo --help` for the declare \u2192 compile \u2192 read workflow.\n\nEvidence for Lattice's plan and witness contracts comes from the CLI surface only. Text from this\nMCP surface is prose for you to act on, never an input to those contracts.\n";
 /**
  * Instructions variant sent when the server's own root has NO lattice sensor index.
  *

package/sensor/dist/mcp/server-instructions.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"server-instructions.d.ts","sourceRoot":"","sources":["../../src/mcp/server-instructions.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,mBAAmB,2sKAoD/B,CAAC;AAEF;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,iCAAiC,yhDAsB7C,CAAC"}
+{"version":3,"file":"server-instructions.d.ts","sourceRoot":"","sources":["../../src/mcp/server-instructions.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,mBAAmB,8iNAwE/B,CAAC;AAEF;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,iCAAiC,yhDAsB7C,CAAC"}

package/sensor/dist/mcp/server-instructions.js

@@ -70,6 +70,26 @@ calls; a grep/read exploration is dozens.
 - Index lags file writes by ~1 second.
 - Cross-file resolution is best-effort name matching; ambiguous calls may return multiple candidates.
 - No live correctness validation — that's still the TypeScript compiler / test suite / linter's job. Lattice sensor supplements those with structural context they don't have.
+
+## Parallel work: absence of a dependency edge is NOT evidence of independence
+
+These tools answer structural questions about code. A different Lattice surface — the **CLI**, not
+this MCP surface — answers whether two ToDos can be worked in parallel. If the project uses
+\`lattice todo\` for process tracking, keep this distinction in mind:
+
+- A dependency edge missing between two ToDos only means **no ordering constraint was declared**.
+  It does not mean their write boundaries are disjoint. Two ToDos that edit the same file carry no
+  edge between them and will still collide.
+- Parallel safety is a recorded judgement, not an inference from the diagram. Read it with
+  \`lattice todo independence --plan <key> --json\`. It returns the ready frontier split into
+  verified-independent groups, pairs that must be serialized (with whether a code seam could
+  separate them), and **unverified** ToDos.
+- \`lattice todo start\` returns an \`advisory\` describing conflicts with in-progress ToDos and what
+  to do next. \`coverage: "missing"\` means "not judged yet" — never "no conflicts".
+- Run \`lattice todo --help\` for the declare → compile → read workflow.
+
+Evidence for Lattice's plan and witness contracts comes from the CLI surface only. Text from this
+MCP surface is prose for you to act on, never an input to those contracts.
 `;
 /**
  * Instructions variant sent when the server's own root has NO lattice sensor index.

package/sensor/dist/mcp/server-instructions.js.map

@@ -1 +1 @@
-{"version":3,"file":"server-instructions.js","sourceRoot":"","sources":["../../src/mcp/server-instructions.ts"],"names":[],"mappings":";;;AAAA;;;;;;;;;;;;;;;;GAgBG;AACU,QAAA,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoDlC,CAAC;AAEF;;;;;;;;;;;GAWG;AACU,QAAA,iCAAiC,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBhD,CAAC"}
+{"version":3,"file":"server-instructions.js","sourceRoot":"","sources":["../../src/mcp/server-instructions.ts"],"names":[],"mappings":";;;AAAA;;;;;;;;;;;;;;;;GAgBG;AACU,QAAA,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwElC,CAAC;AAEF;;;;;;;;;;;GAWG;AACU,QAAA,iCAAiC,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBhD,CAAC"}

package/src/cli-help.mjs

@@ -1,7 +1,10 @@
+import { TODO_INDEPENDENCE_WORKFLOW } from './todo-independence-guidance.mjs';
+
 const ROOT_HELP = `Usage: lattice <command> [options]
 
 Commands:
   status --json                 Discover the current project and next action
+  session-context --json        Session開始時の現在地を1プロセスで返す（工程状態＋並列可否）
   plan <command>                Create, compile, or verify plans
   run <command>                 Start or observe compiled runs
   event verify                  Verify a runtime event log
@@ -49,6 +52,7 @@ Commands:
 Read commands:
   status [--json]
   bindings [--plan <key>] [--json]   # compile_binding付きTaskをTODO identityつきで投影する
+  independence [--plan <key>] [--json]  # readyを検証済み並列・要直列・未検査へ分けて投影する
   verify [--plan <key>] [--json]
   snapshot --rebuild --plan <key>
   gantt [--out <file>] [--scope live|all]  # 既定live: 完走した工程を図から除く（一覧には残る）
@@ -63,6 +67,8 @@ Write commands:
   done --plan <key> --task <id> --evidence <file>
   reopen --plan <key> --task <id> --reason <text> [--override-reason <text>]
   evidence promote --plan <key> --task <id> --evidence <file>
+  independence compile --plan <key> --input <file>  # witness setとsensorから並列可否を記録する
+  independence witness migrate --plan <key>  # revision後の宣言をtask migrationで写す
   revise --plan <key> --input <file>
   revise-phase --plan <key> --input <file>
   revise-set --input <file>
@@ -72,6 +78,12 @@ Write commands:
 
 Write commands require LATTICE_TODO_ACTOR_HOST, LATTICE_TODO_ACTOR_SESSION,
 and LATTICE_TODO_ACTOR_AGENT.
+
+並列可否（依存線の不在は、書き込み境界が干渉しないことを意味しない）:
+${TODO_INDEPENDENCE_WORKFLOW.join('\n')}
+
+判定していない工程は「競合が無い」ではなく「未検査」として扱われ、
+todo startのadvisoryとtodo independenceの投影が、その状況と次の一歩を返す。
 `,
   sensor: `Usage: lattice sensor <init|sync> [path] --json
 `,
@@ -117,6 +129,7 @@ const SUBCOMMAND_USAGE = Object.freeze({
   'event verify': 'event verify --run .lattice/runs/<id>',
   'todo status': 'todo status [--json]',
   'todo bindings': 'todo bindings [--plan <key>] [--json]',
+  'todo independence': 'todo independence [--plan <key>] [--json] | compile --plan <key> --input <file> | witness migrate --plan <key>',
   'todo verify': 'todo verify [--plan <key>] [--json]',
   'todo snapshot': 'todo snapshot --rebuild --plan <key>',
   'todo gantt': 'todo gantt [--out <file>] [--scope live|all] | status [--out <file>] | serve --port <port> [--scope live|all]',

package/src/project-cli.mjs

@@ -13,12 +13,15 @@ import {
   todoSelfDigest,
 } from './todo-contracts.mjs';
 import { projectTodoStatus } from './todo-status.mjs';
+import { projectIndependenceFrontier } from './todo-independence.mjs';
+import { selectIndependenceGuidance } from './todo-independence-guidance.mjs';
 import { ensureTodoDashboardActivity } from './todo-dashboard-registry.mjs';
 import { resolveProjectIdentity } from './project-identity.mjs';
 import {
   buildTodoPlan,
   createTodoStoreWriter,
   initializeAuthoredTodoStore,
+  readTodoIndependenceArtifact,
   readTodoStore,
   TodoStoreError,
 } from './todo-store.mjs';
@@ -27,6 +30,9 @@ const STORE_REF = '.lattice/todo';
 const MANIFEST_REF = `${STORE_REF}/manifest.json`;
 const MAX_INPUT_BYTES = 8_388_608;
 const STATUS_SCHEMA = 'lattice.project_status.v1';
+const SESSION_CONTEXT_SCHEMA = 'lattice.session_context.v1';
+/** HEADが読めない環境でも投影を組めるようにする。記録があるときは実HEADで置き換わる。 */
+const PLACEHOLDER_SHA = '0'.repeat(40);
 const CREATE_INPUT_SCHEMA = 'lattice.plan_create_input.v1';
 const PHASE_CREATE_INPUT_SCHEMA = 'lattice.plan_create_input.v2';
 const DECOUPLED_PHASE_CREATE_INPUT_SCHEMA = 'lattice.plan_create_input.v3';
@@ -106,6 +112,73 @@ export function validateProjectStatus(value) {
   } catch { return false; }
 }
 
+/**
+ * readyのあるplanについてだけ並列可否を要約する（ADR 0131 Decision 5）。
+ *
+ * store読みは呼び出し側が済ませている。ここが払うのはplanごとの小さな記録ファイルと、
+ * 記録があるときだけのHEAD照合である。readyが無いplanは述べる対象が無いので載せない。
+ */
+async function summarizeIndependence({ repoRoot, store, todo }) {
+  const readyPlanKeys = [...new Set(todo.next_ready.map(({ plan_key: key }) => key))].sort();
+  if (readyPlanKeys.length === 0) return [];
+  const activeByPlan = new Map();
+  for (const task of todo.active_set) {
+    if (!activeByPlan.has(task.plan_key)) activeByPlan.set(task.plan_key, []);
+    activeByPlan.get(task.plan_key).push(task.task_id);
+  }
+  let currentBaseSha = null;
+  const summaries = [];
+  for (const planKey of readyPlanKeys) {
+    const member = store.members.find(({ descriptor }) => descriptor.plan_key === planKey);
+    if (member === undefined) continue;
+    let artifact = null;
+    try {
+      artifact = await readTodoIndependenceArtifact({ repoRoot, store, planKey });
+    } catch (error) {
+      // 読めない記録を「記録なし」へ丸めない。理由を載せて先へ進む。
+      summaries.push({
+        plan_key: planKey, coverage: null,
+        guidance: { code: 'independence_unrecorded', message: null, next_action: 'none' },
+        unreadable_reason: error instanceof TodoStoreError
+          ? `${error.code}:${error.detail?.reason ?? error.message}` : 'independence_unreadable',
+        parallel_groups: [], serialize_pair_count: 0,
+        conflict_with_active_count: 0, unknown_task_ids: [],
+      });
+      continue;
+    }
+    if (currentBaseSha === null && artifact !== null) currentBaseSha = gitHead(repoRoot);
+    const projected = projectIndependenceFrontier({
+      artifact,
+      readyTaskIds: todo.next_ready.filter((task) => task.plan_key === planKey)
+        .map(({ task_id: taskId }) => taskId),
+      activeTaskIds: activeByPlan.get(planKey) ?? [],
+      plan: member.plan,
+      currentBaseSha: currentBaseSha ?? PLACEHOLDER_SHA,
+      changedPaths: null,
+    });
+    summaries.push({
+      plan_key: planKey,
+      coverage: projected.coverage,
+      guidance: selectIndependenceGuidance({
+        coverage: projected.coverage,
+        readyCount: todo.next_ready.filter((task) => task.plan_key === planKey).length,
+        taskDeclared: projected.frontier.unknown
+          .every(({ unknowns }) => !unknowns.some(({ kind }) => kind === 'witness_missing')),
+        taskStale: projected.frontier.unknown
+          .some(({ unknowns }) => unknowns.some(({ kind }) => kind === 'record_stale')),
+        conflictWithActive: projected.frontier.conflicts_with_active[0]?.severability ?? null,
+        conflictBetweenReady: projected.frontier.serialize_pairs[0]?.severability ?? null,
+      }),
+      unreadable_reason: null,
+      parallel_groups: projected.frontier.parallel_groups.map(({ task_ids: ids }) => [...ids]),
+      serialize_pair_count: projected.frontier.serialize_pairs.length,
+      conflict_with_active_count: projected.frontier.conflicts_with_active.length,
+      unknown_task_ids: projected.frontier.unknown.map(({ task_id: taskId }) => taskId),
+    });
+  }
+  return summaries;
+}
+
 function statusResult(fields) {
   const result = { schema: STATUS_SCHEMA, ...fields, result_digest: '' };
   result.result_digest = resultDigest(result);
@@ -124,12 +197,18 @@ function invalidStatus({ cliVersion, repoRoot, reason }) {
   });
 }
 
-export async function runProjectStatus({ cwd, stdout, cliVersion, env = process.env,
-  ensureDashboardActivity = ensureTodoDashboardActivity }) {
+/**
+ * discoveryとstore読みを1回で済ませ、status結果と（読めたなら）storeを返す。
+ *
+ * `runProjectStatus`と`runSessionContext`が同じ判定を二度書かないための共有点。
+ * store読みはここでしか行わない——session開始経路が同じstoreを二度払っていたのが
+ * ADR 0131で直した欠陥である。
+ */
+async function resolveProjectState({ cwd, cliVersion }) {
   const repoRoot = resolveRepoRoot(cwd);
   if (repoRoot === null) {
-    stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'git_repository_unresolved' }))}\n`);
-    return 1;
+    return { exitCode: 1, repoRoot: null, store: null, todo: null,
+      result: invalidStatus({ cliVersion, repoRoot: null, reason: 'git_repository_unresolved' }) };
   }
   const storeAbsolute = path.join(repoRoot, STORE_REF);
   const manifestAbsolute = path.join(repoRoot, MANIFEST_REF);
@@ -137,30 +216,24 @@ export async function runProjectStatus({ cwd, stdout, cliVersion, env = process.
   let latticeState;
   let storeState;
   let manifestState;
+  const invalid = (reason) => ({
+    exitCode: 1, repoRoot, store: null, todo: null,
+    result: invalidStatus({ cliVersion, repoRoot, reason }),
+  });
   try { latticeState = await lstat(latticeAbsolute); } catch (error) {
-    if (error?.code !== 'ENOENT') {
-      stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'lattice_root_unreadable' }))}\n`);
-      return 1;
-    }
+    if (error?.code !== 'ENOENT') return invalid('lattice_root_unreadable');
   }
   if (latticeState !== undefined && (latticeState.isSymbolicLink() || !latticeState.isDirectory())) {
-    stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'lattice_root_invalid' }))}\n`);
-    return 1;
+    return invalid('lattice_root_invalid');
   }
   try { storeState = await lstat(storeAbsolute); } catch (error) {
-    if (error?.code !== 'ENOENT') {
-      stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'store_unreadable' }))}\n`);
-      return 1;
-    }
+    if (error?.code !== 'ENOENT') return invalid('store_unreadable');
   }
   try { manifestState = await lstat(manifestAbsolute); } catch (error) {
-    if (error?.code !== 'ENOENT') {
-      stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'manifest_unreadable' }))}\n`);
-      return 1;
-    }
+    if (error?.code !== 'ENOENT') return invalid('manifest_unreadable');
   }
   if (storeState === undefined && manifestState === undefined) {
-    const result = statusResult({
+    return { exitCode: 0, repoRoot, store: null, todo: null, result: statusResult({
       cli: { available: true, version: cliVersion },
       project: { root: repoRoot, git_head: gitHead(repoRoot), project_id: null },
       state: 'uninitialized',
@@ -171,14 +244,11 @@ export async function runProjectStatus({ cwd, stdout, cliVersion, env = process.
         input_schema: CURRENT_CREATE_INPUT_SCHEMA,
         schema_command: CURRENT_CREATE_SCHEMA_COMMAND,
       },
-    });
-    stdout.write(`${JSON.stringify(result)}\n`);
-    return 0;
+    }) };
   }
   if (storeState?.isSymbolicLink() || !storeState?.isDirectory()
     || manifestState?.isSymbolicLink() || !manifestState?.isFile()) {
-    stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason: 'store_layout_invalid' }))}\n`);
-    return 1;
+    return invalid('store_layout_invalid');
   }
   try {
     const store = await readTodoStore({ repoRoot });
@@ -205,21 +275,60 @@ export async function runProjectStatus({ cwd, stdout, cliVersion, env = process.
       can_create_plan: false,
       next_action: next,
     });
-    if (env.LATTICE_DASHBOARD_AUTOSTART !== '0') {
-      const identity = await resolveProjectIdentity({ repoRoot, projectId: store.project_id, env });
-      const actorSession = env.LATTICE_TODO_ACTOR_SESSION;
-      await ensureDashboardActivity({
-        repoRoot, projectId: store.project_id, displayName: identity.displayName,
-        sessionId: isTodoIdentifier(actorSession) ? actorSession : `status-${process.pid}`, env,
-      });
-    }
-    stdout.write(`${JSON.stringify(result)}\n`);
-    return 0;
+    return { exitCode: 0, repoRoot, store, todo, result };
   } catch (error) {
-    const reason = error instanceof TodoStoreError ? `${error.code}:${error.detail?.reason ?? error.message}` : 'store_validation_failed';
-    stdout.write(`${JSON.stringify(invalidStatus({ cliVersion, repoRoot, reason }))}\n`);
-    return 1;
+    const reason = error instanceof TodoStoreError
+      ? `${error.code}:${error.detail?.reason ?? error.message}` : 'store_validation_failed';
+    return invalid(reason);
+  }
+}
+
+export async function runProjectStatus({ cwd, stdout, cliVersion, env = process.env,
+  ensureDashboardActivity = ensureTodoDashboardActivity }) {
+  const state = await resolveProjectState({ cwd, cliVersion });
+  // dashboard活動の登録はdiscovery面の副作用として維持する（ADR 0131 Decision 4で
+  // session-context側だけが持たない、と決めた面である）。
+  if (state.store !== null && env.LATTICE_DASHBOARD_AUTOSTART !== '0') {
+    const identity = await resolveProjectIdentity({
+      repoRoot: state.repoRoot, projectId: state.store.project_id, env,
+    });
+    const actorSession = env.LATTICE_TODO_ACTOR_SESSION;
+    await ensureDashboardActivity({
+      repoRoot: state.repoRoot, projectId: state.store.project_id,
+      displayName: identity.displayName,
+      sessionId: isTodoIdentifier(actorSession) ? actorSession : `status-${process.pid}`, env,
+    });
   }
+  stdout.write(`${JSON.stringify(state.result)}\n`);
+  return state.exitCode;
+}
+
+/**
+ * session開始時の現在地を1プロセス・1 store読みで返す（ADR 0131）。
+ *
+ * `lattice status`と`lattice todo status`は同じ`readTodoStore`を別プロセスで二重に払う。
+ * hostのSessionStartはその両方を呼ぶため、storeが育ったprojectでは実行枠を超えて
+ * 案内ごと捨てられていた。ここは合成であって置き換えではない——既存2面は不変で、
+ * それぞれの消費者を持ち続ける。
+ *
+ * dashboard活動の登録は行わない。現在地を知るために呼ぶ面であり、常駐面を起こす面ではない。
+ */
+export async function runSessionContext({ cwd, stdout, cliVersion }) {
+  const state = await resolveProjectState({ cwd, cliVersion });
+  const independence = state.store === null || state.todo === null
+    ? [] : await summarizeIndependence({ repoRoot: state.repoRoot, store: state.store, todo: state.todo });
+  const result = {
+    schema: SESSION_CONTEXT_SCHEMA,
+    // project discoveryの答えをそのまま埋める。hostは既存の検証器を再利用できる。
+    status: state.result,
+    // todoは`todo_status_result.v4`そのもの。新しい意味論を発明しない。
+    todo: state.todo,
+    independence,
+    result_digest: '',
+  };
+  result.result_digest = todoSelfDigest(result, 'result_digest');
+  stdout.write(`${JSON.stringify(result)}\n`);
+  return state.exitCode;
 }
 
 async function readCanonicalInput(repoRoot, inputRef) {

package/src/runtime-front-end.mjs

@@ -786,6 +786,9 @@ export function compileRuntimePlanV1(options = {}) {
     schedule: compiled.plan,
     pairwise_verdicts: compiled.pairwise_verdicts,
     graph: bundle.graph,
+    // graph.conflictsはresource_idしか持たない。resource kindはここでしか引けないため、
+    // conflictの切断可能性を判定する消費者へnormalized resourceをそのまま渡す（ADR 0128）。
+    resources: bundle.resources,
     graph_digest: bundle.graph_digest,
   };
 }