sneakoscope 7.3.0 → 7.5.0

package/README.md

@@ -22,7 +22,9 @@ Proof-first orchestration for Codex CLI, ChatGPT Desktop, AI coding agents, mult
 Sneakoscope Codex (`sks`) is an open-source trust layer for Codex CLI and ChatGPT Desktop. It coordinates bounded AI coding agents, records machine-verifiable evidence, preserves project memory, and blocks release claims that are not supported by current tests or artifacts. Search visibility outcomes are measured separately; SKS does not promise rankings or traffic.
 <!-- END SKS SEARCH VISIBILITY MARKETING -->
 
-Current release: **SKS 7.3.0**, with the package preferred Codex channel at **CLI 0.145.0**. SKS stays version-agnostic: older hosts keep working where capabilities allow, while Menu Bar / Center induce updates to the preferred latest. It resolves managed SKS skills from the authoritative global install, preserves a runnable Naruto child slot when `max_threads=2`, and keeps current-version Menu Bar repair transactional so stamped generations remain verifiable. Naruto uses stable opt-in multi-agent V2 when the host exposes it. Local code search is mode-separated (`sks search files|text|structure|symbol|context`) with optional Rust acceleration and no required `rg`/`ast-grep`/`fd` install — see [docs/architecture/search-engine-target.md](docs/architecture/search-engine-target.md). See [CHANGELOG.md](CHANGELOG.md).
+This README documents package **SKS 7.5.0** — its own identity, read from `package.json` and verified by the release gate, not advice about what to install.
+
+Use the official latest stable SKS and Codex CLI releases. SKS stays version-agnostic: older hosts keep working where capabilities allow, while Menu Bar / Center induce updates to the latest stable build. Run `sks update-check` for what is installed and read the capability report for what is actually supported — feature availability is decided by capability probes, not by a version number printed in a document. It resolves managed SKS skills from the authoritative global install, preserves a runnable Naruto child slot when `max_threads=2`, and keeps Menu Bar repair transactional so stamped generations remain verifiable. Naruto uses stable opt-in multi-agent V2 when the host exposes it. Local code search is mode-separated (`sks search files|text|structure|symbol|context`); `context` is answered by the compiled TriWiki Context Graph with evidence paths rather than lexical guessing — see [docs/architecture/context-graph.md](docs/architecture/context-graph.md) and [docs/architecture/search-engine-target.md](docs/architecture/search-engine-target.md). See [CHANGELOG.md](CHANGELOG.md).
 
 ## What 7.0.0 Ships
 
@@ -45,8 +47,15 @@ That installs or repairs SKS, runs `sks doctor --fix`, and prepares the Codex Ap
 
 For package-managed installs:
 
+The npm lifecycle is non-mutating outside the installed package by default:
+it restores only the package-local build stamp and prints the explicit setup
+commands. To intentionally run the legacy bootstrap during installation, set
+`SKS_POSTINSTALL_BOOTSTRAP=1`; `SKS_POSTINSTALL_NO_BOOTSTRAP=1` remains the
+stronger safety override.
+
 ```sh
 npm i -g sneakoscope
+sks bootstrap --yes
 sks doctor --fix
 ```
 
@@ -56,11 +65,11 @@ The SKS menu bar shows the installed Codex CLI version and latest known version.
 
 ### Telegram remote coding on this Mac
 
-Open **SKS Center → Remote & Telegram**, create a private bot with BotFather, send `/start` to that bot from the Telegram account you want to pair, then choose **Connect Bot & Register Coding Session…** and paste the token. SKS verifies the bot, stores the token only in macOS Keychain, pairs only that private chat/user, and registers one dedicated session bound to the current project. Choose **Start Hub**, then send ordinary text to the bot. On the first real message, the Hub creates the Codex thread and starts its first turn in the same App Server connection so the thread is durably resumable; later messages resume that exact thread and return the final response to Telegram.
+Open **SKS Center → Remote & Telegram**, create a bot with BotFather, send `/start` to that bot from the Telegram account you want to pair, then choose **Connect Bot & Register Coding Session…** and paste the token. SKS verifies the bot, stores the token only in macOS Keychain, pairs only that private chat/user, and registers one dedicated session bound to the current project. Choose **Start Hub**, then send ordinary text to the bot. On the first real message, the Hub creates the Codex thread and starts its first turn in the same App Server connection so the thread is durably resumable; later messages resume that exact thread and return the final response to Telegram.
 
 The Hub runs as a user LaunchAgent and uses `caffeinate -i` while the logged-in Mac is available. The Mac still needs to remain powered on, logged in, awake, and network-connected; closing the lid or logging out can stop access. Telegram input has no arbitrary shell path, runs with approvals disabled and network access disabled inside the Codex workspace sandbox, and cannot target an unpaired chat or another project.
 
