trackops 1.1.0 → 2.0.0

package/skills/trackops/references/activation.md

@@ -2,38 +2,72 @@
 
 ## Global install
 
-The marketplace skill prepares TrackOps globally for the agent. It must not create repo files by itself.
-
-Install it with:
+Install the marketplace skill:
 
 ```bash
-npx skills add Baxahaun/trackops --skill trackops --full-depth --global --agent codex -y
+npx skills add Baxahaun/trackops
 ```
 
-Replace `codex` with any supported target: `antigravity`, `claude-code`, `codex`, `cursor`, `gemini-cli`, `github-copilot`, or `kiro-cli`.
-
-Before using TrackOps commands, run:
+On first use, ensure the runtime with:
 
 ```bash
 node scripts/bootstrap-trackops.js
 ```
 
-That bootstrap validates prerequisites, installs or updates the TrackOps runtime, and records state in `~/.trackops/runtime.json`.
+The global skill must not create repository files by itself.
 
 ## Local activation
 
-Inside a repository, the normal flow is:
+Inside a repository:
 
 ```bash
 trackops init
 trackops opera install
 ```
 
-Rules:
+By default, `trackops init` creates a split workspace with:
+
+- `app/`
+- `ops/`
+- `/.env`
+- `/.env.example`
+- `.trackops-workspace.json`
+
+## OPERA routing
+
+OPERA always starts by classifying:
+
+- technical level
+- project state
+- documentation state
+
+If the project is still early or the user is non-technical, TrackOps writes:
+
+- `ops/bootstrap/agent-handoff.md`
+- `ops/bootstrap/agent-handoff.json`
+
+The agent then produces:
+
+- `ops/bootstrap/intake.json`
+- `ops/bootstrap/spec-dossier.md`
+- `ops/bootstrap/open-questions.md` when needed
 
-- Use `trackops init` when the repo is not yet managed by TrackOps.
-- By default, `trackops init` creates a split workspace with `app/`, `ops/`, `/.env`, `/.env.example`, and `.trackops-workspace.json`.
-- Use `trackops opera install` only after `trackops init` and only when the user wants OPERA.
-- Use `trackops init --with-opera` only as an explicit shortcut.
-- Use `trackops init --legacy-layout` only for compatibility with the old single-root layout.
-- Never assume that a global skill install authorizes local repo mutations by default.
+When the quality gate passes, OPERA compiles:
+
+- `ops/contract/operating-contract.json`
+- `ops/genesis.md`
+- `ops/policy/autonomy.json`
+
+Resume with:
+
+```bash
+trackops opera bootstrap --resume
+```
+
+Locale controls:
+
+```bash
+trackops locale get
+trackops locale set en
+trackops doctor locale
+```

package/skills/trackops/references/troubleshooting.md

@@ -2,33 +2,48 @@
 
 ## Missing prerequisites
 
-- If Node is missing or older than 18, install Node 18+ first.
-- If npm is missing, install a Node distribution that includes npm.
+- Install Node 18+ if Node is missing or too old.
+- Install a Node distribution that includes npm if npm is missing.
 
-## skills cannot find the TrackOps skill
+## Global install command failed
 
-- Install from the repository root:
-  `npx skills add Baxahaun/trackops --skill trackops --full-depth --global --agent codex -y`
-- Confirm the remote repository already contains the latest committed skill changes.
-- Remember that skills installs from committed Git state, not from uncommitted local changes.
+- Install from committed GitHub state:
+  `npx skills add Baxahaun/trackops`
+- Then ensure the local runtime with:
+  `node scripts/bootstrap-trackops.js`
+- If the install succeeded but the CLI still looks unavailable, confirm that `~/.trackops/runtime.json` exists.
 
-## Global npm install failed
+## Runtime bootstrap failed
 
-- Re-run `node scripts/bootstrap-trackops.js` and inspect stderr.
-- If npm global permissions are blocked, configure a user-writable npm prefix instead of relying on `sudo`.
+- Re-run `node scripts/bootstrap-trackops.js`.
+- If npm global permissions fail, configure a user-writable npm prefix instead of using `sudo`.
 
-## Runtime cannot be verified
+## OPERA routed bootstrap to the agent
 
-If installation succeeds but `trackops` is still not executable:
+This is expected when:
 
