sneakoscope 8.0.2 → 8.0.4

package/README.md

@@ -22,7 +22,7 @@ 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 -->
 
-This README documents package **SKS 8.0.2** — its own identity, read from `package.json` and subject to release-gate verification, not advice about what to install.
+This README documents package **SKS 8.0.4** — its own identity, read from `package.json` and subject to release-gate verification, 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).
 
@@ -32,7 +32,7 @@ Use the official latest stable SKS and Codex CLI releases. SKS stays version-agn
 | --- | --- |
 | Overview mixed Menu Bar, installed SKS, and cached registry versions | Each value is labeled by authority, stale or unavailable probes remain explicit, and Refresh forces a bounded update-status refresh. |
 | Naruto stopped creating children after its first wave | The root parent records settled waves, recovers open-thread capacity, rescans the ready DAG, and can launch later direct-child waves under the same workflow run. |
-| Most delegated work drifted to Sol Max | Read-heavy discovery uses Terra Medium, ordinary implementation uses Sol High, and Sol Max is reserved for focused high-risk or final judgment slices. |
+| Most delegated work drifted to Sol Max | Read-heavy discovery uses Terra Max, ordinary implementation uses Sol High, and Sol Max is reserved for focused high-risk or final judgment slices. |
 | Goal creation started a second SKS-owned mission and loop | Codex native Goal is the only persisted owner; create/edit objectives are detailed and bounded, while SKS writes no Goal state or fallback loop. |
 | Global instructions accumulated duplicated route rules and forced synthetic tests | One Core Engineering Directive anchors all work, route-specific details stay with their route, and verification targets normal behavior, meaningful boundaries, and plausible failures. |
 | GUI-launched status commands could hang or contaminate real update state during tests | Menu Bar commands use a safe HOME cwd, closed stdin, and timeouts; update fixtures use isolated HOME and cache paths. |
@@ -40,10 +40,10 @@ Use the official latest stable SKS and Codex CLI releases. SKS stays version-agn
 ## Install In One Command
 
 ```sh
-npx sneakoscope install --yes
+npm exec --yes --package=sneakoscope@latest -- sneakoscope install --yes
 ```
 
-That installs or repairs SKS, runs `sks doctor --fix`, and prepares the Codex App integration. The plugin marketplace path is also prepared through `plugins/sks/.codex-plugin/plugin.json`.
+The explicit `@latest` tag prevents a local package or stale npx cache from silently choosing an older installer. The installer verifies the registry tag, installs the exact version carried by that package, runs the exact installed entrypoint's `doctor --fix`, and succeeds only when the first `sks` on `PATH` targets that entrypoint and reports the same version. An older or same-version shadow prefix that still wins is reported as a blocker with a recoverable prior-version command. The plugin marketplace path is also prepared through `plugins/sks/.codex-plugin/plugin.json`.
 
 For package-managed installs:
 
@@ -54,20 +54,124 @@ commands. To intentionally run the legacy bootstrap during installation, set
 stronger safety override.
 
 ```sh
-npm i -g sneakoscope
-sks bootstrap --yes
-sks doctor --fix
+npm install --global sneakoscope@latest
+node "$(npm root --global)/sneakoscope/dist/bin/sks.js" bootstrap --yes
+node "$(npm root --global)/sneakoscope/dist/bin/sks.js" doctor --fix
+sks --version
 ```
 
+The two setup calls intentionally use the entrypoint under the npm global root.
+The final `sks --version` must report that same package version; if it does not,
+an older prefix still precedes the new npm bin directory on `PATH`.
+
 The SKS menu bar shows the installed Codex CLI version and latest known version. An `⬆` marker appears when an update is available; **Update Codex CLI Now** uses native `codex update` when the selected CLI advertises it, otherwise it verifies the installation provenance and invokes the matching official standalone-installer, npm-global, or Homebrew-cask update method. If the method cannot be verified, it fails closed instead of guessing. Control Center updates keep the active UI alive until the operation receipt is durable, then relaunch the companion out of process. This is an explicit global tool mutation. **Run sks doctor --fix** performs the global-only menu repair flow without treating the user's home directory as a project.
 
 **Manage MCP Servers…** opens a native macOS manager for the global `~/.codex/config.toml`. It can add remote URL or local stdio servers, enable/disable existing entries, remove entries after confirmation, and refresh the current state. Mutations are lock-protected, backed up, TOML-validated, and written with mode `0600`; configured environment values and command arguments are never rendered in the list. Changes apply to new Codex sessions. The same plumbing is available through the canonical `sks mcp config list|get|add|edit|duplicate|enable|disable|remove|test|login|logout|backups|restore` surface for diagnostics and automation.
 
