| SMC-01 | single-issue plan cache | within-conversation; durable only after an explicit handoff marker write | Persist and update /memories/session/plan-issue-{ID}.md with vscode/memory; D9 writes <!-- plan-issue-{ID} --> only on Pause/Stop when needed. | /plan and /orchestrate use GitHub issue comments with <!-- plan-issue-{ID} --> plus parent dispatch context; Claude has no separate vscode/memory cache. | partial - same-session cache is not cross-tool; durable marker handoff is cross-tool. #379 follow-up/cross-link needed for the partial path. | Citations: Issue-Planner, Code-Conductor, Claude guide. Pending #384 (). Update this row when #384 resolves: revise the cache/marker split if plan-storage ownership changes. |
| SMC-02 | bundled plan cache | within-conversation; durable only through per-issue handoff marker writes | Persist /memories/session/plan-bundle-{primary}-{secondary1}-{secondaryN}.md; Code-Conductor reads bundle plans before single-issue plans and writes per-issue <!-- plan-issue-{ID} --> markers only on bundle D9 Pause/Stop when needed. | /orchestrate carries bundle context to code-conductor; durable resume reads each issue's GitHub markers rather than a Claude-local bundle cache. | partial - local bundle cache is not fungible; per-issue durable markers are. #379 follow-up/cross-link needed for the bundle handoff path. | Citations: Code-Conductor multi-issue flow, /orchestrate. Pending #384 (). Update this row when #384 resolves: revise bundled-plan storage and marker rules if the plan-storage contract changes. |
| SMC-03 | design cache | within-conversation; design source is durable in the issue body or an explicit design handoff marker | Cache /memories/session/design-issue-{ID}.md from the current design snapshot; Solution-Designer persists design details to the issue body, and D9 may write <!-- design-issue-{ID} --> when needed. | Prefer parent context, then latest <!-- design-issue-{ID} --> issue comment, then issue body; Claude does not require a local design cache. | yes - authoritative issue body and durable design marker are cross-tool; the session cache is only an optimization. | Citations: .github/copilot-instructions, Code-Conductor, code-conductor shell. Pending #384 (). Update this row when #384 resolves: revise design-cache and durable-design precedence if the plan/design handoff contract changes. |
| SMC-05 | pre-PR review-state | within-conversation | Persist branch-keyed local review state to /memories/session/review-state-{ID}.md with review mode and prosecution/defense/judgment booleans before PR creation when the branch exposes an issue ID. | No durable Claude-local equivalent before PR creation; review commands may consume the same branch-keyed shape only when the active conversation has the session-memory file available, otherwise re-enter missing review stages. | partial - pre-PR review-state is branch-keyed session state and not a durable cross-tool artifact. #379 follow-up/cross-link needed for any cross-tool pre-PR resume story. | Citations: review-state persistence, review reconciliation. |
| SMC-06 | post-PR review-state resume | durable; session memory is a final fallback | Resume review completion from the durable review comment first, then PR-body <!-- pipeline-metrics -->, then /memories/session/review-state-{ID}.md. | Same durable PR comment and PR-body lookup; session memory is optional fallback only when the surface has it. | yes - durable PR artifacts are cross-tool and latest durable evidence wins. | Citations: review-state persistence, review reconciliation, pipeline metrics schema. |
| SMC-07 | run-once startup-check marker | within-conversation:hooks; inline surfaces may have an honest gap | Write /memories/session/session-startup-check-complete.md after the automatic startup detector runs; fail open if session memory cannot be read or written. | Hook-driven Claude startup shares the run-once intent, but inline/headless command paths may lack a reliable session-memory write surface and must say so. | partial - hook path is bounded to the conversation, inline/headless gaps are not fungible. #379 follow-up/cross-link needed for cross-surface startup semantics. | Citations: session-startup, README hook note, CUSTOMIZATION startup note. |
| SMC-08 | phase-completion markers | durable | Use GitHub issue comments such as <!-- experience-owner-complete-{ID} -->, <!-- design-phase-complete-{ID} -->, <!-- plan-issue-{ID} -->, and <!-- design-issue-{ID} --> for smart resume and D9 durable handoff. | Same GitHub markers; /orchestrate checks them before dispatching Code-Conductor. | yes - GitHub markers are the shared cross-tool resume surface. | Citations: Code-Conductor smart resume, /orchestrate, CLAUDE handoffs. |
| SMC-09 | calibration snapshots | per-dispatch; durable only after inclusion in PR-body metrics | Capture aggregate-review output and prosecution-depth decisions during the review cycle; PR bodies persist the selected summary through <!-- pipeline-metrics --> when a PR is created. | Same scripts and PR-body metrics are available when Claude runs the workflow, but raw command output is not a shared state store. | partial - raw snapshots are per-dispatch; PR-body metrics are durable. #379 follow-up/cross-link needed for raw calibration snapshot handoff expectations. | Citations: review reconciliation, pipeline metrics schema, aggregate-review-scores. |
| SMC-10 | per-finding calibration cache | within-worktree | Write per-finding entries and re-activation events to .copilot-tracking/calibration/review-data.json through write-calibration-entry.ps1 or backfill tooling. | Same local worktree file when Claude is operating in the same checkout; otherwise reconstruct from PR-body pipeline metrics or skip local optimization. | partial - same-worktree cache is reusable across Copilot and Claude; PR-body metrics are required for durable or fresh-checkout handoff. | Citations: calibration-pipeline, write-calibration-entry core, tracking-format. |
| SMC-11 | cross-PR calibration state | within-worktree | Aggregate scripts update derived state in .copilot-tracking/calibration/review-data.json, including prosecution depth, re-activation events, complexity history, and proposal tracking. | Same local calibration file and scripts when the worktree is shared; otherwise use GitHub PR bodies as the durable raw source and rebuild. | partial - same-worktree derived state is reusable across Copilot and Claude; GitHub PR metrics are the durable rebuild source for fresh checkouts. | Citations: aggregate-review-scores, create-improvement-issue core, pipeline metrics schema. |
| SMC-12 | plugin release-hygiene decision | within-worktree:hooks; within-conversation:hooks when the hook payload provides session_id | Store the scoped decision in .claude/.state/release-hygiene-{slug}.json; Copilot normally keys by branch slug when no session ID exists. | Store the same decision file through the Claude PostToolUse hook, preferring session_id and falling back to branch slug or session fallback. | partial - both surfaces use the same state-file shape, but keying can diverge (session_id versus branch slug); silence is shared only when both resolve the same key. | Citations: plugin-release-hygiene, Copilot platform note, Claude platform note. |
| SMC-13 | .copilot-tracking/ artifacts | within-worktree | Store local research, specification, archived tracking, and calibration artifacts under .copilot-tracking/; do not use this directory for session-memory plan files. | Claude shells may write the same local research/spec artifacts when running in the shared checkout; cloud or fresh-branch agents cannot read them unless they are copied or committed elsewhere. | partial - same-worktree artifacts are reusable; use GitHub issues or committed docs for durable fresh-checkout or cross-agent handoff. | Citations: tracking-format, Research-Agent, Specification, session cleanup detector. |
| SMC-14 | subagent-env-handshake state | per-dispatch | n/a; Copilot subagent dispatch does not use this Claude environment-handshake carrier. | Prepend a <!-- subagent-env-handshake v1 --> prompt block with parent HEAD, branch, cwd, dirty fingerprint, workspace mode, and timestamp; the subagent verifies live state before tree-grounded claims. | n/a | Delegated/informational note: this row delegates the schema and match/mismatch/error behavior to subagent-env-handshake; the state is prompt-carried and intentionally not persisted. |
| SMC-15 | rate-limit deferred work state | within-conversation | When a rate-limited subagent call defers remaining work and vscode/memory is available, write /memories/session/rate-limit-deferred-{scope}.md with deferred findings/work items, interrupted phase/step, and resume point. | Claude surfaces that can read/write /memories/session may use the same bounded payload; inline/no-write Claude cannot persist it and must carry deferred items in visible conversation or handoff text instead. | partial - same-conversation/session-memory payload is not cross-tool or cross-session; durable plan/PR/issue context can restart the phase but does not preserve the pending payload. | Citations: parallel-execution error handling, code review D38 rationale, and session-memory contract rationale. This row catalogs a bounded state shape only; it is not a durable fallback or new persistence mechanism. |
| SMC-16 | review-judge-produced sentinel | durable | Copilot judge runs post <!-- review-judge-produced-{PR} --> as a PR comment immediately after the judge ruling finalizes and before pipeline-metrics persistence. Idempotency: check gh pr view {PR} --json comments before writing; skip if already present. | Claude judge runs post the same sentinel via gh pr comment {PR} --body '<!-- review-judge-produced-{PR} -->' with the same idempotency check. The sentinel is separate from the judge-rulings YAML comment and must be written first (ordering: sentinel → judge-rulings). | yes - both Copilot and Claude judge runs write this sentinel; Code-Conductor reads it via the warn-only hook synthesis path to detect "review completed but credit not yet written." | Citations: review-judgment skill, frame-credit-ledger-core.ps1 (Test-ReviewSentinelPresent, Resolve-NotPersistedSynthesis). Governed by this row (SMC-16). |
| SMC-17 | credit-input deferred-emission marker | durable | Pipeline-entry agents (Experience-Owner, Solution-Designer, Issue-Planner) and Code-Conductor (for the orchestration port) write <!-- credit-input-{port}-{ID} --> as an issue comment immediately after posting their completion marker. Payload: a single yaml fenced block carrying { port, adapter, evidence } matching the corresponding Build-*CreditRow parameter list. | Same GitHub issue-comment write via gh issue comment {ID} --body .... Code-Conductor reads these markers at PR-creation time by scanning gh issue view {ID} --json comments --paginate, parses the YAML payload, calls the matching Build-*CreditRow, and emits the credit row into the PR body's pipeline-metrics credits[] block. Read-after-write retry: up to 3 times with 1s exponential backoff if the credit-input marker is absent after the paired completion marker for the same port is present (e.g., <!-- experience-owner-complete-{ID} --> for experience, <!-- design-phase-complete-{ID} --> for design, <!-- plan-issue-{ID} --> for plan, <!-- engagement-record-orchestration-{ID} --> for orchestration). | yes - GitHub issue-comment is the shared cross-tool durable artifact; Code-Conductor on both platforms harvests the same comment thread via gh CLI. | Citations: frame-credit-ledger-core.ps1 (Invoke-CreditInputHarvest), Code-Conductor, CLAUDE.md cross-tool markers. Governed by this row (SMC-17). Port set: experience, design, plan, orchestration. Payload survival: durable; retry state: within-conversation. |
| SMC-18 | cost-collection install-prompt suppression key | session (within-conversation; survives Copilot compaction when /memories/session/ is preserved) | Write any non-empty value to /memories/session/cost-collection-install-prompt-{repo-cwd} via vscode/memory after the user responds to the prompt; check the key with vscode/memory view before each specialist dispatch and skip the prompt if set. Failure path on vscode/memory unavailable: fall back to one-prompt-per-session (no suppression — the prompt may fire on every dispatch within the session, but the workflow is not blocked). | n/a — Claude orchestration skips the Copilot cost-collection pre-flight entirely; this key is never read or written by Claude paths. | n/a — Copilot-only by design D9 | Citations: Code-Conductor Hub Execution Workflow item 3, copilot-cost-collection skill. Key shape: cost-collection-install-prompt-{repo-cwd} where {repo-cwd} is the absolute workspace root path. Governed by this row (SMC-18). Added in issue #514 Step 6. |
| SMC-19 | design finding-dispositions marker payload | durable | Store finding_dispositions: only inside the <!-- design-phase-complete-{ID} --> issue-comment marker. Shape: a single yaml fenced block with schema_version: 1, passes_run, and entries[] carrying finding_id, pass, disposition, classification, disposition_rationale, optional artifact_citation, and optional also_flagged_by. Copilot resume reads the SMC-08 design completion marker and preserves the block when updating the marker. | Same GitHub issue-comment marker and YAML shape. Claude resume reads the SMC-08 design completion marker and preserves the block when updating the marker. Do not mirror this payload into <!-- credit-input-{port}-{ID} --> markers. | yes - the GitHub issue-comment marker is the shared durable resume surface, and the same payload shape is read by both platforms. | Citations: solution-authoring disposition gate, design disposition audit tests, phase-completion markers row SMC-08. Governed by this row (SMC-19). Payload survival: durable; cross-tool fungibility: yes. |
| SMC-20 | engagement-record marker payload | durable | Upstream agents (Experience-Owner, Solution-Designer, and Issue-Planner) write <!-- engagement-record-{phase}-{ID} --> as an issue comment alongside their phase-completion marker. Payload: single yaml fenced block with schema_version: 2, phase, capture_session, load_bearing_decisions[]. Multiple markers per (phase, issue) are allowed; latest-createdAt wins on read. Note: the orchestration phase uses schema_version: 3 and is written by Code-Conductor (not an upstream agent) immediately after scope-classification resolves. | Same GitHub issue-comment write via gh issue comment {ID} --body .... Resume read via Read-EngagementRecords from .github/scripts/lib/frame-engagement-record-core.ps1 — consumed by solution-authoring's same-decision-resume skip rule at upstream phase re-entry. Helper uses powershell-yaml; gh query preserves createdAt. | yes - GitHub issue-comment is the shared cross-tool durable artifact; both platforms read via the same helper. | Citations: engagement-record-emission, solution-authoring same-decision-resume, frame-engagement-record-core.ps1 (Read-EngagementRecords). Governed by this row (SMC-20). Port set: experience, design, plan, orchestration, review. Note: the review phase is PR-keyed; it uses -PullRequestNumber on the read helper and writes to PR comments rather than issue comments. Governed by SMC-23. Write path active per #576; read path active per #575. Payload survival: durable; cross-tool fungibility: yes. |
| SMC-21 | gate-decision event log (L0 tokens + L1 events) | within-conversation (session memory: memories/session/gate-events-{key}.jsonl); fallback within-worktree (.copilot-tracking/gate-events.jsonl) | Agents emit L0 gate-decision tokens at each classification-gate decision point (solution-authoring gate); the PostToolUse hook appends L1 corroboration events. The L2 reconciliation validator (gate-reconciliation-core.ps1) reads this log at review time. Schema: skills/solution-authoring/schemas/gate-decision-token.schema.json. Key derivation: Resolve-GateSessionKey in skills/solution-authoring/scripts/gate-event-logger-hook.ps1 (session_id → branch-slug → sha fallback). | L0 tokens: agent-written (no separate cross-tool contract — tokens are emitted by the active agent on either platform using the same schema). L1 events: hook-written via PostToolUse on Claude (AskUserQuestion) and conditionally on Copilot (vscode/askQuestions — platform-confirmed in issue #617 s1). The log path and key-resolution strategy are shared. | partial — L0 tokens are platform-neutral; L1 hook events depend on PostToolUse support for the structured-question tool on each platform (L1 hook on Claude: designed for AskUserQuestion (PostToolUse); empirical confirmation pending (spike artifact not produced in #617 s1); conditional for Copilot per vscode/askQuestions per #617 s1). | Citations: gate-decision-token schema, gate-event-logger-hook.ps1, gate-reconciliation-core.ps1, issue #617. Governed by this row (SMC-21). Added in issue #617. |
| SMC-22 | reference pre-flight run-once marker | within-conversation:hooks; inline/headless path may lack a reliable session-memory write surface — fail open (run the loader) if the marker cannot be read | Write the (issue, conversation) body-hash-based skip key after the first reference pre-flight injection for a given (issue, conversation) pair; on a second prompt for the same issue in the same conversation, skip re-injection unless the issue-body hash has changed (two-phase check: Phase-1 loads prior marker state — no short-circuit, gh fetch follows unconditionally; Phase-2 compares stored body_hash against freshly fetched hash and skips only when equal). "Conversation" is realized as session_id from the hook payload; when session_id is absent the hook falls back to 'unknown', which means all prompts without a session ID share one marker file (known 'unknown'-session collision caveat). The run-once gate is implemented in reference-preflight-hook.ps1 via the Claude UserPromptSubmit hook. | n/a — Copilot does not use the UserPromptSubmit hook for reference pre-flight; the hook path is Claude-only. Copilot surfaces rely on the upstream-onboarding skill's Project Reference Loading step to invoke the loader directly. | n/a — Claude-only hook path by design | Citations: project-references SKILL.md §Sentinel (defines the canonical <!-- refs-injected-{issue} --> sentinel grammar); upstream-onboarding SKILL.md (sentinel-detect/defer step). Honest gap: the inline/headless path may have no reliable session-memory write surface; the hook must fail open and run the loader rather than silently skipping injection. This row documents the run-once marker contract only — it does not introduce a new persistence mechanism (no-new-mechanism rule, Rule 4). Governed by this row (SMC-22). Added in issue #647. |
| SMC-23 | review-phase engagement-record + review-dispositions marker pair | durable | Write <!-- engagement-record-review-{PR} --> and <!-- review-dispositions-{PR} --> as PR comments after the judge verdict resolves. Payload: engagement-record uses schema_version: 4, phase: review, PR-keyed (not issue-keyed). review-dispositions payload uses schema_version: 1, passes_run, entries[] with stable_finding_key. Multiple markers per PR allowed; latest-createdAt wins on read. | Same PR-comment write via gh pr comment {PR} --body .... Resume read for engagement-record via Read-EngagementRecords -PullRequestNumber {PR} -Phase review; resume read for dispositions via dedicated review-dispositions validator (see S4). | yes - GitHub PR comment is the shared durable cross-tool artifact; both platforms read via the same helper and PR comment thread. | Citations: engagement-record-emission (amended #655 S3), frame-engagement-record-core.ps1 (PR-aware path, #655 S2), solution-authoring disposition gate. Governed by this row (SMC-23). Added in #655 S3. Payload survival: durable; cross-tool fungibility: yes. |