-- Check whether the npm global bin directory is on `PATH`.
-- Re-open the terminal after updating shell profile settings.
-- Re-run `node scripts/bootstrap-trackops.js` once `trackops --version` works.
+- the user is non-technical
+- the project is still in idea stage
+- documentation is weak
 
-## Workspace environment looks inconsistent
+Use:
 
-If a split workspace is active and tools do not see the expected environment file:
+```bash
+trackops opera handoff --print
+trackops opera bootstrap --resume
+```
 
-- Run `trackops env status` to inspect required, present, and missing keys without exposing values.
-- Run `trackops env sync` to recreate `/.env`, `/.env.example`, and the `app/.env` bridge.
-- If bridge mode is `copy`, do not edit `app/.env` directly; TrackOps regenerates it from the root `.env`.
+## Resume does not complete
+
+TrackOps will not invent missing context.
+
+Check that both files exist and contain usable data:
+
+- `ops/bootstrap/intake.json`
+- `ops/bootstrap/spec-dossier.md`
+
+## Environment looks inconsistent
+
+- Run `trackops env status`.
+- Run `trackops env sync`.
+- If bridge mode is `copy`, do not edit `app/.env` directly.

package/skills/trackops/references/workflow.md

@@ -1,20 +1,26 @@
 # Workflow
 
-Once TrackOps is active in a repository, operate in this order:
+Once TrackOps is active in a repository:
 
-1. Run `trackops status` to inspect focus, phase, blockers, and repo state.
-2. Run `trackops next` to identify the next ready task.
-3. Update task state with `trackops task ...` as work progresses.
-4. Run `trackops sync` after meaningful changes so generated docs stay aligned.
-5. Run `trackops env status` when the project depends on credentials or external services.
+1. Run `trackops status`.
+2. Run `trackops next`.
+3. Move task state with `trackops task ...`.
+4. Run `trackops sync` after meaningful changes.
+5. Run `trackops env status` when credentials matter.
 
 Operational rules:
 
 - In split workspaces, use `ops/project_control.json` as the source of truth.
-- In legacy repos, use `project_control.json` at repo root.
-- In split workspaces, generated operational docs live under `ops/`.
-- Product code lives under `app/`.
-- Use `/.env` for real secrets and `/.env.example` for the public environment contract.
+- Generated operational docs live in `ops/`.
+- Product code lives in `app/`.
+- Real secrets live in `/.env`.
+- Public environment contract lives in `/.env.example`.
 - `app/.env` is only a compatibility bridge.
-- If OPERA is installed, use `ops/genesis.md`, `ops/.agent/hub/`, and `ops/.agents/skills/_registry.md` as managed framework artifacts.
-- Keep the global skill layer separate from the local project layer.
+
+If OPERA is installed:
+
+- `ops/contract/operating-contract.json` holds the machine contract.
+- `ops/genesis.md` holds the compiled human view.
+- `ops/policy/autonomy.json` holds the executable autonomy policy.
+- `ops/bootstrap/` holds onboarding artifacts.
+- `ops/.agent/hub/` and `ops/.agents/skills/` hold managed agent artifacts.

package/skills/trackops/scripts/bootstrap-trackops.js

@@ -4,6 +4,7 @@ const fs = require("fs");
 const os = require("os");
 const path = require("path");
 const { spawnSync } = require("child_process");