-SKS Center is the menu bar companion: install it with `sks menubar install`, then click the SKS icon in the macOS menu bar and choose **Open SKS Control Center…**. Every GUI step above has a CLI equivalent (`sks telegram setup --bot-token-stdin`, `sks telegram hub start`, `sks telegram status`). See **[docs/telegram-and-center.md](docs/telegram-and-center.md)** for the full step-by-step guide, storage locations, security model, and a blocker-by-blocker troubleshooting table.
+SKS Center is the menu bar companion: install it with `sks menubar install`, then click the SKS icon in the macOS menu bar and choose **Open SKS Control Center…**. Every GUI step above has a CLI equivalent (`sks telegram setup --bot-token-stdin`, `sks telegram hub start`, `sks telegram status`). The hub uses long polling, so a bot with an existing webhook must have that webhook removed before the hub can start; SKS fails closed with `telegram_webhook_conflict` and never clears it automatically. See **[docs/telegram-and-center.md](docs/telegram-and-center.md)** for the complete BotFather setup, optional command menu and privacy-mode guidance, secure token rotation, verification, and troubleshooting.
 
 ## The Front Door
 
@@ -84,10 +93,113 @@ Gates are task-profile aware: greetings and answer-only turns create no mission
 
 Every installed Codex hook runs one common Naruto decision gate. The gate records `none`, `generic_naruto`, or `route_owned`: Answer, DFix, Wiki, Computer Use, Goal, and simple Git/control turns stay lightweight; ordinary non-trivial work defaults to two independent official subagents; critical work spanning at least three risk domains may use three. Research, AutoResearch, and QA-Loop retain their own exact orchestration contracts instead of receiving a second generic fan-out. Explicit `--agents N` remains authoritative.
 
-SKS installs twenty-five narrow project custom agents, including native AppKit, toolchain, protocol, runtime-reliability, TriWiki-evidence, long-context, Computer Use, Browser/Chrome, and image-generation specialists. Delegation prompts inject at most the three roles recommended for the current goal rather than serializing the full catalog, so expanding role coverage does not serialize the full inventory into every prompt. TriWiki context is also bounded and query-aware: ordinary work receives up to four trust/hydration anchors and complex, parallel, or high-risk work receives up to six, with source hydration required before relying on lower-trust hints. In CLI Zellij mode, the right side is a live observability surface rather than a static lane reservation: one monitor plus one viewport by default (maximum three) shows official thread role/model, redacted live phase/task/file updates from rollout-compatible Codex 0.144.1+ sessions while the current release baseline remains 0.145.0, plus `running`, `verifying`, and trustworthy parent-verdict completion/failure states. Rollout activity is display-only and never completion proof.
+SKS installs twenty-five narrow project custom agents, including native AppKit, toolchain, protocol, runtime-reliability, TriWiki-evidence, long-context, Computer Use, Browser/Chrome, and image-generation specialists. Delegation prompts inject at most the three roles recommended for the current goal rather than serializing the full catalog, so expanding role coverage does not serialize the full inventory into every prompt. TriWiki context is also bounded and query-aware: ordinary work receives up to four trust/hydration anchors and complex, parallel, or high-risk work receives up to six, with source hydration required before relying on lower-trust hints. In CLI Zellij mode, the right side is a live observability surface rather than a static lane reservation: one monitor plus one viewport by default (maximum three) shows official thread role/model, redacted live phase/task/file updates from rollout-compatible Codex sessions on the official latest stable CLI, plus `running`, `verifying`, and trustworthy parent-verdict completion/failure states. Rollout activity is display-only and never completion proof.
 
 Official subagent requests use `--agents`; removed scheduler, pool, backend, and model flags fail closed.
 