-### Remote coding: Orca (external option)
-
-SKS no longer provides a first-party Telegram coding bridge. If you want to monitor or steer coding work from another device, consider [Orca](https://github.com/stablyai/orca), an external MIT-licensed project that can launch Codex in a worktree. Orca is not bundled with SKS, supported by SKS, or required to use SKS; SKS adds no Orca dependency or configuration.
-
-Orca's mobile companion and Remote Orca Servers are beta. Their desktop/server runtime remains the source of truth and must keep running; remote access may require a private LAN or Tailscale path. See [the Orca migration and remote-coding guide](docs/orca-remote-coding.md) for scope, setup links, and former Telegram-user migration notes.
+### Remote control: Telegram BotFather integration
+
+SKS 8.0.4 provides a first-party Telegram Bot API transport for the existing
+typed remote-control contract. A bounded outbound `getUpdates` loop runs only
+inside the resident Menu Bar process: it opens no inbound port, tunnel, daemon,
+or public webhook.
+
+#### BotFather setup
+
+1. In Telegram, open **@BotFather**, send `/newbot`, and complete its name and
+   username prompts. BotFather returns the bot token. The token authorizes the
+   bot against the Bot API; treat it like a password. Do not place it in a
+   shell command, config file, commit, issue, or screenshot.
+2. On the Mac that runs SKS, open **SKS Center → Remote Coding**, choose
+   **Enter Bot Token…**, and paste the token into the native secure-input
+   sheet. SKS verifies `getMe` and the bot's webhook state before it stores
+   anything. If a webhook is active, the token is not retained and Center asks
+   for explicit consent before removing that webhook without dropping pending
+   updates.
+
+   For a terminal-only setup, use a no-echo `zsh` prompt and pipe the token on
+   standard input; direct interactive TTY input is intentionally rejected:
+
+   ```sh
+   IFS= read -r -s "sks_telegram_token?BotFather token: "
+   printf '\n'
+   printf '%s\n' "$sks_telegram_token" | sks telegram setup --token-stdin
+   unset sks_telegram_token
+   ```
+
+   If that command reports an existing webhook, review the delivery change and
+   repeat the same no-echo flow with `--remove-webhook`. This is explicit
+   consent to stop the old webhook endpoint; SKS always requests
+   `drop_pending_updates=false`. The token travels only on standard input, is
+   verified with Telegram before storage, is never printed, and is stored in
+   the owner-only user secret file. A token supplied by `TELEGRAM_BOT_TOKEN` or
+   `SKS_TELEGRAM_BOT_TOKEN` is also supported for an operator-managed runtime,
+   but environment values can be exposed to other local processes and are not
+   the recommended setup path. SKS Center restarts its resident poller after a
+   successful save; if that restart reports a blocker, resolve it before
+   generating or sending a pairing code.
+3. For terminal-only setup, restart the resident Menu Bar process immediately
+   after setup (and after any webhook removal or token rotation). The poller
+   must be running before it can consume and confirm `/start`:
+
+   ```sh
+   sks menubar restart
+   ```
+
+   There is deliberately no `sks telegram start` or `sks telegram stop`:
+   Telegram is not a separate daemon. SKS Center exposes **Start**, **Stop**,
+   and **Restart** for the poller owned by the current resident Menu Bar
+   process. **Stop** preserves the token and pairings and lasts only until that
+   companion is relaunched. To keep Telegram stopped across relaunches, stop or
+   uninstall the entire Menu Bar companion; that also disables its other
+   resident features.
+4. Issue a short-lived pairing code with `sks telegram pair`:
+
+   ```sh
+   sks telegram pair --json
+   ```
+
+   From the one intended **private** chat, send the returned
+   `/start <pairing-code>` message to the bot before it expires. Only that
+   private chat/user pair is enrolled. Unpaired chats receive no reply.
+5. After the bot confirms pairing, send a typed command such as:
+
+   ```text
+   /sks status {}
+   ```
+
+   The command grammar is `/sks <command> <JSON object>`; the JSON object may
+   be omitted when the command needs no options. The allowlist is `gates`,
+   `paths`, `pipeline`, `proof`, `search`, `stats`, `status`, `stop-gate`,
+   `trust`, `update-check`, and `validate-artifacts`. If SKS replies with a
+   short-lived confirmation nonce, send the exact `/confirm <nonce>` message
+   once before it expires. Arbitrary prose and free-form shell commands are not
+   executed.
+6. Confirm runtime evidence:
+
+   ```sh
+   sks telegram status --json
+   sks telegram doctor --json
+   sks doctor
+   ```
+
+   `status` reads the secret-free liveness receipt. `telegram doctor` evaluates
+   token presence, the bot identity, pairing, audit health, poller state, and
+   liveness. A ready result requires a real `getMe` check, a paired private
+   chat, and a running poller; a configured token alone is not readiness.
+
+The transport accepts only allowlisted typed commands. It never accepts
+free-form shell input; higher-risk commands require actor-bound two-step
+confirmation and an audit receipt. Telegram long polling and a webhook cannot
+be active together. If Doctor reports a webhook/409 conflict, enter the token
+again in SKS Center and approve webhook removal, or repeat the no-echo CLI
+setup with `--remove-webhook`, then restart the poller. SKS never drops pending
+updates during that transition.
+
+If a token may have leaked, revoke/regenerate it in BotFather, enter the
+replacement through SKS Center (or the no-echo CLI flow), and restart the
+poller. Token rotation and BotFather credential changes are external actions;
+SKS does not publish packages, revoke tokens, or make any other irreversible
+remote change on the operator's behalf.
 
 ## The Front Door
 
@@ -79,28 +183,37 @@ Orca's mobile companion and Remote Orca Servers are beta. Their desktop/server r
 | `$sks-mad-sks` / `sks mad-sks` | Single high-risk MAD route for scoped permission widening plus SQL-plane execution, including read-back proof and profile closure. |
 | `$sks-review` / `sks review --staged` | Reviews diffs with `evidence: machine` findings sorted above `evidence: llm`. |
 
-`sks --mad` now prioritizes the interactive ready path: independent macOS config probes run concurrently, failed read-only preflight does not repeat mutation-capable repair inspection, verified Zellij/codex-lb evidence is reused, and the remote Zellij update lookup runs after the UI is ready. Existing unreadable or malformed config still blocks safely; pass an explicit repair flag such as `--repair-config` when repair is intended.
+`sks --mad` now prioritizes the interactive ready path: independent macOS config probes run concurrently, failed read-only preflight does not repeat mutation-capable repair inspection, and verified Codex evidence is reused. Existing unreadable or malformed config still blocks safely; pass an explicit repair flag such as `--repair-config` when repair is intended.
 
 ## Naruto Workflow
 
-`$sks-naruto` and `sks naruto run "task" --agents 8 --max-threads 12` use Codex official subagents. Standalone and Codex App tasks that request project-host database, spreadsheet, or render tools require the non-persistent `--trusted-project` flag after the operator reviews the checkout; an App session ID scopes evidence but does not grant trust. The parent is GPT-5.6 Sol Max. Tiny mechanical `worker` slices use Luna Max; ordinary UI, logic, backend, and native coding uses Sol High; review, testing, debugging, architecture, integration, security, database, research, release, and other judgment-sensitive work uses Sol Max; long-context scans and direct Computer Use, Browser/Chrome, or image-generation execution uses Terra Medium. Mixed execution/judgment work is split when possible, and unsplittable judgment defaults to Sol Max.
+`$sks-naruto` and `sks naruto run "task" --agents 8 --max-threads 12` use Codex official subagents. Standalone and Codex App tasks that request project-host database, spreadsheet, or render tools require the non-persistent `--trusted-project` flag after the operator reviews the checkout; an App session ID scopes evidence but does not grant trust. The parent is GPT-5.6 Sol Max. Tiny mechanical `worker` slices—including clear simple code, configuration, and setup changes—use Luna Max; ordinary UI, logic, backend, and native coding uses Sol High; review, testing, debugging, architecture, integration, security, database, research, release, and other judgment-sensitive work uses Sol Max; long-context scans, long-term memory, large-scale first-draft code processing, and direct Computer Use, Browser/Chrome, or image-generation execution use Terra Max. Mixed execution/judgment work is split when possible, and unsplittable judgment defaults to Sol Max.
+
+Fresh SKS-owned project config enables Codex 0.145+ multi-agent V2 with `agents.max_concurrent_threads_per_session = 256`, `features.multi_agent_v2.max_concurrent_threads_per_session = 257`, `max_depth = 1`, and `interrupt_message = true`. Nested delegation remains forbidden. Explicit user-owned limits are preserved, while legacy SKS-owned 12/13 defaults migrate to 256/257.
 
-Fresh SKS-owned project config enables Codex 0.145+ multi-agent V2 with `agents.max_concurrent_threads_per_session = 12`, `features.multi_agent_v2.max_concurrent_threads_per_session = 13`, `max_depth = 1`, and `interrupt_message = true`. Nested delegation remains forbidden. Explicit user limits are preserved, and larger requests run in waves.
+Naruto's automatic starting tiers are 4/6/8 children for ordinary work and 16
+for mass cheap-model work. After decomposition, either lane may expand to the
+SKS-owned ceiling of 256 independent useful children. Explicit
+`--agents N` and `--max-threads N` values from 1 through 256 remain
+authoritative instead of being reduced to those automatic tiers. A first wave
+may reach 256 child slots only when independent ready work, disjoint ownership,
+verifier/tool capacity, and the external Codex/session host all permit it;
+otherwise Naruto records the exact active limiter and reuses returned capacity
+in later waves.
 
-Naruto's automatic tiers are 4/6/8 children for ordinary work and 16 for
-mass cheap-model work, with automatic ceilings of 12 and 64 respectively.
-The absolute `--agents`/`--max-threads` frame ceiling is 256, and requests
-beyond current capacity reuse slots across waves. `SKS_NARUTO_REMOTE_API_PARALLEL_BUDGET`
-can lower the governor's remote API parallel-request budget. These are structural
-scheduling limits, not a recommended target or proof that 256 live agents were
-load-tested on the current host; CPU, memory, file descriptors, process/worktree
-capacity, ready work, and verifier capacity can select a much smaller active wave.
+`SKS_NARUTO_REMOTE_API_PARALLEL_BUDGET` declares a lower remote provider/API
+parallel-request budget for the governor. It cannot raise a lower external-host
+or session limit. The official Codex lane does not impose a local CPU/RAM or
+unmeasured API-default clamp; it follows an explicit provider budget and a
+measured host cap. The 256 ceiling is structural, not a recommendation or proof
+that 256 live agents were load-tested on the current host. The four GPT-5.6
+model profiles are routing lanes, not an agent-count limit.
 
 Gates are task-profile aware: greetings and answer-only turns create no mission gate; tiny work gets minimal verification; parallel work gets scoped ownership and verification; high-risk work keeps the full safety gates. `SubagentStart`/`SubagentStop` prove lifecycle only. Completion also requires `subagent-parent-summary.json` with one trustworthy structured outcome per thread, correlated with `subagent-events.jsonl` and `subagent-evidence.json`.
 
 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 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.
+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. Official event evidence and the parent verdict—not display state—determine completion.
 
 Official subagent requests use `--agents`; removed scheduler, pool, backend, and model flags fail closed.
 
@@ -123,13 +236,13 @@ sks naruto run "task" \
 | 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 |
+| Parent model / effort | `--parent-model`, `--parent-effort` | `SKS_NARUTO_PARENT_MODEL`, `SKS_NARUTO_PARENT_EFFORT` | Overrides the built-in parent policy; GPT-5.6 parents remain Sol/Terra/Luna Max-only as applicable |
+| Subagent model / effort | `--subagent-model`, `--subagent-effort` | `SKS_NARUTO_SUBAGENT_MODEL`, `SKS_NARUTO_SUBAGENT_EFFORT` | Overrides the default subagent policy; GPT-5.6 Luna/Terra require Max and Sol requires High or Max |
 
 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.
+- **A malformed or policy-invalid 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`, a GPT-5.6 Luna/Terra effort other than 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.
 
@@ -214,7 +327,7 @@ Adapter rules that keep updates safe:
 | Did tests/typecheck fail? | Another model may say so. | Machine check output is tagged `evidence: machine`. |
 | Are findings ranked? | Usually one blended opinion. | Machine evidence sorts before LLM findings. |
 | Can work stop? | The model decides. | Stop gates, Completion Proof, and Honest Mode decide. |
-| Can I inspect agent-thread progress? | Usually no runtime UI. | Use the official Codex subagent/thread surfaces and SKS Zellij monitor/viewport panes. |
+| Can I inspect agent-thread progress? | Usually no runtime UI. | Use the official Codex subagent/thread surfaces and their proof artifacts. |
 
 ## Demo
 
@@ -234,10 +347,10 @@ 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 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.
+- 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. A selected route is green only after one measured request records the destination host, gateway-key authentication class, measurement time, and latency; config presence alone is not routing proof.
 - 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.
+- Release gates: `npm run release:check:affected` for ordinary change-aware verification and `npm run release:check:confidence` for the final local confidence pass. Evidence for the 8.0.4 physical checklist includes a successful old-install-to-8.0.4 resolved-CLI upgrade, a 5,001-directory update scan, exactly one running Menu Bar process at the current package version, one measured real codex-lb request to the selected remote host, and one Telegram command/reply E2E over cellular.
+- Release preparation: typecheck, one clean build, focused tests, affected/confidence gates, all four source-bound physical receipts, then `npm publish --dry-run --json --registry https://registry.npmjs.org/ --tag latest --access public`. The dry-run does not publish or require release tags; real staging/publication remains a separate authenticated maintainer workflow.
 - Release readiness notes: [docs/release-readiness.md](docs/release-readiness.md) and [CHANGELOG.md](CHANGELOG.md)
 - Image generation review routes require Codex App `$imagegen`/`gpt-image-2` evidence with recorded output hashes; direct API fallback and mock fixtures do not satisfy full route gates.
 
@@ -248,22 +361,22 @@ It shows the current quickstart flow: one-line install, `$sks-plan`, `sks review
 - macOS optional: menu bar integration and `/usr/bin/open`
   - The menubar icon shows and hides itself automatically as the Codex desktop app launches/quits; set `quit_with_codex: true` in `~/.codex/sks-menubar/config.json` to have the menubar fully quit with Codex instead of just hiding (default `false`).
   - Native input dialogs (API keys, codex-lb setup) pass secrets to `sks` via `--api-key-stdin` instead of a visible Terminal window or process arguments.
-  - Codex Desktop always keeps its real ChatGPT OAuth identity. codex-lb setup stores a separate gateway endpoint/key in an owner-only `0600` env file and never replaces `~/.codex/auth.json`; Keychain requests fail closed until a dedicated signed helper is available.
+  - Codex Desktop keeps `~/.codex/auth.json` byte-preserved. **Use codex-lb** atomically stores the provider definition and active top-level selection and resolves its separate gateway key from the owner-only `0600` env file; while selected, requests must not consume the stored ChatGPT OAuth identity. Turning codex-lb off returns to the official OAuth path. Keychain requests fail closed until a dedicated signed helper is available.
   - Explicit codex-lb setup/reconfiguration migrates the retired generic `sks-codex-lb` Keychain item only after the replacement owner-only store is verified, deletes only the exact legacy account, and proves absence by readback. If cleanup cannot be proved, the replacement store is retained and the provider key should be rotated.
-  - Providers separates **Desktop Full Capability**, **CLI Provider**, and **Capability Matrix**. Desktop Full Capability keeps the built-in OpenAI provider and routes supported traffic through a loopback bridge; CLI Provider is selected only for the CLI process.
+  - Providers exposes atomic **Use codex-lb** / **Use ChatGPT OAuth** selection plus shared RoutingTruth. A green codex-lb state requires one measured request to the configured remote base URL; the Menu Bar and Doctor render the same host, authentication class, measurement time, and latency.
   - The retired dual-auth compatibility mode is detected only for safe migration. It cannot be activated or reported ready because it would require a global GUI secret.
-  - Authentication and routing modes do not toggle Codex App's native model picker, Fast, image, Browser Use, Computer Use, voice, plugins/apps, or other built-in surfaces. Capability status describes evidence for the codex-lb data path, not permission to use the native feature.
+  - Authentication and routing modes do not toggle Codex App's native model picker, Fast, image, Browser Use, Computer Use, voice, plugins/apps, or other built-in surfaces. Capability status describes measured evidence for the codex-lb data path, not permission to use a native feature.
   - `sks update`, setup, repair, and routing changes preserve OAuth, user model/reasoning/Fast settings, unknown catalog fields, and unrelated provider configuration. Legacy shared-auth routing requires explicit `sks codex-lb migrate-legacy-desktop --restart-app`; without a real restart and post-restart identity check it cannot finalize a migration receipt.
   - The remote codex-lb service remains independently hosted and operated. SKS uses only the configured URL and gateway key; it does not deploy, restart, or change credentials on that host.
-  - Full release proof blocks with `real_required_missing` until fresh trust-anchored evidence covers the real Desktop feature/lifecycle matrix and the separately hosted other-Mac runtime; fixtures and configuration cannot satisfy that boundary.
-  - Update installs always rebuild the companion with the newly installed SKS package, preventing a previous-version updater from restoring a stale menu binary.
+  - Full release proof blocks with `real_required_missing` until fresh trust-anchored evidence covers the real Desktop feature/lifecycle matrix, one measured gateway-key request to the selected separately hosted codex-lb instance, and the other-Mac runtime; fixtures and configuration cannot satisfy that boundary.
+  - Update installs stop and verify every prior Menu Bar process before replacement, rebuild the companion from the newly installed SKS package, bootstrap it, and require exactly one running process whose version probe equals the current package version.
+  - Telegram remote control uses one bounded long-poller inside that same Menu Bar process. Release evidence must include a real cellular command/reply round trip; `getMe`, a local fixture, or a configured token alone cannot satisfy the E2E gate.
   - The menubar dropdown's `View Last Log` item opens the most recent background action's log file, so you don't need to keep a Terminal window open to see command output.
   - `Manage MCP Servers…` provides a resizable native table and add/remove/enable/disable controls for global Codex MCP configuration. Secret environment values and command arguments are accepted through native dialogs/stdin but omitted from list output and logs.
   - `sks menubar status --json` reports a `codex_sync` object with `bundle_id`, `codex_running`, and `icon_visible_expected` to show Codex-lifecycle detection state.
   - The menu displays the installed Codex CLI version, adds an `⬆` status icon when `sks codex update-status` sees a newer release, runs the official self-updater through `Update Codex CLI Now`, and exposes `Run sks doctor --fix` as a background repair action.
   - **Codex Fast** is labeled as the official 1.5× Codex speed option, with a verified service-tier status row and direct On/Off actions. Center explains that ChatGPT-sign-in GPT-5.6/GPT-5.5 use 2.5× Standard credits and GPT-5.4 uses 2×, while API-key token pricing and API Priority processing are separate. Model selection, Codex-Spark, and reasoning effort remain independent; status failures render as unavailable with neither choice falsely selected.
 - If Codex shows `[No tool output found for custom tool call ...]`, SKS blocks reuse of that structurally ambiguous thread. Upgrade codex-lb or run `sks codex-lb disable`, inspect possible side effects, then continue the persisted mission in a fresh Codex task. SKS never rewrites session JSONL or fabricates a successful tool output.
-- Zellij optional but recommended for terminal worker panes
 
 ## License
 

package/config/skills-hash-ledger.v1.json

@@ -38,7 +38,7 @@
     { "canonical_name": "sks-init-deep", "trusted_sha256": ["a679fa4ba36e070de5753994f58595c4352302cc98d868ba70ff98305d15f451"] },
     { "canonical_name": "sks-loop", "trusted_sha256": ["e56f9c4d0f7227961779daf6806943f1926bb588ce21a965a813e8ad91cfd5c8"] },
     { "canonical_name": "sks-mad-sks", "trusted_sha256": ["03fb5063d19c3d48d004cd8e6e39bfe244016d7edacfe99e5dab087cbbfa6db9", "a3d0110ca97576130893311b3267621acb02c16ca9aea4b2da3e5300eea58158"] },
-    { "canonical_name": "sks-naruto", "trusted_sha256": ["f8e808622e222b4ad7dcb2907e5f06a890db83139ae443ec6c8c33781dfa3e37", "49b5e3dcc1b537b49c2cf09e5b875cb16acb05c622b22798e265e64dacd8ac90"] },
+    { "canonical_name": "sks-naruto", "trusted_sha256": ["d0d5968e78ac25e1d3e588735de1ddbcf149cfb3165edebca5dec1ed7c7a5c46", "34222c72e4e1ead3584907f4d905444b7de820283ee7348018f110d5e6b04461", "f8e808622e222b4ad7dcb2907e5f06a890db83139ae443ec6c8c33781dfa3e37", "49b5e3dcc1b537b49c2cf09e5b875cb16acb05c622b22798e265e64dacd8ac90"] },
     { "canonical_name": "sks-performance-evaluator", "trusted_sha256": ["5b8c6cea19ffda8e434700297ed060fde3cfcfc9c98635402599e84756466db4", "c0bfd5a2e6c74813cb5dac9dadd4c7543ee768a48cf3e36b86b3d9306c2712c6"] },
     { "canonical_name": "sks-pipeline-runner", "trusted_sha256": ["020ba4da2f96bcda23cee4596b1e790816780178f1917dee748ff4b289cba0e5", "ffcbe0ea4b585e3d2886f1d9fa7a3b88706aaf42182fb177b2371b76beb0ddcd"] },
     { "canonical_name": "sks-plan", "trusted_sha256": ["7795867b38a5f169924125850f137c31995cf28000f74284839530a68ace156a", "b6f3b09230e9809acf4e13df2de6af3c75a8534e8890d6560664ebfc2e4072f8"] },

package/crates/sks-core/Cargo.lock

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

package/crates/sks-core/Cargo.toml

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

package/dist/bin/fast-inline.js

@@ -13,11 +13,7 @@ function rootJsonFastInline(fs, cwd = process.cwd()) {
 }
 async function doctorJsonFastInline(input = {}) {
     const startedAt = Date.now();
-    const { inspectOAuthCallbackPortConflict, oauthCallbackDoctorGuidance } = await import('../core/codex/oauth-callback-port-diagnostic.js');
-    const oauthCallbackPortDiagnostic = await inspectOAuthCallbackPortConflict({
-        ...(input.run ? { run: input.run } : {})
-    });
-    const oauthCallbackOperatorActions = oauthCallbackDoctorGuidance(oauthCallbackPortDiagnostic);
+    const secretResolution = await inspectCodexLbSecretResolutionFastInline(input);
     const write = input.write || ((text) => process.stdout.write(text));
     write(`${JSON.stringify({
         schema: 'sks.doctor-status.v3',
@@ -38,20 +34,6 @@ async function doctorJsonFastInline(input = {}) {
             hook_evidence_policy: 'unknown-do-not-count',
             agent_role_strategy: 'message-role'
         },
-        zellij_readiness: {
-            schema: 'sks.zellij-readiness.v1',
-            binary: 'zellij',
-            status: 'skipped',
-            min_version: '0.41.0',
-            version: null,
-            required_for: ['sks --mad', 'interactive lane UI'],
-            layout_proof: 'unavailable',
-            pane_proof: 'unavailable',
-            screen_proof: 'unavailable',
-            mad_ready: false,
-            cli_ready: false,
-            ready_for_interactive_runtime: false
-        },
         codex: { bin: null, version: null, available: null, skipped: true, reason: 'fast_readonly_json' },
         repair: {
             setup: null,
@@ -59,12 +41,10 @@ async function doctorJsonFastInline(input = {}) {
         },
         doctor_fix_transaction: null,
         blockers: [],
-        warnings: [
-            'fast_readonly_doctor_skipped_optional_deep_diagnostics',
-            ...oauthCallbackPortDiagnostic.warnings
-        ],
-        operator_actions: oauthCallbackOperatorActions,
-        oauth_callback_port_diagnostic: oauthCallbackPortDiagnostic
+        warnings: ['fast_readonly_doctor_skipped_optional_deep_diagnostics'],
+        codex_lb: {
+            secret_resolution: secretResolution
+        }
     }, null, 2)}\n`);
 }
 async function narutoHelpJsonFastInline() {
@@ -125,12 +105,60 @@ function findProjectRootSync(fs, start) {
         dir = parent;
     }
 }
+async function inspectCodexLbSecretResolutionFastInline(input) {
+    const processEnv = input.processEnv || process.env;
+    const home = input.home || processEnv.HOME || processEnv.USERPROFILE || process.cwd();
+    const codexHome = joinPath(home, '.codex');
+    const envPath = joinPath(codexHome, 'sks-codex-lb.env');
+    const metadataPath = joinPath(codexHome, 'sks-codex-lb.json');
+    const [{ inspectConfinedPath }, { readPrivateCredentialFile }] = await Promise.all([
+        import('../core/managed-path-safety.js'),
+        import('../core/security/private-credential-file.js')
+    ]);
+    let envFilePresent = false;
+    let envFilePrivate = false;
+    try {
+        const inspected = await inspectConfinedPath(codexHome, envPath);
+        envFilePresent = inspected.exists;
+        const expectedUid = typeof process.getuid === 'function' ? process.getuid() : null;
+        envFilePrivate = inspected.exists
+            && !inspected.leafSymlink
+            && inspected.stat?.isFile() === true
+            && (inspected.stat.mode & 0o777) === 0o600
+            && (expectedUid === null || inspected.stat.uid === expectedUid);
+    }
+    catch {
+        envFilePresent = false;
+    }
+    let metadataValid = false;
+    if (envFilePrivate) {
+        try {
+            const snapshot = await readPrivateCredentialFile(codexHome, metadataPath, 'codex_lb_metadata', { maxBytes: 64 * 1024 });
+            const metadata = JSON.parse(snapshot.bytes.toString('utf8'));
+            metadataValid = metadata?.schema === 'sks.codex-lb-metadata.v1'
+                && /^[a-f0-9]{64}$/.test(String(metadata?.api_key?.sha256 || '').trim().toLowerCase())
+                && Boolean(String(metadata?.base_url || '').trim());
+        }
+        catch {
+            metadataValid = false;
+        }
+    }
+    const processKeyPresent = Boolean(String(processEnv.CODEX_LB_API_KEY || '').trim());
+    const source = envFilePrivate && metadataValid ? 'env-file' : processKeyPresent ? 'process.env' : 'missing';
+    return {
+        source,
+        path: source === 'env-file' || envFilePresent ? envPath : null,
+        prompt_risk: (input.platform || process.platform) === 'darwin'
+            ? 'unknown_keychain_not_probed'
+            : 'none'
+    };
+}
 function fsInline() {
     return process.getBuiltinModule?.('node:fs') || require('node:fs');
 }
-function readJsonSyncInline(file) {
+function readJsonSyncInline(file, fs = fsInline()) {
     try {
-        return JSON.parse(fsInline().readFileSync(file, 'utf8'));
+        return JSON.parse(fs.readFileSync(file, 'utf8'));
     }
     catch {
         return null;

package/dist/bin/install.js

@@ -1,33 +1,7 @@
 #!/usr/bin/env node
-const { spawnSync } = require('node:child_process');
-const args = process.argv.slice(2);
-const command = args.find((arg) => !arg.startsWith('-')) || 'install';
-const autonomous = args.includes('--no-tui') || args.includes('--yes') || args.includes('-y');
-function run(cmd, cmdArgs) {
-    const result = spawnSync(cmd, cmdArgs, { stdio: 'inherit' });
-    return result.status ?? 1;
-}
-if (!['install', 'setup', 'bootstrap'].includes(command)) {
-    console.error('Usage: npx sneakoscope install [--yes|--no-tui]');
-    process.exit(2);
-}
-console.log('SKS installer - proof-first Codex harness');
-const already = spawnSync('sks', ['--version'], { encoding: 'utf8' });
-if (already.status !== 0) {
-    console.log('> installing global package (npm i -g sneakoscope)...');
-    if (run('npm', ['install', '-g', 'sneakoscope']) !== 0) {
-        console.error('global install failed - check npm permissions');
-        process.exit(1);
-    }
-}
-console.log('> repairing/validating environment (sks doctor --fix)...');
-if (run('sks', ['doctor', '--fix', ...(autonomous ? ['--yes'] : [])]) !== 0) {
-    console.error('doctor reported blockers - see report above');
-    process.exit(1);
-}
-console.log(`
-SKS ready. 다음 3개만 기억하세요 (Codex 입력창에서):
-   $sks-plan "무엇을 만들지" - 계획만 세움 (코드 안 건드림)
-   $sks-work                 - 계획을 증거 기반으로 실행
-   실행 상태: sks status --json / zellij 세션은 자동
-`);
+import('../core/commands/install-package-command.js')
+  .then(({ installPackageCommand }) => installPackageCommand())
+  .catch((error) => {
+    console.error(error instanceof Error ? error.message : String(error));
+    process.exitCode = 1;
+  });

package/dist/bin/sks-dispatch.js

@@ -13,7 +13,7 @@ async function runSks(args) {
         const { rootJsonFastInline } = await import('./fast-inline.js');
         rootJsonFastInline(fs);
     }
-    else if (args[0] === 'doctor' && args.includes('--json') && !args.includes('--report-file') && !args.includes('--fix') && !args.includes('--full') && !args.includes('--capabilities') && !args.includes('--search')) {
+    else if (args[0] === 'doctor' && args.includes('--json') && !args.includes('--report-file') && !args.includes('--fix') && !args.includes('--full') && !args.includes('--capabilities') && !args.includes('--profile') && !args.includes('--search')) {
         const { doctorJsonFastInline } = await import('./fast-inline.js');
         await doctorJsonFastInline();
     }

package/dist/cli/args.js

@@ -42,9 +42,7 @@ export function positionalArgs(args = []) {
         '--write-mode',
         '--max-write-agents',
         '--service-tier',
-        '--zellij-session-name',
         '--worker-placement',
-        '--zellij-visible-pane-cap',
         '--phase',
         '--message',
         '--role',

package/dist/cli/cli-theme.js

@@ -1,24 +1,33 @@
 import { PACKAGE_VERSION } from '../core/version.js';
-import { ANSI_CODES, paint, resolveZellijTheme } from '../core/zellij/zellij-theme.js';
-const theme = resolveZellijTheme();
+const ANSI_CODES = {
+    reset: '\x1b[0m',
+    dim: '\x1b[2m',
+    red: '\x1b[31m',
+    green: '\x1b[32m',
+    yellow: '\x1b[33m'
+};
+const colorEnabled = process.env.NO_COLOR !== '1' && process.stdout.isTTY !== false;
+function paint(code, text) {
+    return colorEnabled && code ? `${code}${text}${ANSI_CODES.reset}` : text;
+}
 export const ui = {
     banner(cmd) {
-        console.log(paint(theme, ANSI_CODES.dim, `SKS ${PACKAGE_VERSION} · ${cmd}`));
+        console.log(paint(ANSI_CODES.dim, `SKS ${PACKAGE_VERSION} · ${cmd}`));
     },
     ok(msg) {
-        console.log(`${paint(theme, ANSI_CODES.green, '✔')} ${msg}`);
+        console.log(`${paint(ANSI_CODES.green, '✔')} ${msg}`);
     },
     warn(msg) {
-        console.log(`${paint(theme, ANSI_CODES.yellow, '▲')} ${msg}`);
+        console.log(`${paint(ANSI_CODES.yellow, '▲')} ${msg}`);
     },
     fail(msg) {
-        console.log(`${paint(theme, ANSI_CODES.red, '✖')} ${msg}`);
+        console.log(`${paint(ANSI_CODES.red, '✖')} ${msg}`);
     },
     step(msg) {
-        console.log(`${paint(theme, ANSI_CODES.dim, '>')} ${msg}`);
+        console.log(`${paint(ANSI_CODES.dim, '>')} ${msg}`);
     },
     kv(k, v) {
-        console.log(`  ${paint(theme, ANSI_CODES.dim, k.padEnd(18))} ${v}`);
+        console.log(`  ${paint(ANSI_CODES.dim, k.padEnd(18))} ${v}`);
     },
     table(rows) {
         if (!rows.length)
@@ -26,7 +35,7 @@ export const ui = {
         const widths = rows[0]?.map((_cell, index) => Math.max(...rows.map((row) => String(row[index] || '').length))) || [];
         for (const [rowIndex, row] of rows.entries()) {
             const line = row.map((cell, index) => String(cell || '').padEnd(widths[index] || 0)).join('  ').trimEnd();
-            console.log(rowIndex === 0 ? paint(theme, ANSI_CODES.dim, line) : line);
+            console.log(rowIndex === 0 ? paint(ANSI_CODES.dim, line) : line);
         }
     }
 };

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

@@ -14,9 +14,11 @@ const COMMAND_MANIFEST_LITE_BASE = [
     { name: 'status', summary: 'Show concise active mission and trust status', maturity: 'stable', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
     { name: 'review', summary: 'Review a git diff with machine evidence first', maturity: 'stable', allowedDuringActiveRoute: true },
     { name: 'root', summary: 'Show active SKS root', maturity: 'stable', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
+    { name: 'install', summary: 'Install the exact packaged SKS version globally and verify the resolved CLI', maturity: 'stable', skipMigrationGate: true },
     { name: 'update', summary: 'Inspect, review, apply, or roll back the global SKS update', maturity: 'stable' },
     { name: 'uninstall', summary: 'Uninstall SKS global skills, hooks, config, menu bar, and optional project residue', maturity: 'stable', allowedDuringActiveRoute: true },
     { name: 'update-check', summary: 'Show the shared SKS, Codex CLI, and Menu Bar update status', maturity: 'stable', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
+    { name: 'config', summary: 'Adopt project Codex config into SKS management', maturity: 'stable', skipMigrationGate: true },
     { name: 'mcp', summary: 'Manage scoped Codex MCP configuration', maturity: 'beta', skipMigrationGate: true },
     { name: 'wizard', summary: 'Open setup wizard help', maturity: 'stable' },
     { name: 'usage', summary: 'Show focused usage topic', maturity: 'stable', readonly: true, allowedDuringActiveRoute: true, diagnostic: true },
@@ -37,13 +39,8 @@ const COMMAND_MANIFEST_LITE_BASE = [
     { name: 'codex-lb', summary: 'Inspect codex-lb status and circuit health', maturity: 'beta', skipMigrationGate: true },
     { name: 'menubar', summary: 'Inspect/install/restart/uninstall SKS menu bar', maturity: 'beta', skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
     { name: 'remote', summary: 'Inspect official Remote readiness and run the proof-aware SSH stdio worker', maturity: 'beta' },
+    { name: 'telegram', summary: 'Pair and inspect the Telegram remote-control transport', maturity: 'beta', skipMigrationGate: true },
     { name: 'hooks', summary: 'Explain and inspect Codex hooks', maturity: 'beta', skipMigrationGate: true },
-    { name: 'zellij-lane', summary: 'Render a Zellij lane frame for SKS sessions', maturity: 'beta' },
-    { name: 'zellij-slot-pane', summary: 'Render a compact Zellij worker slot pane', maturity: 'beta' },
-    { name: 'zellij-monitor-pane', summary: 'Render the live Zellij MAD/Naruto monitor pane', maturity: 'beta', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
-    { name: 'zellij-viewport-pane', summary: 'Render a dynamically bound Zellij worker viewport pane', maturity: 'beta', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
-    { name: 'zellij-slot-column-anchor', summary: 'Render the compact SLOTS anchor pane for first-slot-down Zellij stacks', maturity: 'beta' },
-    { name: 'zellij', summary: 'Inspect Zellij runtime status and explain repair (no auto-install)', maturity: 'beta', skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
     { name: 'mad-sks', summary: 'MAD-SKS scoped permission modifier + SQL-plane execution', maturity: 'beta', mutatesRouteState: true },
     { name: 'auto-review', summary: 'Manage auto-review profile', maturity: 'beta' },
     { name: 'dollar-commands', summary: 'List Codex App dollar commands', maturity: 'stable', readonly: true, skipMigrationGate: true, allowedDuringActiveRoute: true, diagnostic: true },
@@ -116,6 +113,7 @@ const COMMAND_CONTRACT_OVERRIDES_LITE = {
     check: { risk: 'R1', latency: 'long' },
     'commit-and-push': { risk: 'R3' },
     'computer-use': { latency: 'long' },
+    config: { risk: 'R2', supportsJson: true, remoteAllowed: false, inputProfile: 'json-only' },
     dfix: { latency: 'long' },
     'dollar-commands': { risk: 'R2', latency: 'normal' },
     eval: { latency: 'long' },
@@ -124,6 +122,7 @@ const COMMAND_CONTRACT_OVERRIDES_LITE = {
     },
     harness: { latency: 'long' },
     'image-ux-review': { latency: 'long' },
+    install: { risk: 'R2', latency: 'long' },
     loop: { latency: 'long' },
     'mad-sks': { risk: 'R3', latency: 'long' },
     mcp: { risk: 'R2', latency: 'long', supportsJson: true, inputProfile: 'json-only' },
@@ -165,6 +164,7 @@ const COMMAND_CONTRACT_OVERRIDES_LITE = {
         requiredCapabilities: ['proof.stop-gate']
     },
     task: { risk: 'R1', latency: 'long' },
+    telegram: { risk: 'R2', supportsJson: true, remoteAllowed: false, inputProfile: 'json-only' },
     trust: {
         risk: 'R0', latency: 'fast', supportsJson: true, remoteAllowed: true, inputProfile: 'trust', requiredCapabilities: ['proof.trust']
     },