+const runtimeState = require("../../../lib/runtime-state");
 
 const EXIT_CODES = {
   READY: 0,
@@ -129,10 +130,9 @@ function runInstall(config, prefix) {
 }
 
 function writeRuntimeStamp(config, verification) {
-  const runtimeDir = path.join(getHomeDir(), ".trackops");
-  const runtimeFile = path.join(runtimeDir, "runtime.json");
-  fs.mkdirSync(runtimeDir, { recursive: true });
-  const payload = {
+  const previous = runtimeState.readRuntimeState();
+  const payload = runtimeState.writeRuntimeState({
+    ...previous,
     skill: config.name,
     skillVersion: config.skillVersion,
     runtimePackage: config.npmPackage,
@@ -142,8 +142,8 @@ function writeRuntimeStamp(config, verification) {
     verifiedAt: new Date().toISOString(),
     verifiedWith: verification.installed.via,
     executable: verification.installed.command,
-  };
-  fs.writeFileSync(runtimeFile, `${JSON.stringify(payload, null, 2)}\n`, "utf8");
+  });
+  return payload;
 }
 
 function printInstallGuidance(prefix) {
@@ -157,7 +157,7 @@ function printInstallGuidance(prefix) {
   console.error("Add your npm global bin directory to PATH, reopen the terminal, and retry.");
 }
 
-function main() {
+async function main() {
   const config = readSkillConfig();
   const prefix = getPrefixOverride();
 
@@ -173,6 +173,7 @@ function main() {
 
   const current = verifyRuntime(config.trackopsVersion, prefix);
   if (current.ok) {
+    await runtimeState.ensureGlobalLocale({ interactive: false });
     writeRuntimeStamp(config, current);
     console.log(`TrackOps runtime ${config.trackopsVersion} is already ready.`);
     process.exit(EXIT_CODES.READY);
@@ -193,6 +194,7 @@ function main() {
     process.exit(EXIT_CODES.UNVERIFIABLE);
   }
 
+  await runtimeState.ensureGlobalLocale({ interactive: false });
   writeRuntimeStamp(config, verification);
   console.log(`TrackOps runtime ${config.trackopsVersion} is ready.`);
   process.exit(EXIT_CODES.READY);

package/skills/trackops/skill.json

@@ -1,9 +1,9 @@
 {
   "name": "trackops",
-  "shortDescription": "Global TrackOps skill for local project orchestration and operational automation with AI agents.",
-  "description": "Installs TrackOps as a global skill, prepares your agent for local project orchestration, ensures the runtime on first use, and guides per-project activation with optional OPERA.",
-  "skillVersion": "1.1.0",
-  "trackopsVersion": "1.1.0",
+  "shortDescription": "Global TrackOps skill for local project orchestration, agent coordination, bilingual onboarding, and operational automation.",
+  "description": "Installs TrackOps as a global skill, ensures the runtime on first use, lets users choose Spanish or English, activates local project orchestration, and routes OPERA onboarding into either direct bootstrap or agent-led discovery.",
+  "skillVersion": "2.0.0",
+  "trackopsVersion": "2.0.0",
   "npmPackage": "trackops",
   "bootstrapPolicy": "first_use",
   "supportedAgentsV1": [

package/templates/opera/agent.md

@@ -4,23 +4,24 @@
 Eres el agente principal del proyecto **{{PROJECT_NAME}}**. Operas bajo el protocolo O.P.E.R.A. v3.0.
 
 ## Fuente de Verdad
-Tu fuente de verdad es `genesis.md`. Antes de tomar cualquier decisión, consulta este archivo.
-Para el seguimiento operativo y el estado del backlog, usa `project_control.json`.
+Tu fuente de verdad de maquina es `ops/contract/operating-contract.json`.
+Tu vista humana compilada es `ops/genesis.md`.
+Para el seguimiento operativo y el estado del backlog, usa `ops/project_control.json`.
 
 ## Comportamiento
-- Sigue las reglas de comportamiento definidas en `genesis.md`.
-- Respeta la Matriz de Autonomía (Semáforo) para determinar qué acciones puedes tomar.
-- Gestiona tareas y estados desde `project_control.json`.
-- No edites manualmente `task_plan.md`, `progress.md` ni `findings.md`; se regeneran con `trackops sync`.
+- Sigue las reglas definidas en `ops/contract/operating-contract.json` y reflejadas en `ops/genesis.md`.
+- Respeta `ops/policy/autonomy.json` para determinar qué acciones puedes tomar sin aprobacion.
+- Gestiona tareas y estados desde `ops/project_control.json`.
+- No edites manualmente `ops/task_plan.md`, `ops/progress.md` ni `ops/findings.md`; se regeneran con `trackops sync`.
 
 ## Skills Disponibles
-Consulta `.agents/skills/_registry.md` para ver las skills instaladas.
+Consulta `ops/.agents/skills/_registry.md` para ver las skills instaladas.
 También puedes buscar nuevas skills con `trackops skill catalog`.
 
 ## Ciclo de Trabajo
 1. Ejecuta `trackops status` al inicio de cada bloque de trabajo.
-2. Consulta `genesis.md` para entender los datos y reglas.
+2. Consulta `ops/contract/operating-contract.json` y `ops/genesis.md` para entender el contrato y su vista humana.
 3. Usa `trackops next` para ver la siguiente cola priorizada.
 4. Antes de implementar, marca la tarea con `trackops task start <task-id>`.
-5. Usa el router (`.agent/hub/router.md`) para saber qué skill aplicar.
+5. Usa el router (`ops/.agent/hub/router.md`) para saber que skill aplicar.
 6. Al terminar, pasa la tarea a `review`, `complete` o `block` y ejecuta `trackops sync`.

package/templates/opera/architecture/dependency-graph.md

@@ -0,0 +1,24 @@
+# Dependency Graph
+
+```mermaid
+flowchart TD
+    A[Global runtime bootstrap] --> B[trackops init]
+    B --> C[trackops opera install]
+    C --> D{Routing}
+    D -->|direct_cli| E[Direct intake]
+    D -->|agent_handoff| F[agent-handoff.md/json]
+    F --> G[intake.json + spec-dossier.md]
+    E --> H[quality-report.json]
+    G --> H
+    H --> I[operating-contract.json]
+    I --> J[genesis.md]
+    I --> K[task_plan.md / progress.md / findings.md]
+    I --> L[dashboard + API state]
+    I --> M[env sync + policy enforcement]
+```
+
+## Notes
+
+- `ops/project_control.json` is the operational source of truth for backlog and session state.
+- `ops/contract/operating-contract.json` is the machine contract.
+- `ops/genesis.md` is a compiled human view.

package/templates/opera/architecture/runtime-automation.md

@@ -0,0 +1,24 @@
+# SOP - Runtime Automation
+
+## Objective
+
+Keep validation automatic on every relevant change.
+
+## Trigger policy
+
+- Validate on push to `develop` and `master`.
+- Validate on pull requests targeting `develop` or `master`.
+- Allow manual execution with workflow dispatch.
+
+## Validation circuit
+
+1. Install Node 18 and 20.
+2. Install runtime dependencies.
+3. Run `npm run release:check`.
+4. Fail fast on any smoke, skill or packaging regression.
+
+## Release hygiene
+
+- Do not publish if `release:check` fails.
+- Do not treat local runtime state as deployable proof.
+- Re-run smoke after structural or locale changes.

package/templates/opera/architecture/runtime-operations.md

@@ -0,0 +1,34 @@
+# SOP - Runtime Operations
+
+## Purpose
+
+Define the minimum operating procedure to keep a TrackOps + OPERA workspace healthy.
+
+## Inputs
+
+- `ops/project_control.json`
+- `ops/contract/operating-contract.json`
+- `ops/policy/autonomy.json`
+- `ops/bootstrap/quality-report.json`
+
+## Core checks
+
+1. Run `trackops status`.
+2. Run `trackops opera status`.
+3. Run `trackops env status`.
+4. Confirm `contract readiness` is not `hypothesis` for active delivery work.
+5. Confirm `legacyStatus` is `supported`.
+
+## Recovery path
+
+1. If bootstrap is incomplete, run `trackops opera handoff --print`.
+2. If discovery artifacts already exist, run `trackops opera bootstrap --resume`.
+3. If operational docs drift, run `trackops sync`.
+4. If managed artifacts drift, run `trackops opera upgrade --stable`.
+
+## Exit criteria
+
+- Runtime status is readable.
+- OPERA status is readable.
+- Contract and policy files exist.
+- No critical blocker remains undocumented.

package/templates/opera/en/agent.md

@@ -1,26 +1,27 @@
 # Project Agent: {{PROJECT_NAME}}
 
-## Identity
-You are the primary agent for **{{PROJECT_NAME}}**. You operate under the O.P.E.R.A. v3.0 protocol.
-
-## Source of Truth
-Your source of truth is `genesis.md`. Before making any architectural or implementation decision, read it first.
-For operational tracking and backlog state, use `project_control.json`.
-
-## Behavior
-- Follow the behavior rules defined in `genesis.md`.
-- Respect the autonomy matrix to determine which actions are allowed.
-- Manage tasks and states from `project_control.json`.
-- Do not edit `task_plan.md`, `progress.md`, or `findings.md` manually; regenerate them with `trackops sync`.
+## Identity
+You are the primary agent for **{{PROJECT_NAME}}**. You operate under the O.P.E.R.A. v3.0 protocol.
+
+## Source of Truth
+Your machine source of truth is `ops/contract/operating-contract.json`.
+Your compiled human view is `ops/genesis.md`.
+For operational tracking and backlog state, use `ops/project_control.json`.
+
+## Behavior
+- Follow the rules defined in `ops/contract/operating-contract.json` and reflected in `ops/genesis.md`.
+- Respect `ops/policy/autonomy.json` to determine which actions are allowed without approval.
+- Manage tasks and states from `ops/project_control.json`.
+- Do not edit `ops/task_plan.md`, `ops/progress.md`, or `ops/findings.md` manually; regenerate them with `trackops sync`.
 
 ## Available Skills
-Check `.agents/skills/_registry.md` to see installed skills.
+Check `ops/.agents/skills/_registry.md` to see installed skills.
 You can also discover new skills with `trackops skill catalog`.
 
-## Work Cycle
-1. Run `trackops status` at the beginning of each work block.
-2. Read `genesis.md` to understand the data and rules.
-3. Use `trackops next` to inspect the prioritized queue.
-4. Before implementing, mark the task with `trackops task start <task-id>`.
-5. Use the router in `.agent/hub/router.md` to choose the right skill.
-6. When you finish, move the task to `review`, `complete`, or `block`, then run `trackops sync`.
+## Work Cycle
+1. Run `trackops status` at the beginning of each work block.
+2. Read `ops/contract/operating-contract.json` and `ops/genesis.md` to understand the contract and its human view.
+3. Use `trackops next` to inspect the prioritized queue.
+4. Before implementing, mark the task with `trackops task start <task-id>`.
+5. Use the router in `ops/.agent/hub/router.md` to choose the right skill.
+6. When you finish, move the task to `review`, `complete`, or `block`, then run `trackops sync`.

package/templates/opera/en/architecture/dependency-graph.md

@@ -0,0 +1,24 @@
+# Dependency Graph
+
+```mermaid
+flowchart TD
+    A[Global runtime bootstrap] --> B[trackops init]
+    B --> C[trackops opera install]
+    C --> D{Routing}
+    D -->|direct_cli| E[Direct intake]
+    D -->|agent_handoff| F[agent-handoff.md/json]
+    F --> G[intake.json + spec-dossier.md]
+    E --> H[quality-report.json]
+    G --> H
+    H --> I[operating-contract.json]
+    I --> J[genesis.md]
+    I --> K[task_plan.md / progress.md / findings.md]
+    I --> L[dashboard + API state]
+    I --> M[env sync + policy enforcement]
+```
+
+## Notes
+
+- `ops/project_control.json` is the operational source of truth for backlog and session state.
+- `ops/contract/operating-contract.json` is the machine contract.
+- `ops/genesis.md` is a compiled human view.

package/templates/opera/en/architecture/runtime-automation.md

@@ -0,0 +1,24 @@
+# SOP - Runtime Automation
+
+## Objective
+
+Keep validation automatic on every relevant change.
+
+## Trigger policy
+
+- Validate on push to `develop` and `master`.
+- Validate on pull requests targeting `develop` or `master`.
+- Allow manual execution with workflow dispatch.
+
+## Validation circuit
+
+1. Install Node 18 and 20.
+2. Install runtime dependencies.
+3. Run `npm run release:check`.
+4. Fail fast on any smoke, skill or packaging regression.
+
+## Release hygiene
+
+- Do not publish if `release:check` fails.
+- Do not treat local runtime state as deployable proof.
+- Re-run smoke after structural or locale changes.

package/templates/opera/en/architecture/runtime-operations.md

@@ -0,0 +1,34 @@
+# SOP - Runtime Operations
+
+## Purpose
+
+Define the minimum operating procedure required to keep a TrackOps + OPERA workspace healthy.
+
+## Inputs
+
+- `ops/project_control.json`
+- `ops/contract/operating-contract.json`
+- `ops/policy/autonomy.json`
+- `ops/bootstrap/quality-report.json`
+
+## Core checks
+
+1. Run `trackops status`.
+2. Run `trackops opera status`.
+3. Run `trackops env status`.
+4. Confirm `contract readiness` is not `hypothesis` for active delivery work.
+5. Confirm `legacyStatus` is `supported`.
+
+## Recovery path
+
+1. If bootstrap is incomplete, run `trackops opera handoff --print`.
+2. If discovery artifacts already exist, run `trackops opera bootstrap --resume`.
+3. If operational docs drift, run `trackops sync`.
+4. If managed artifacts drift, run `trackops opera upgrade --stable`.
+
+## Exit criteria
+
+- Runtime status is readable.
+- OPERA status is readable.
+- Contract and policy files exist.
+- No critical blocker remains undocumented.

package/templates/opera/en/reviews/delivery-audit.md

@@ -0,0 +1,18 @@
+# Delivery Audit
+
+## Scope
+
+Review the final output shape against the active templates and compiled contract.
+
+## Checklist
+
+- `ops/genesis.md` matches the current contract.
+- `ops/task_plan.md`, `ops/progress.md` and `ops/findings.md` are synchronized.
+- Public copy matches runtime behavior.
+- API and dashboard reflect the same operational state.
+- Visual review completed when a UI change exists.
+
+## Result
+
+- Status: pending review
+- Notes: replace this section with project-specific evidence.

package/templates/opera/en/reviews/integration-audit.md

@@ -0,0 +1,18 @@
+# Integration Audit
+
+## Scope
+
+Review credentials, connectivity assumptions and external response shapes before expanding delivery.
+
+## Checklist
+
+- Required keys identified from the contract and environment contract.
+- Missing keys documented without exposing secret values.
+- External services listed in the contract.
+- Response shapes aligned with `ops/contract/operating-contract.json`.
+- Findings recorded in `ops/findings.md` when applicable.
+
+## Result
+
+- Status: pending review
+- Notes: replace this section with project-specific evidence.

package/templates/opera/en/router.md

@@ -15,15 +15,25 @@ This file defines the routing rules between the main agent and the available ski
 - **Skill**: `changelog-updater`
 - **Action**: Run the changelog update flow.
 
-### Context: Project initialization
-- **Trigger**: The user wants to create a new project.
-- **Skill**: `project-starter-skill` (global)
-- **Action**: Run the full initialization protocol.
-
-### Context: Operational tracking
-- **Trigger**: A work block is about to start, resume, or close.
-- **Skill**: No external skill.
-- **Action**: Run `trackops status`, take the next task with `trackops next`, and keep `project_control.json` as the operational source of truth.
+### Context: Agent-led project start
+- **Trigger**: The user has an idea, partial specification, or TrackOps has generated `ops/bootstrap/agent-handoff.md`.
+- **Skill**: `project-starter-skill`
+- **Action**: Turn the user context into `ops/bootstrap/intake.json`, `ops/bootstrap/spec-dossier.md`, and `ops/bootstrap/open-questions.md` when needed.
+
+### Context: Contract audit
+- **Trigger**: `ops/contract/operating-contract.json` or `ops/bootstrap/quality-report.json` exists and there are doubts about gaps or contradictions.
+- **Skill**: `opera-contract-auditor`
+- **Action**: Audit consistency, gaps, and false precision before execution continues.
+
+### Context: Operational risk
+- **Trigger**: The action affects persistent data, deployments, external side effects, or sensitive permissions.
+- **Skill**: `opera-policy-guard`
+- **Action**: Read `ops/policy/autonomy.json` and decide whether explicit approval is required.
+
+### Context: Operational tracking
+- **Trigger**: A work block is about to start, resume, or close.
+- **Skill**: No external skill.
+- **Action**: Run `trackops status`, take the next task with `trackops next`, use `ops/contract/operating-contract.json` as the machine contract, and keep `ops/project_control.json` as the backlog source of truth.
 
 ## Adding New Rules
 

package/templates/opera/reviews/delivery-audit.md

@@ -0,0 +1,18 @@
+# Delivery Audit
+
+## Scope
+
+Review the final output shape against the active templates and compiled contract.
+
+## Checklist
+
+- `ops/genesis.md` matches the current contract.
+- `ops/task_plan.md`, `ops/progress.md` and `ops/findings.md` are synchronized.
+- Public copy matches runtime behavior.
+- API and dashboard reflect the same operational state.
+- Visual review completed when a UI change exists.
+
+## Result
+
+- Status: pending review
+- Notes: replace this section with project-specific evidence.

package/templates/opera/reviews/integration-audit.md

@@ -0,0 +1,18 @@
+# Integration Audit
+
+## Scope
+
+Review credentials, connectivity assumptions and external response shapes before expanding delivery.
+
+## Checklist
+
+- Required keys identified from the contract and environment contract.
+- Missing keys documented without exposing secret values.
+- External services listed in the contract.
+- Response shapes aligned with `ops/contract/operating-contract.json`.
+- Findings recorded in `ops/findings.md` when applicable.
+
+## Result
+
+- Status: pending review
+- Notes: replace this section with project-specific evidence.