+## Embedding SKS In Another Agent System
+
+By default SKS owns the credential: it pins `model_provider="openai"` and `forced_login_method="chatgpt"`, so an operator's interactive ChatGPT session authenticates the run and it cannot drift onto another provider unnoticed.
+
+That default is wrong for an unattended host. An orchestrator that already holds and rotates a customer's OpenAI-compatible credential — a local codex-lb endpoint, OpenRouter, any `env_key` provider block — cannot log in interactively on every node, and forcing `chatgpt` makes Codex treat an `auth_mode="apikey"` session as a hard logout and delete `auth.json`. **Host mode** hands that decision back.
+
+```sh
+sks naruto run "task" \
+  --auth-mode=host \
+  --model-provider=codex-lb \
+  --provider-env-key=CODEX_LB_API_KEY
+```
+
+| Surface | Flag | Environment | Effect |
+| --- | --- | --- | --- |
+| Who authenticates | `--auth-mode=host` | `SKS_NARUTO_AUTH_MODE=host` | SKS injects neither `model_provider` nor `forced_login_method`; Codex uses your `config.toml` provider block |
+| Which provider block | `--model-provider=<name>` | `SKS_NARUTO_MODEL_PROVIDER` | Names a `[model_providers.<name>]` block. Host mode only |
+| Which credential variable | `--provider-env-key=<NAME>` | `SKS_NARUTO_PROVIDER_ENV_KEY` | Forwards exactly that variable to the child so the block's `env_key` resolves. Host mode only |
+| Release the login only | `--no-forced-login-method` | `SKS_NARUTO_FORCED_LOGIN_METHOD=none` | Keeps the SKS provider, drops the forced ChatGPT login |
+| Parent model / effort | `--parent-model`, `--parent-effort` | `SKS_NARUTO_PARENT_MODEL`, `SKS_NARUTO_PARENT_EFFORT` | Overrides the built-in parent policy |
+| Subagent model / effort | `--subagent-model`, `--subagent-effort` | `SKS_NARUTO_SUBAGENT_MODEL`, `SKS_NARUTO_SUBAGENT_EFFORT` | Overrides the default subagent policy |
+
+Guarantees this contract makes:
+
+- **SKS never reads, stores, forwards to a third party, or logs your credential.** It forwards one named environment variable to the Codex child and records only that variable's *name* in receipts. Values of secret-shaped variables are redacted from captured output.
+- **A malformed value blocks the run.** An unknown auth mode, a provider name with a space, an effort tier that is not `minimal|low|medium|high|max`, or a `--provider-env-key` that is absent from the environment all fail before mission state is written. SKS never quietly falls back to its own credential — that surprise is the failure mode this contract exists to prevent.
+- **Mixed configurations are refused.** Naming a provider while SKS still forces a ChatGPT login would authenticate one way and bill another, so it is a blocker rather than a silent precedence rule.
+- **The default is unchanged.** Managed mode still pins the ChatGPT login, and the real-credential smoke gate still proves it.
+
+### Designing an adapter that wraps SKS without fighting it
+
+The rule that keeps an adapter conflict-free: **let SKS own the mission, the evidence, and the gates; let the host own the credential, the model policy, and the workspace.** Cross that line — by patching `dist/`, writing `.sneakoscope/` yourself, or re-implementing the gate DAG — and every SKS update breaks you.
+
+```ts
+// acas/adapters/sks.ts — one process boundary, no dist patching.
+import { execFile } from 'node:child_process'
+import { promisify } from 'node:util'
+
+const run = promisify(execFile)
+
+export interface SksMissionRequest {
+  workspace: string          // host owns the checkout
+  task: string
+  agents?: number
+  tenant: {
+    providerBlock: string    // [model_providers.<name>] the host wrote into config.toml
+    credentialEnvKey: string // env var the block's env_key points at
+    credential: string       // held by the host; never persisted by SKS
+    parentModel?: string
+    subagentModel?: string
+  }
+}
+
+export async function runSksMission(request: SksMissionRequest) {
+  const { stdout } = await run('sks', [
+    'naruto', 'run', request.task,
+    '--json',
+    ...(request.agents ? ['--agents', String(request.agents)] : []),
+    // Host owns authentication and model policy.
+    '--auth-mode=host',
+    `--model-provider=${request.tenant.providerBlock}`,
+    `--provider-env-key=${request.tenant.credentialEnvKey}`,
+    ...(request.tenant.parentModel ? [`--parent-model=${request.tenant.parentModel}`] : []),
+    ...(request.tenant.subagentModel ? [`--subagent-model=${request.tenant.subagentModel}`] : [])
+  ], {
+    cwd: request.workspace,
+    env: {
+      ...process.env,
+      // The one variable the provider block resolves. Scope it to this call
+      // rather than exporting it process-wide.
+      [request.tenant.credentialEnvKey]: request.tenant.credential
+    },
+    maxBuffer: 64 * 1024 * 1024
+  })
+  // SKS answers with its own result schema; treat it as the source of truth for
+  // status and evidence rather than re-deriving success from stdout text.
+  return JSON.parse(stdout)
+}
+```
+
+Then read the outcome through SKS's own surfaces instead of inferring it:
+
+```sh
+sks naruto proof --json                 # completion proof, blockers, evidence links
+sks triwiki graph-status --fast --json  # is the compiled graph usable right now (no git, no spawn)
+sks search context "..." --json         # evidence-backed context with reason paths
+```
+
+`graph-status --fast` is the probe to poll from a host loop: it reads the stored
+artifacts only, so it costs no subprocess, and it reports which staleness reasons
+it could not evaluate rather than returning a `fresh` that means less than it
+looks. Drop `--fast` when you want the full git-aware verdict.
+
+Adapter rules that keep updates safe:
+
+1. **One process boundary.** Shell out to the `sks` CLI with `--json`. Do not import SKS internals; they are not a published API and they move.
+2. **Never patch `dist/`.** A local patch is overwritten by every install and is asserted against by release gates. If a behaviour you need is missing, it belongs behind a flag like the ones above.
+3. **Host owns the workspace, SKS owns `.sneakoscope/`.** Write your own state anywhere else; treat `.sneakoscope/` as SKS-owned and read-only from outside.
+4. **Pass credentials per invocation, not per machine.** A per-call `env` entry keeps one tenant's key out of another tenant's run.
+5. **Let the gates fail.** A blocked mission with blockers is a correct answer. Do not retry it with safety flags off, and do not treat `--trusted-project` as a default — it is an operator decision about a reviewed checkout.
+6. **Do not pin a version in your own docs or error strings.** Ask for the official latest stable release and read the capability report; SKS enforces this on itself with the `latest-version:guidance` gate.
+7. **Parallelism advice is advisory.** `sks naruto` decides its own wave shape; if you plan slices yourself, check them against the graph advisory rather than assuming disjointness.
+
 ## Why Not Just An LLM Reviewer?
 
 | Question | Oracle-style LLM review | SKS gate/review |
