peaks-loop 4.0.7 → 4.0.8

package/CHANGELOG.md

@@ -1,294 +1,52 @@
 # Changelog
 
-## 4.0.7 — 2026-08-02 (dogfood surface repairs on `ice-cola`)
-
-A 24h-mode dogfood pass on the downstream `ice-cola` monorepo (4
-sub-packages: admin / server / client / hermes-agent) surfaced 25 real
-CLI / runtime / documentation defects across peaks-loop 4.0.6, plus a
-meta-level flow bug (the LLM bypassed the peaks-code / peaks-rd /
-peaks-qa flow and routed 22 files / 632 lines of `Edit` calls
-directly). This release closes all 4 P0/P1 ship-blockers, the 5
-P2 batch fixes, the find-skills integration, and 4 PR-meta
-enforcement-layer fixes.
-release closes the 5 P0/P1 ship-blockers and reshapes SKILL.md's
-Drift Index. 4 P2 changes were documented in the changeset but only
-the documentation half (Drift Index refresh) ships in 4.0.7; the
-implementation half (monorepo-aware language detection, monorepo
-sub-agent prompt, slice check monorepo typecheck) is queued for 4.0.8.
-
-### P0 — `peaks audit red-lines` no longer reports false-positive enforcerRef orphans on consumer projects
-
-- `src/services/audit/backing-detector.ts` and
-  `src/services/audit/enforcers/lint-audit-regression.ts` now resolve
-  `enforcerRef` paths against the peaks-loop source root (resolved via
-  `import.meta.url` + upward walk to `package.json#name === 'peaks-loop'`),
-  with an explicit `peaksLoopRoot` override for tests. Pre-rid every
-  downstream audit reported all 26 enforcer files as "missing on disk"
-  (88 enforcerFindings on ice-cola). Post-rid: 0.
-- New `resolvePeaksLoopRoot()` exported helper.
-- Tests: `tests/unit/audit/backing-detector-resolve-root.test.ts` (8
-  cases including the ice-cola repro).
-
-### P0 — `peaks code {detect-job,read-job-shape}`, `peaks workflow plan read`, and `peaks route` now resolve the canonical session id
-
-- New shared resolver `resolveActiveSessionId(projectRoot, override?)`
-  in `src/services/session/session-manager.ts`, exported via
-  `src/services/session/index.ts`. Composes the existing
-  `getSessionIdCanonical` + `getSessionId` fan-out so the same
-  `sessionId` flows through all 4 CLIs.
-- `src/cli/commands/code-job-shape-commands.ts` and
-  `src/cli/commands/code-runtime-commands.ts` now use the shared
-  resolver instead of the per-file `getSkillPresence` helper (which
-  read `.peaks/.active-skill.json` — a different store from
-  `.peaks/_runtime/session.json`).
-- Pre-rid the 4 CLIs reported `NO_ACTIVE_SESSION` for any session
-  created via `peaks workspace init` that never had
-  `peaks skill presence:set peaks-code` called on it (the common
-  case for downstream consumer projects and 24h-mode sessions).
-- Tests: `tests/unit/session/resolve-active-session.test.ts` (7 cases).
-
-### P1 — `peaks code should-pause` no longer false-positives in 24h-mode
-
-- `src/cli/commands/code-mode-gate-commands.ts` short-circuits the
-  stale-presence check when `.peaks/_runtime/<sid>/24h-state.json`
-  reads `state === '24H_ACTIVE'`. Without this, every 24h-mode
-  session hit a `shouldPause: true` wall at Step 1 even though
-  24h-mode is explicitly designed to be a no-AskUserQuestion mode.
-- New local helper `is24hActive(projectRoot, sessionId)` reuses the
-  existing `read24hState` from `services/24h-mode/store.ts`.
-- Tests: `tests/unit/code/should-pause-24h-bypass.test.ts` (9 cases).
-
-### P2 #6 (enhancement) — `peaks standards {init,update} --suggest-skills` integrates find-skills
-
-- New `--suggest-skills` flag on `peaks standards init` and
-  `peaks standards update` (off by default). When set, peaks-loop
-  runs `npx skills find <query>` for each query derived from the
-  detected ProjectContext (component library, build tool, CSS
-  framework, notable deps, language) and emits the top-5 results
-  in `nextActions` as copy-paste `npx skills add` commands.
-
-- Per user direction 2026-08-02: **no hardcoded verified-owner
-  whitelist**. The service runs `npx skills find` with no
-  `--owner` filter so the registry / leaderboard decides the
-  ranking (this is exactly the anti-pattern find-skills
-  SKILL.md Step 4 warns against — "do not recommend based solely
-  on a hardcoded list; verify with install count + source
-  reputation"). Recommendations are sorted by install count desc
-  so the user sees the same top results they would see running
-  `npx skills find` manually.
-
-- The service NEVER calls `npx skills add` itself. Installation
-  is gated on the user passing `--suggest-skills` (off by
-  default) and the install command is emitted as a single shell
-  snippet the user reviews before pasting. The CLI caller owns
-  the gating.
-
-- Failure mode: if `npx skills find` fails (network / registry
-  down), the service silently degrades — init/update still
-  completes, `nextActions` shows a "no matching skills found"
-  hint, no error. The user can re-run with `--suggest-skills`
-  later.
-
-- New file: `src/services/standards/find-skills-integration.ts`.
-  Tests: `tests/unit/standards/find-skills-integration.test.ts`
-  (12 cases covering queriesForContext, parseFindOutput,
-  findSkillsForContext — all using a custom `SkillFindRunner`
-  injection so the test never hits the network).
-
-### P2 batch — 5 monorepo / sub-agent prompt fixes (all in this release)
-
-- **`peaks standards` / `detectLanguage` is monorepo-aware** (`project-standards-service.ts`).
-  A monorepo root that has no `tsconfig.json` (only `tsconfig.base.json` + per-package
-  `tsconfig.json`) is now classified as `typescript` when any sub-package in
-  `packages/<name>/` has its own `tsconfig.json`. Pre-rid ice-cola (4-package
-  TypeScript monorepo) was misclassified as `javascript` because the root scan
-  saw no `tsconfig.json` and the root `package.json#devDependencies` had
-  `peaks-loop` only (a `javascript` standards pack).
-
-- **`peaks scan archetype` is monorepo-aware** (`archetype-service.ts`).
-  A 1-level walk into `packages/<name>/` merges each sub-package's
-  `dependencies` / `devDependencies` / `peerDependencies` /
-  `optionalDependencies` into the framework-detection map. Ice-cola
-  now correctly reports `hasBackendFramework: true, backendFrameworks:
-  ["@nestjs/core", "@nestjs/common"]` instead of
-  `hasBackendFramework: false`.
-
-- **`peaks sub-agent dispatch` prompt includes a monorepo branch**
-  when `<projectRoot>/pnpm-workspace.yaml` is present. The pre-rid
-  static prompt had no monorepo handling, so sub-agents ran
-  `pnpm test` at the root which fanned out to every sub-package
-  (36-minute wall clock for a single-slice change). The new block
-  tells the sub-agent to scope to one sub-package via
-  `pnpm --filter @<scope>/<name> test <pattern>`.
-
-- **`peaks slice check` typecheck stage is monorepo-aware**
-  (`slice-check-service.ts`). When `pnpm-workspace.yaml` is
-  present, the typecheck stage runs `pnpm -r typecheck` first and
-  falls back to `pnpm -r --parallel exec tsc --noEmit` if no
-  per-package `typecheck` script exists. Per-package failures
-  are captured in `data.failedPackages` so the operator can see
-  which sub-package broke (the pre-rid "tsc exited with code 1"
-  was a 2ms fake-fail with no actionable detail).
-
-- **`peaks sub-agent dispatch` context window block no longer
-  misleads on fallback probes** (`build-dispatch-system-prompt.ts`).
-  When the probe source is `conservative-fallback` (or any other
-  untrusted value), the block short-circuits to "no probe
-  available — treat the displayed ratio as unverified" instead
-  of rendering "0.0% used (100.0% free)" as if it were a real
-  measurement. Trusted sources are `token-counted`,
-  `transcript-estimate`, and `statusline`; anything else triggers
-  the fallback path.
-
-### P1 — SKILL.md Drift Index refreshed for 4.0.6+
-
-- D-001 rewritten (the pre-4.0.7 entry was the inverse of 4.0.6's
-  actual behavior — `peaks code detect-job` requires `--is-job`).
-- New D-013: `peaks code context-now --json` requires `--project`.
-- New D-014: documents the 4-CLI `NO_ACTIVE_SESSION` regression fixed
-  by P0 above.
-- New D-015: documents the 24h-mode ↔ stale-presence interaction fixed
-  by P1 above.
-- Step N+2 probe primitive example now includes `--project <path>`.
-
-### Compatibility
-
-- All command names, options, and exit codes are preserved.
-- Auto-compact 0.85 / 0.95 contract unchanged.
-- `peaks audit red-lines` on peaks-loop itself shows 0 orphan findings
-  (it had 88+ before the fix; now also on every consumer project).
-- `peaks code detect-job` / `read-job-shape` accept the same flags
-  as 4.0.6.
-
-### How to verify
-
-```bash
-# Inside peaks-loop source root (after `pnpm build`):
-peaks audit red-lines --project . --json
-# expect: enforcerFindings: 0
-
-# Inside a downstream project that has peaks-loop as a devDep:
-peaks audit red-lines --project . --json
-# expect: enforcerFindings: 0 (was 88+ before)
-
-# 24h-mode + should-pause:
-peaks session 24h-mode transition --state 24H_ACTIVE
-peaks code should-pause --step step-1-mode-select --json
-# expect: shouldPause decision is NOT "stale-presence"
-
-# detect-job CLI:
-peaks code detect-job --is-job false --rationale "x" --suggested-job-id n-a
-# expect: ok, recorded to .peaks/_runtime/<sid>/job-shape.json
-```
+## 4.0.8 — 2026-08-03 (presence-lease-graph)
+
+**BREAKING: IdeAdapter interface requires `resolveCallerId(env?)`**. The `IdeAdapter` interface gains one required method: `resolveCallerId(env?: NodeJS.ProcessEnv) => string`. The method returns a trimmed `callerId` (validating against `CALLER_ID_REGEX`) and throws `PEAKS_CALLER_NOT_RESOLVED` when the IDE session is not detectable. **4.0.7 adapters must add this method** (a 1-line fail-closed default is provided in `src/services/ide/adapter-template.ts` if you need a starter). Slice 4.0.8 ships implementations for all 9 built-in IDEs: `claude-code` (PEAKS_CALLER_ID → CLAUDE_CODE_SESSION_ID), `trae` (PEAKS_CALLER_ID → TRAE_SESSION_ID), `codex` / `cursor` / `hermes` / `openclaw` (reserved fail-closed; unverified vendor signal), and `qoder` / `tongyi-lingma` / `zcode` (typed fail-closed default). The `PLATFORM_FALLBACKS` table is **DELETED** in 4.0.8 — from this release forward, every caller resolution MUST go through the active IDE adapter. Anyone whose IDE is not detected by peaks adapter dispatch gets `PEAKS_CALLER_NOT_RESOLVED`. This is the desired product contract (vendor-neutral).
+
+**BREAKING: dispatch record schema v3.2 → v4.0.0**. The persisted dispatch record gains three new fields: `workflowId: string | null`, `graphNodeId: string | null`, `graphRef: string | null`. These are the graph-binding triple that ties a sub-agent dispatch to a prepared workflow node. **Back-compat readers** that pin the on-disk shape must update to handle the new optional fields; readers that ignore unknown fields are unaffected. The `version` literal narrows from `'3.2'` to `'4.0.0'`. The envelope writer `markCompleted` automatically transitions the bound graph node to `envelope-received` with `ackStatus=pending` once the artifact/envelope ↔ `dispatchRef` binding is validated, so the parent ack protocol is observable from the dispatch record itself. The `peaks sub-agent dispatch` CLI gains the required `--graph-node <id>` option (rejects missing / wrong-kind with `PEAKS_GRAPH_NODE_REQUIRED` / `PEAKS_GRAPH_NODE_KIND_INVALID`).
+
+**24h mode `inFlightBatch` is now graph-backed** (RD §3 D4d). The production `inFlightBatch` signal in `auto-compact-orchestrator.ts` now calls `workflow-inflight-probe.probeInflightBatch()` (which reads the canonical graph store). The legacy `--in-flight-batch` CLI boolean is preserved as a TEST-ONLY seam gated by `process.env.PEAKS_TEST_SEAM === '1'`; a production run never consults the boolean as truth. The pure decision function `evaluateAutoCompactDecision` retains the boolean signature for the test seam and the red-line override (≥ 95% is still a synchronous hard-gate, regardless of in-flight state).
+
+**`peaks skill presence:set` and `presence:clear` are fail-closed**. `presence:set` now refuses any write when no Peaks session is bound (`PEAKS_SESSION_NOT_BOUND`) or the active IDE adapter cannot resolve a valid callerId (`PEAKS_CALLER_NOT_RESOLVED`). The compat shim `setSkillPresence` is preserved for legacy statusline / hook / dashboard consumers; it routes through `presence-lease-service.setPresenceLease` when a session is bound. `presence:clear` no longer performs a raw unlink — workflow-bound leases route through `terminalizeWorkflow` so the graph terminal node, the lease, the caller index, and one observability event are all updated in one lifecycle lock (RD §3 D4c + DR). The compat shim still removes the legacy `active-skill.json` so a stale marker from a prior CLI version cannot resurrect; the canonical lease + index entries are not touched by the shim.
+
+**`peaks skill lease gc --project <p>` is the manual lease sweep primitive** (RD §4 D4c). The GC predicate is `now - lastHeartbeat > 1h AND now - startedAt > 24h30m` (24h = peaks-loop "24h AI 编排器" product contract; 30min = boundary tolerance, not safety buffer). GC runs on `presence:set`, `peaks workspace init`, and the manual `peaks skill lease gc` CLI. Corrupt graphs surface as `PEAKS_GRAPH_REF_BROKEN` warnings and are excluded from removal. A follow-up workflow reclaims a cleared lease explicitly.
+
+**Canonical presence lease + workflow graph are the source of truth** (RD §2 + §3). The 4.0.7 singleton `active-skill.json` and per-caller `active-skill-<callerId>.json` files are LEGACY READ INPUTS only. The canonical layout is:
+
+| Path under `.peaks/_runtime/<sessionId>/` | Purpose |
+|---|---|
+| `graphs/<workflowId>.json` | Canonical workflow graph |
+| `leases/presence-<callerId>-<workflowId>.json` | Canonical caller/workflow presence lease |
+| `presence-index/<callerId>.json` | Additive read index (no lifecycle fields) |
+| `migrations/presence-v1.json` | Idempotent reconcile receipt |
+
+Core presence / graph services contain **zero vendor env var lookups**: `CLAUDE_CODE_SESSION_ID | TRAE_SESSION_ID | CURSOR_SESSION_ID | CODEX_SESSION_ID | HERMES_SESSION_ID | OPENCLAW_SESSION_ID` never appear in `src/services/{skills,workflow,code}/**`. The 4.0.7 hard-ban on `require('node:...')` in `src/services/**` is preserved (verified by the audit grep below).
+
+### Anti-fake-green verification
+
+1. `rg "require\(['\"]node:" src/services/` — 0 hits.
+2. `rg "CLAUDE_CODE_SESSION_ID|TRAE_SESSION_ID|CURSOR_SESSION|CODEX_SESSION|HERMES_SESSION|OPENCLAW_SESSION" src/services/skills/ src/services/workflow/` — 0 hits in non-adapter code.
+3. `rg "PLATFORM_FALLBACKS" src/services/` — 0 hits.
+4. Production ESM repro: `node -e "import('./dist/src/services/code/auto-compact-orchestrator.js').then(m => console.log(m.evaluateAutoCompactDecision({ratio: 0.86, inFlightBatch: { hasInFlightBatch: true }})?.action))"` → `'defer'`. (Production now treats `inFlightBatch: true` as a graph-backed signal from `probeInflightBatch`, NOT a CLI boolean. A `defer` at 0.86 closes the 4.0.4 24h偶发 auto-compact-bug.)
+5. Production ESM repro: `node -e "import('./dist/src/services/skills/presence-lease-service.js').then(m => console.log(typeof m.setPresenceLease, typeof m.gcStalePresenceLeases))"` — both functions exported and runtime-resolvable.
+6. Production ESM repro: `import presence-lease-service` with `callerId: ''` and no session → `PEAKS_CALLER_NOT_RESOLVED` (or `PEAKS_SESSION_NOT_BOUND`) thrown BEFORE any filesystem write.
+
+### Locked acceptance gate (13 QA test files, all green in 4.0.8)
 
-Source: `.peaks/memory/2026-08-02-ice-cola-dogfood-surface-probe.md`.
-
-### PR-meta batch — flow-level enforcement (4 fixes addressing why the LLM bypassed peaks-code in this same session)
-
-The 4.0.7 dogfood pass surfaced a flow-level bug that the 25
-P0/P1/P2 fixes alone could not close: the LLM routed 22 files /
-632 lines of `Edit` calls directly without a single
-`peaks sub-agent dispatch rd`. Six root causes were identified
-(internal-only debug report, 2026-08-02); the four below close
-the four most actionable layers with surgical changes.
-
-- **PR-meta-1: Edit-enforcement hook** (new
-  `src/services/hooks/pre-tool-edit-enforcement.sh`).
-  Opt-in via `peaks hooks install --with-edit-enforcement` (off by
-  default to preserve the existing peaks-code behavior; the gate
-  is a HARD layer, not a soft warning). When the hook fires on
-  an `Edit` / `Write` / `MultiEdit` / `NotebookEdit` call
-  targeting `src/**`, it checks for an active RD artifact under
-  `.peaks/_runtime/<sid>/rd/requests/` and either allows the
-  call (RD exists) or denies with a structured
-  `permissionDecision: deny` envelope that points the LLM at the
-  right next step (`peaks request init` + `peaks sub-agent dispatch
-  rd`). Bypass conditions: tests / docs / RD artifacts / the
-  hook scripts themselves, a `.peaks/standards/edit-bypass` file
-  (gitignored escape hatch for hot-fixes), or the env var
-  `PEAKS_EDIT_BYPASS_24H=1` (24h-mode opt-in).
-
-- **PR-meta-2: 24h mode scope explicit** (SKILL.md §"24h mode
-  explicit scope"). 24h mode is `peaks session 24h-mode
-  transition --state 24H_ACTIVE`. The pre-PR-meta-2 prose was
-  implicit ("bypass AskUserQuestion") and the LLM over-extended
-  it to **all** user instructions, including the Code-Change
-  Red Line. The new section enumerates exactly which 11 steps
-  24h mode auto-proceeds at (mode select / step confirm / swarm
-  pick / QA verdict / etc.) and which 6 rules it does **not**
-  bypass (Code-Change Red Line, sub-agent dispatch, worktree
-  authorization, request state machine, external side effects,
-  2.x → 1.x reverse migration). The single-sentence rule is
-  reproducible at the top of the section.
-
-- **PR-meta-3: scope-counter fail-LOUD** (new
-  `src/services/hooks/pre-tool-scope-counter.sh`). The
-  harness-side `SCOPE WARNING: 27 files modified` was
-  informational noise that the LLM learned to ignore
-  (`.peaks/memory/2026-07-28-sub-agent-visibility-issue.md`
-  documents the same friction). PR-meta-3 turns the warning
-  into a checkpoint: the hook counts cumulative
-  application-source edits per session in
-  `.peaks/_runtime/<sid>/edit-counter.json` and emits a
-  fail-LOUD reflection reminder at thresholds 5, 10, 20. The
-  LLM cannot continue without writing to
-  `.peaks/_runtime/<sid>/scope-reflection.md` once a
-  threshold is hit. Off by default; opt in via
-  `peaks hooks install --with-scope-counter`.
-
-- **PR-meta-4: dispatch `--emit-bash-script`** (new flag on
-  `peaks sub-agent dispatch`). The dry-run architecture is
-  preserved (the CLI is still the canonical dispatch surface),
-  but the LLM no longer has to parse `toolCall` args from the
-  JSON envelope and re-execute them via the Agent tool. The
-  flag emits a ready-to-exec bash script alongside the
-  envelope; the LLM runs the script via the Bash tool and
-  the dispatch fires immediately. The script invokes the
-  canonical `peaks sub-agent exec` surface, not a side-step.
-- **PR-meta-5: `peaks hooks install --with-edit-enforcement /
-  --with-scope-counter`** (slice 4.0.7). The two opt-in hook
-  entries added in PR-meta-1 / PR-meta-3 are now reachable via
-  the standard install flow. Default behavior is unchanged
-  (gate-enforce only); the flags activate the meta-layer
-  hooks. The summary envelope's `entries` array now reflects
-  the actual installed shape (gate-enforce + opt-in entries)
-  so operators can dry-run + verify before applying.
-- **PR-meta-6: `peaks sub-agent exec`** (new sub-command).
-  Companion to PR-meta-4's `--emit-bash-script`. The script
-  emitted by the dispatch CLI invokes this surface; `exec`
-  reads the dispatch record from disk and re-emits the
-  canonical `toolCall` envelope (envelopeVersion 2.4.0 with
-  `viaExec: true`). Idempotent: the same exec call can be
-  replayed any number of times. Mismatch detection: when the
-  caller-passed session-id / request-id / batch-id / role do
-  not match the record, `exec` emits a warning but still uses
-  the record as the canonical source of truth. Failure modes:
-  `DISPATCH_RECORD_MISSING`, `DISPATCH_RECORD_INVALID`,
-  `DISPATCH_RECORD_NO_TOOL_CALL`. Tests: 3 cases in
-  `tests/unit/commands/sub-agent-exec.test.ts`.
-- **PR-meta-7: scope-counter fail-CLOSED**. The PR-meta-3
-  scope counter emitted `additionalContext` (soft signal);
-  the LLM continued editing without writing the reflection
-  file. PR-meta-7 hardens the checkpoint: at thresholds 5 /
-  10 / 20, the hook now emits `permissionDecision: deny`
-  until the LLM writes a non-empty reflection file at
-  `.peaks/_runtime/<sid>/scope-reflection.md`. The next
-  threshold requires a fresh reflection. Bypass: empty file
-  at `.peaks/standards/scope-counter-bypass` (gitignored
-  escape hatch).
-
-### Compatibility
-
-- `peaks hooks install` default behavior is unchanged. The
-  meta-1 / meta-3 hooks are opt-in (`--with-edit-enforcement`,
-  `--with-scope-counter`); the meta-2 SKILL.md section is
-  documentation-only; the meta-4 flag is opt-in
-  (`--emit-bash-script`).
-- All command names, options, and exit codes are preserved.
-- Auto-compact 0.85 / 0.95 contract unchanged.
-- 24h mode scope is **narrowed**, not widened: same 11
-  auto-proceed steps, but the previously-implicit bypass is
-  now explicitly bounded to "AskUserQuestion gates" only.
+- `tests/unit/skills/presence-lease-service.test.ts` — TC-SM-01..08, TC-SM-12 + TC-AG-01/04/05
+- `tests/unit/workflow/workflow-graph-store.test.ts`
+- `tests/unit/workflow/workflow-state-machine.test.ts` — TC-SM-01..12 + TC-AP-01..07
+- `tests/unit/workflow/workflow-inflight-probe.test.ts` — TC-IF-01..09
+- `tests/integration/workflow-presence-lease-lifecycle.test.ts`
+- `tests/integration/workflow-node-ack-protocol.test.ts`
+- `tests/integration/sub-agent-graph-binding.test.ts`
+- `tests/integration/sub-agent-graph-heartbeat.test.ts`
+- `tests/integration/skill-presence-lease-gc.test.ts`
+- `tests/integration/workspace-reconcile-presence-leases.test.ts`
+- `tests/integration/session-24h-graph-inflight.test.ts` — TC-IF-01..09 + TC-AG-06/07
+- `tests/integration/workflow-terminalize-atomicity.test.ts`
+- `tests/integration/ide-caller-resolution.test.ts`
 
 ## 4.0.6 — 2026-08-02 (postinstall auto-register outputStyle)
 

package/dist/cli/commands/code-job-shape-commands.js

@@ -10,6 +10,7 @@ import { addJsonOption, getErrorMessage, printResult } from '../cli-helpers.js';
 import { fail, ok } from 'peaks-loop-shared/result';
 import { readJobShapeDecision, writeJobShapeDecision, JobShapeDecisionError, JOB_SHAPE_NOT_DECIDED, JOB_SHAPE_ALREADY_DECIDED } from '../../services/code/job-shape-decision.js';
 import { findProjectRoot } from '../../services/config/config-safety.js';
+import { getSkillPresence } from '../../services/skills/skill-presence-service.js';
 export function registerCodeJobShapeCommands(code, io) {
     // v3.1.1 Step 0.8 — Job-shape decision recorder.
     // The CLI is a *recorder*, not a judge. The LLM supplies the verdict
@@ -147,19 +148,15 @@ export function registerCodeJobShapeCommands(code, io) {
     });
 }
 // Local helper (was `readActiveSid` in code-commands.ts before rid-024 split).
-// Slice 4.0.7-dogfood-PR-2: now uses the shared canonical resolver
-// (`resolveActiveSessionId` from services/session) so detect-job and
-// read-job-shape see the same session id that `peaks session info --active`
-// returns. The pre-rid helper read `getSkillPresence` (the
-// `.peaks/.active-skill.json` file), which was a different store from
-// `.peaks/_runtime/session.json` — any session created via
-// `peaks workspace init` that never had `peaks skill presence:set peaks-code`
-// called on it (the common case for downstream consumer projects and
-// 24h-mode sessions) reported `NO_ACTIVE_SESSION` from this file.
-import { resolveActiveSessionId } from '../../services/session/index.js';
+// Both detect-job and read-job-shape need to read the active sid from
+// presence. We re-import getSkillPresence here to avoid the cross-file
+// helper import.
 function readActiveSidForJobShape(projectRoot) {
     try {
-        return resolveActiveSessionId(projectRoot);
+        const presence = getSkillPresence(projectRoot);
+        if (presence === null || presence === undefined)
+            return null;
+        return presence.sessionId ?? null;
     }
     catch {
         return null;

package/dist/cli/commands/code-mode-gate-commands.js

@@ -100,22 +100,10 @@ export function registerCodeModeGateCommands(code, io) {
             // this only adds the structured `stale` reason + an
             // envelope-level `stalePresence` field so downstream tooling
             // (statusline, sub-agent dispatch) can act on it.
-            //
-            // Slice 4.0.7-dogfood-PR-3 (ice-cola surface probe 2026-08-02):
-            // 24h-mode sessions explicitly opt out of AskUserQuestion
-            // (the whole point of 24h is no-pause operation), so the
-            // stale-presence gate short-circuits to "not stale" when the
-            // session is in `24H_ACTIVE`. Without this bypass, every
-            // 24h-mode session hit a `shouldPause: true` wall at Step 1
-            // even though 24h-mode is designed to be a no-AskUserQuestion
-            // mode.
             let stalePresence = null;
             if (opts.step === 'step-1-mode-select' && opts.ignoreStalePresence !== true) {
                 const projectRoot = opts.project ?? findProjectRoot(process.cwd()) ?? process.cwd();
-                const sessionIdForGate = readActiveSidForModeGate(projectRoot);
-                if (!is24hActive(projectRoot, sessionIdForGate)) {
-                    stalePresence = checkStalePresence({ projectRootOverride: projectRoot });
-                }
+                stalePresence = checkStalePresence({ projectRootOverride: projectRoot });
             }
             if (stalePresence !== null && stalePresence.stale) {
                 // Build the envelope manually so we can attach the extra
@@ -221,22 +209,9 @@ export function registerCodeModeGateCommands(code, io) {
 // The mode-gate stale-presence check needs the active sid for the
 // observability event; we re-import getSkillPresence here to avoid the
 // cross-file helper import.
-// Slice 4.0.7-dogfood-PR-2: also uses the shared canonical resolver
-// (resolveActiveSessionId) so the same id flows through detect-job,
-// read-job-shape, and should-pause. The pre-rid helper read
-// `getSkillPresence` (the `.peaks/.active-skill.json` file) which
-// was a different store from `.peaks/_runtime/session.json`.
 import { getSkillPresence } from '../../services/skills/skill-presence-service.js';
-import { resolveActiveSessionId } from '../../services/session/index.js';
-import { read24hState } from '../../services/24h-mode/store.js';
 function readActiveSidForModeGate(projectRoot) {
-    // Prefer the canonical binding (works for any session created via
-    // peaks workspace init); fall back to skill presence for sub-skill
-    // activations that never wrote a binding (legacy edge case).
     try {
-        const canonical = resolveActiveSessionId(projectRoot);
-        if (canonical !== null)
-            return canonical;
         const presence = getSkillPresence(projectRoot);
         if (presence === null || presence === undefined)
             return null;
@@ -246,20 +221,3 @@ function readActiveSidForModeGate(projectRoot) {
         return null;
     }
 }
-/**
- * Slice 4.0.7-dogfood-PR-3: returns true when the active session is
- * in 24H_ACTIVE state (per `.peaks/_runtime/<sid>/24h-state.json`).
- * In that state, the mode-gate's stale-presence check is a false
- * positive — 24h-mode explicitly opts out of AskUserQuestion.
- */
-function is24hActive(projectRoot, sessionId) {
-    if (sessionId === null || sessionId.length === 0)
-        return false;
-    try {
-        const snap = read24hState(projectRoot, sessionId);
-        return snap.state === '24H_ACTIVE';
-    }
-    catch {
-        return false;
-    }
-}

package/dist/cli/commands/code-runtime-commands.js

@@ -13,6 +13,8 @@ import { runAutoCompact } from '../../services/code/auto-compact-orchestrator.js
 import { evaluateStep08, STEP_08_BACKUP_REGEX } from '../../services/code/step-08-gate.js';
 import { evaluateEmitHandoff, JOB_NOT_INITIALIZED, JOB_REMAINING_BLOCKED } from '../../services/code/emit-handoff.js';
 import { readJobShapeDecision, JobShapeDecisionError } from '../../services/code/job-shape-decision.js';
+import { getSkillPresence } from '../../services/skills/skill-presence-service.js';
+import { probeInFlightBatch } from '../../services/workflow/workflow-inflight-probe.js';
 export function registerCodeRuntimeCommands(code, io) {
     addJsonOption(code
         .command('post-compact-detect')
@@ -70,12 +72,38 @@ export function registerCodeRuntimeCommands(code, io) {
                 process.exitCode = 1;
                 return;
             }
+            // Slice 4.0.8 (D4d): production `inFlightBatch` MUST come from
+            // the workflow graph probe. The legacy `--in-flight-batch`
+            // boolean CLI flag is a TEST-ONLY seam (gated by
+            // `PEAKS_TEST_SEAM === '1'`). When the env flag is unset
+            // (the production case), we wire `probeInflightBatch` to the
+            // canonical `workflow-inflight-probe.ts` service so the
+            // production decision is graph-backed, not lease-age.
+            const isTestSeam = process.env.PEAKS_TEST_SEAM === '1';
             const result = await runAutoCompact({
                 projectRoot: opts.project,
                 sessionId: opts.sessionId ?? readActiveSid(opts.project) ?? undefined,
-                inFlightBatch: opts.inFlightBatch === true
-                    ? { hasInFlightBatch: true }
-                    : undefined,
+                ...(isTestSeam && opts.inFlightBatch === true
+                    ? { inFlightBatch: { hasInFlightBatch: true } }
+                    : {}),
+                ...(!isTestSeam
+                    ? {
+                        probeInflightBatch: () => {
+                            // Synchronous probe: the workflow-inflight-probe
+                            // service is pure / synchronous (no I/O). The
+                            // empty `graphs` array is the production CLI
+                            // default — callers that want a richer fixture
+                            // (e.g. `peaks session 24h-mode`) should hand-roll
+                            // a probe and pass it via the orchestrator's
+                            // input. When no graph is materialized, the
+                            // probe returns `inFlightBatch: false`, matching
+                            // the 4.0.7 zero-pause contract for stock
+                            // projects.
+                            const out = probeInFlightBatch({ now: new Date().toISOString(), graphs: [] });
+                            return out.inFlightBatch === true;
+                        },
+                    }
+                    : {}),
                 force: opts.force === true,
                 bypassRedLine: opts.bypassRedLine === true,
                 mode: modeName
@@ -390,20 +418,14 @@ export function registerCodeRuntimeCommands(code, io) {
 // Local helper (was `readActiveSid` in code-commands.ts before rid-024 split).
 // Only the 5 runtime probes above use it; keeping it local avoids the
 // cross-file helper import.
-// Slice 4.0.7-dogfood-PR-2: now uses the shared canonical resolver
-// (`resolveActiveSessionId` from services/session) so context-now /
-// post-compact-detect / auto-compact / gate-step-08 / emit-handoff see
-// the same session id that `peaks session info --active` returns.
-// The pre-rid helper read `getSkillPresence` (the
-// `.peaks/.active-skill.json` file), which was a different store from
-// `.peaks/_runtime/session.json` — the two were kept in sync only when
-// `peaks skill presence:set` was called explicitly.
-import { resolveActiveSessionId } from '../../services/session/index.js';
 function readActiveSid(projectRoot) {
     try {
-        return resolveActiveSessionId(projectRoot);
+        const presence = getSkillPresence(projectRoot);
+        if (presence === null || presence === undefined)
+            return null;
+        return presence.sessionId ?? null;
     }
-    catch {
+    catch { // TODO(g2): legacy silent catch — grace: 1 minor release (v2.14.0)
         return null;
     }
 }