@@ -115,7 +227,7 @@ It shows the current quickstart flow: one-line install, `$sks-plan`, `sks review
 - Project memory: `sks memory build`
 - Codebase index/pack for LLM context: `sks wiki refresh --code`, `sks wiki validate --json` (code-pack freshness)
 - Native capability repair: `sks doctor --fix` (imagegen/Computer Use/Browser Use), `.sneakoscope/reports/native-capability-readiness.json`
-- codex-lb continuity: `sks codex-lb status --json` verifies the selected proxy's unauthenticated `/health` `X-App-Version`. Tool-heavy continuation requires codex-lb `1.21.0-beta.3` or later; older or unverified deployments block setup, doctor, and launch instead of silently falling back.
+- codex-lb continuity: `sks codex-lb status --json` verifies the selected proxy's unauthenticated `/health` `X-App-Version`. Tool-heavy continuation requires a codex-lb deployment that reports the capability; use the official latest stable release. Older or unverified deployments block setup, doctor, and launch instead of silently falling back.
 - Agent bridge for any agent system: `sks mcp-server`, `sks agent-bridge setup`, `SKS_AGENT_MODE=1` — see [docs/AGENT-BRIDGE.md](docs/AGENT-BRIDGE.md)
 - Release gates: `npm run release:check:affected` for ordinary change-aware verification and `npm run release:check:confidence` for the final local confidence pass.
 - Release preparation: typecheck, one clean build, focused tests, affected/confidence gates, then `npm publish --dry-run --json --registry https://registry.npmjs.org/ --tag latest --access public`. The dry-run does not publish; authorization remains a separate maintainer workflow.

package/crates/sks-core/Cargo.lock

@@ -259,7 +259,7 @@ dependencies = [
 
 [[package]]
 name = "sks-core"
-version = "7.3.0"
+version = "7.5.0"
 dependencies = [
  "globset",
  "grep-matcher",

package/crates/sks-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "sks-core"
-version = "7.3.0"
+version = "7.5.0"
 edition = "2021"
 
 [dependencies]

package/dist/cli/codex-app-command.js

@@ -37,7 +37,7 @@ function remoteControlHelp() {
     return [
         'Usage: sks codex-app remote-control [--status|--check|--dry-run|--json] [-- <codex remote-control args>]',
         '',
-        'Starts Codex CLI 0.130.0+ remote-control, the headless remotely controllable app-server entrypoint.',
+        'Starts Codex CLI remote-control, the headless remotely controllable app-server entrypoint.',
         'SKS only wraps the first-party command and refuses older Codex CLI versions instead of falling back to app-server internals.'
     ].join('\n');
 }

package/dist/cli/command-manifest-lite.js

@@ -30,7 +30,7 @@ const COMMAND_MANIFEST_LITE_BASE = [
     { name: 'git', summary: 'Inspect and enforce SKS git collaboration hygiene', maturity: 'beta' },
     { name: 'paths', summary: 'Inspect SKS managed paths', maturity: 'beta', readonly: true, allowedDuringActiveRoute: true, diagnostic: true },
     { name: 'rollback', summary: 'List or apply managed-path rollback actions', maturity: 'beta', skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
-    { name: 'postinstall', summary: 'Run postinstall bootstrap', maturity: 'stable', skipMigrationGate: true },
+    { name: 'postinstall', summary: 'Restore package state; bootstrap only with explicit opt-in', maturity: 'stable', skipMigrationGate: true },
     { name: 'codex', summary: 'Check Codex CLI compatibility and vendored hook schemas', maturity: 'beta', skipMigrationGate: true },
     { name: 'codex-app', summary: 'Check Codex App readiness', maturity: 'beta', skipMigrationGate: true },
     { name: 'codex-native', summary: 'Inspect Codex Native broker and routing readiness', maturity: 'beta' },
@@ -201,6 +201,7 @@ export function commandInputSchema(profile) {
             mission: boundedString(1, 160),
             agents: { type: 'integer', minimum: 1 },
             max_threads: { type: 'integer', minimum: 1 },
+            stdin: { type: 'boolean' },
             readonly: { type: 'boolean' },
             trusted_project: { type: 'boolean' },
             json: { type: 'boolean' }

package/dist/cli/install-helpers-codex-lb-selftest.js

@@ -25,7 +25,8 @@ async function codexLbLoginCallCount(home) {
 function codexLbPostinstallEnv(baseEnv, overrides = {}) {
     return {
         ...baseEnv,
-        SKS_POSTINSTALL_NO_BOOTSTRAP: '1',
+        SKS_POSTINSTALL_BOOTSTRAP: '1',
+        SKS_POSTINSTALL_NO_BOOTSTRAP: '',
         SKS_SKIP_POSTINSTALL_SHIM: '1',
         SKS_SKIP_POSTINSTALL_CONTEXT7: '1',
         SKS_SKIP_POSTINSTALL_GETDESIGN: '1',

package/dist/cli/install-helpers-install-support.js

@@ -252,22 +252,12 @@ export async function ensureGlobalCodexSkillsDuringInstall(opts = {}) {
     }
 }
 export async function ensureGlobalGetdesignSkillDuringInstall() {
-    if (process.env.SKS_SKIP_POSTINSTALL_GETDESIGN === '1')
-        return { status: 'skipped', reason: 'SKS_SKIP_POSTINSTALL_GETDESIGN=1' };
-    const pathEnv = process.env.PATH || '';
-    const skillsBin = await findCommandOnPath('skills', pathEnv);
-    if (!skillsBin)
-        return { status: 'skills_cli_missing', install: GETDESIGN_REFERENCE.codex_skill_install };
-    const add = await runProcess(skillsBin, ['add', GETDESIGN_REFERENCE.codex_skill], {
-        timeoutMs: 30000,
-        maxOutputBytes: 64 * 1024
-    }).catch((err) => ({ code: 1, stdout: '', stderr: err.message }));
-    const out = `${add.stdout || ''}\n${add.stderr || ''}`;
-    if (add.code === 0)
-        return { status: /already|exists|present/i.test(out) ? 'present' : 'installed', command: skillsBin };
-    if (/already|exists|present/i.test(out))
-        return { status: 'present', command: skillsBin };
-    return { status: 'failed', command: skillsBin, error: out.trim() || 'skills add failed' };
+    return {
+        status: 'skipped',
+        reason: 'manual_install_only',
+        install: GETDESIGN_REFERENCE.codex_skill_install,
+        reviewed_ref: GETDESIGN_REFERENCE.codex_skill_ref
+    };
 }
 export async function ensureCodexImagegenDuringInstall(opts = {}) {
     if (process.env.SKS_POSTINSTALL_SKIP_IMAGEGEN_REPAIR === '1' || opts.skip === true) {

package/dist/cli/install-helpers.js

@@ -35,24 +35,31 @@ function packagedSksEntrypoint() {
 }
 export async function postinstall({ bootstrap, args = [] }) {
     const installRoot = path.resolve(process.env.INIT_CWD || process.cwd());
-    const conflictScan = await scanHarnessConflicts(installRoot);
-    if (conflictScan.hard_block) {
-        await postinstallHarnessConflictNotice(conflictScan);
+    console.log('\nSKS installed.');
+    await restoreInstalledPackageBuildStamp();
+    if (!postinstallExternalMutationsAllowed(process.env)) {
+        console.log('Automatic bootstrap was not run; npm install leaves project, HOME, Codex, and global SKS state unchanged by default.');
+        console.log('Next: run `sks bootstrap` when you are ready to initialize SKS.');
+        console.log('Dependency diagnostics remain explicit: sks deps check');
+        console.log('Explicit lifecycle opt-in: SKS_POSTINSTALL_BOOTSTRAP=1 npm i -g sneakoscope');
+        console.log('Optional Homebrew/npm-global tool repair remains off unless SKS_POSTINSTALL_AUTO_INSTALL_CLI_TOOLS=1 is also set.');
+        const reason = process.env.SKS_POSTINSTALL_NO_BOOTSTRAP === '1'
+            ? 'SKS_POSTINSTALL_NO_BOOTSTRAP=1'
+            : 'explicit opt-in required (SKS_POSTINSTALL_BOOTSTRAP=1)';
+        console.log(`Reason: ${reason}.`);
         return;
     }
-    const codexLbConfigSnapshot = await capturePostinstallCodexLbConfigSnapshot();
+    let codexLbConfigSnapshot = null;
+    let reconcileCodexLb = false;
     try {
-        console.log('\nSKS installed.');
-        try {
-            const stampLib = await import('../scripts/lib/ensure-dist-fresh.js');
-            await fsp.access(stampLib.distStampPath).catch(async () => {
-                await fsp.writeFile(stampLib.distStampPath, `${JSON.stringify(stampLib.buildStampPayload(), null, 2)}\n`);
-                console.log('SKS build stamp: restored for update self-verification (npm packages ship without it).');
-            });
-        }
-        catch (err) {
-            console.log(`SKS build stamp: could not restore (${err?.message || err}); \`sks update\` self-verification may report dist_stamp missing.`);
+        const bootstrapDecision = await postinstallBootstrapDecision(installRoot);
+        const conflictScan = await scanHarnessConflicts(installRoot);
+        if (conflictScan.hard_block) {
+            await postinstallHarnessConflictNotice(conflictScan);
+            return;
         }
+        codexLbConfigSnapshot = await capturePostinstallCodexLbConfigSnapshot();
+        reconcileCodexLb = true;
         const shim = await ensureSksCommandDuringInstall();
         if (shim.status === 'present')
             console.log(`SKS command: available (${shim.command ?? 'unknown'}).`);
@@ -150,35 +157,43 @@ export async function postinstall({ bootstrap, args = [] }) {
         else if (globalSkills.status === 'failed')
             console.log(`Codex App global $ skills: auto setup failed. Run \`sks doctor --fix\`. ${globalSkills.error || ''}`.trim());
         const getdesignSkill = await ensureGlobalGetdesignSkillDuringInstall();
-        if (getdesignSkill.status === 'installed')
-            console.log('getdesign Codex skill: installed.');
-        else if (getdesignSkill.status === 'present')
-            console.log('getdesign Codex skill: already available.');
-        else if (getdesignSkill.status === 'skills_cli_missing')
-            console.log(`getdesign Codex skill: skills CLI missing; generated getdesign-reference skill is installed. Later run \`${getdesignSkill.install}\` if the skills CLI is available.`);
-        else if (getdesignSkill.status === 'skipped')
-            console.log(`getdesign Codex skill: skipped (${getdesignSkill.reason}).`);
-        else if (getdesignSkill.status === 'failed')
-            console.log(`getdesign Codex skill: auto setup failed; generated getdesign-reference skill remains available. ${getdesignSkill.error || ''}`.trim());
-        const bootstrapDecision = await postinstallBootstrapDecision(installRoot);
-        if (bootstrapDecision.run) {
-            console.log(`SKS bootstrap: ${bootstrapDecision.reason}.`);
-            await runPostinstallBootstrap(installRoot, bootstrap);
-            return;
-        }
-        console.log('\nNext:');
-        console.log('  sks bootstrap');
-        console.log(`\nSKS bootstrap was not run automatically: ${bootstrapDecision.reason}.`);
-        console.log('This initializes the current project, installs SKS Codex App skills, verifies Codex App/Context7 readiness, and checks Zellij runtime dependencies.');
-        console.log('Dependency repair: sks bootstrap --yes, sks deps check --yes, or sks --mad --yes. Postinstall reports missing CLI tools but does not mutate Homebrew/npm globals unless SKS_POSTINSTALL_AUTO_INSTALL_CLI_TOOLS=1 is set.');
-        console.log('Open runtime after readiness is green: sks\n');
+        console.log(`getdesign Codex skill: not installed automatically; generated getdesign-reference skill is available. To install the upstream skill manually, review commit ${getdesignSkill.reviewed_ref} and run \`${getdesignSkill.install}\`.`);
+        console.log(`SKS bootstrap: ${bootstrapDecision.reason}.`);
+        await runPostinstallBootstrap(installRoot, bootstrap, bootstrapDecision);
+        return;
     }
     catch (err) {
         console.log(`\nSKS postinstall: a setup step did not complete; installation continues. Run \`sks doctor --fix\` afterward. (${err?.message || err})`);
     }
     finally {
-        await restorePostinstallCodexLbConfigSnapshot(codexLbConfigSnapshot).catch(() => { });
-        await reportPostinstallCodexLbAuth(codexLbConfigSnapshot).catch(() => { });
+        if (reconcileCodexLb) {
+            await restorePostinstallCodexLbConfigSnapshot(codexLbConfigSnapshot).catch(() => { });
+            await reportPostinstallCodexLbAuth(codexLbConfigSnapshot).catch(() => { });
+        }
+    }
+}
+function postinstallExternalMutationsAllowed(env) {
+    return env.SKS_POSTINSTALL_BOOTSTRAP === '1' && env.SKS_POSTINSTALL_NO_BOOTSTRAP !== '1';
+}
+async function restoreInstalledPackageBuildStamp() {
+    try {
+        const stampLib = await import('../scripts/lib/ensure-dist-fresh.js');
+        const root = path.resolve(packageRoot());
+        const rawStamp = String(stampLib.distStampPath || '').trim();
+        if (!rawStamp)
+            throw new Error('dist_stamp_path_missing');
+        const stamp = path.resolve(rawStamp);
+        const relative = path.relative(root, stamp);
+        if (relative.startsWith('..') || path.isAbsolute(relative)) {
+            throw new Error('dist_stamp_outside_package_root');
+        }
+        await fsp.access(stamp).catch(async () => {
+            await fsp.writeFile(stamp, `${JSON.stringify(stampLib.buildStampPayload(), null, 2)}\n`);
+            console.log('SKS build stamp: restored inside the installed package for update self-verification.');
+        });
+    }
+    catch (err) {
+        console.log(`SKS build stamp: could not restore (${err?.message || err}); \`sks update\` self-verification may report dist_stamp missing.`);
     }
 }
 async function runPostinstallProjectRetentionCleanup(root) {
@@ -294,23 +309,17 @@ function shouldAskPostinstallQuestion() {
 export async function postinstallBootstrapDecision(root) {
     if (process.env.SKS_POSTINSTALL_NO_BOOTSTRAP === '1')
         return { run: false, reason: 'SKS_POSTINSTALL_NO_BOOTSTRAP=1' };
-    if (process.env.SKS_POSTINSTALL_BOOTSTRAP === '0')
-        return { run: false, reason: 'SKS_POSTINSTALL_BOOTSTRAP=0' };
+    if (process.env.SKS_POSTINSTALL_BOOTSTRAP !== '1') {
+        return { run: false, reason: 'explicit opt-in required (SKS_POSTINSTALL_BOOTSTRAP=1)' };
+    }
     const installRoot = path.resolve(root || process.cwd());
     const candidate = await isProjectSetupCandidate(installRoot);
     const target = candidate ? installRoot : globalSksRoot();
-    if (process.env.SKS_POSTINSTALL_BOOTSTRAP === '1')
-        return { run: true, target, reason: 'forced by SKS_POSTINSTALL_BOOTSTRAP=1' };
-    if (process.env.npm_config_global === 'true' && candidate) {
-        return { run: true, target: globalSksRoot(), reason: 'global install: bootstrapping global SKS runtime only (run `sks setup` inside a project to initialize it)' };
-    }
-    if (candidate)
-        return { run: true, target, reason: 'auto-running sks setup --bootstrap --install-scope global --force' };
-    return { run: true, target, reason: 'no project marker found; auto-running global SKS runtime bootstrap' };
+    return { run: true, target, reason: 'forced by SKS_POSTINSTALL_BOOTSTRAP=1' };
 }
-async function runPostinstallBootstrap(root, bootstrap) {
+async function runPostinstallBootstrap(root, bootstrap, selectedDecision) {
     const previousCwd = process.cwd();
-    const decision = await postinstallBootstrapDecision(root);
+    const decision = selectedDecision || await postinstallBootstrapDecision(root);
     const target = path.resolve(decision.target || root || previousCwd);
     await ensureDir(target);
     process.chdir(target);

package/dist/cli/router.js

@@ -223,9 +223,17 @@ export function safeActiveRouteContinuation(command, args, state = {}) {
     const subcommand = String(args[0] || '').toLowerCase();
     const activeRoute = String(state.route || state.route_command || state.mode || '').replace(/^\$/, '').replace(/[-_]/g, '').toUpperCase();
     if (command === 'naruto') {
-        if (activeRoute !== 'NARUTO' || subcommand !== 'run')
+        if (activeRoute !== 'NARUTO')
             return false;
         const requestedMission = optionValue(args, ['--mission', '--mission-id']);
+        if (subcommand === 'parent-summary') {
+            const explicitParentSummaryMission = optionValue(args, ['--mission']);
+            return Boolean(state.mission_id)
+                && explicitParentSummaryMission === String(state.mission_id)
+                && args.includes('--stdin');
+        }
+        if (subcommand !== 'run')
+            return false;
         return Boolean(state.mission_id)
             && (requestedMission === String(state.mission_id) || requestedMission === 'latest');
     }