@awebai/oats 0.25.9 → 0.26.0

package/docs/execution-capsule.schema.json

@@ -1,108 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://oats.dev/schemas/execution-capsule-v1.json",
-  "title": "Scheduled execution capsule v1",
-  "description": "Immutable local authority for one admitted scheduled execution. executionId identifies this intent; a canonical oats.json.v1 digest of the remaining fields separately identifies content. Structural validation does not verify freshness, the retained resolution, approval, host readiness or provider state.",
-  "type": "object",
-  "additionalProperties": false,
-  "required": [
-    "schemaVersion",
-    "executionId",
-    "resolution",
-    "deployment",
-    "action",
-    "target",
-    "inputRefs",
-    "responsibleHuman"
-  ],
-  "properties": {
-    "schemaVersion": {
-      "const": 1
-    },
-    "executionId": {
-      "type": "string",
-      "minLength": 1,
-      "maxLength": 128,
-      "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,127}$"
-    },
-    "resolution": {
-      "$ref": "https://oats.dev/schemas/portable-v1.json#/$defs/ResolutionRef"
-    },
-    "deployment": {
-      "type": "string",
-      "minLength": 1
-    },
-    "action": {
-      "oneOf": [
-        {
-          "type": "object",
-          "additionalProperties": false,
-          "required": ["kind", "name"],
-          "properties": {
-            "kind": { "const": "command" },
-            "name": { "type": "string", "pattern": "^[^:\\s]+:[^:\\s]+$" }
-          }
-        },
-        {
-          "type": "object",
-          "additionalProperties": false,
-          "required": ["kind", "name"],
-          "properties": {
-            "kind": { "const": "wake" },
-            "name": { "const": "session" }
-          }
-        }
-      ]
-    },
-    "target": {
-      "oneOf": [
-        {
-          "type": "object",
-          "additionalProperties": false,
-          "required": ["cwd", "argv"],
-          "properties": {
-            "cwd": { "type": "string", "minLength": 1 },
-            "argv": {
-              "type": "array",
-              "minItems": 3,
-              "items": { "type": "string" }
-            }
-          }
-        },
-        {
-          "type": "object",
-          "additionalProperties": false,
-          "required": ["home", "message"],
-          "properties": {
-            "home": { "type": "string", "minLength": 1 },
-            "message": { "type": "string", "minLength": 1 }
-          }
-        }
-      ]
-    },
-    "inputRefs": {
-      "type": "object"
-    },
-    "responsibleHuman": {
-      "type": ["object", "null"]
-    }
-  },
-  "allOf": [
-    {
-      "if": {
-        "properties": { "action": { "type": "object", "properties": { "kind": { "const": "command" } } } }
-      },
-      "then": {
-        "properties": { "target": { "type": "object", "required": ["cwd", "argv"], "properties": { "cwd": {}, "argv": {} } } }
-      }
-    },
-    {
-      "if": {
-        "properties": { "action": { "type": "object", "properties": { "kind": { "const": "wake" } } } }
-      },
-      "then": {
-        "properties": { "target": { "type": "object", "required": ["home", "message"], "properties": { "home": {}, "message": {} } } }
-      }
-    }
-  ]
-}

package/docs/first-team-demo.md

@@ -1,92 +0,0 @@
-# First-team example: OATS working on OATS
-
-On 2026-09-05 we installed the published OATS artifacts and used Pi and
-Claude Code workers to fix issues found during a fresh review. The first
-team's work was release preparation in this repository.
-
-> **Historical v1 qualification.** The results below remain evidence for the
-> named versions, not the prepared v2 runtime. Current setup, external ownership
-> and independent delivery are in [the first-team guide](first-team.md).
-
-## The setup
-
-| Component | Qualified value |
-| --- | --- |
-| Kernel and Pi adapter | 0.22.0, installed from npm |
-| Workspace config | `oats.dev` 1.0.0 default, adopted at the common workspace root |
-| Knowledge | `oats.okf` 1.4.1 |
-| Messaging | `oats.aweb` 1.8.0, bound to our existing team |
-| Authoring | `oats.authoring` 1.0.0 |
-| Worker scope | The child OATS Git repository, selected explicitly |
-| Harvester runtime/model | Pi, `openai-codex/gpt-5.5`, configured for this machine |
-
-Package acquisition used the published kernel's catalog and exact locks.
-The executable OKF and aweb capabilities were explicitly trusted.
-`oats doctor` passed. A separate published-authoring probe confirmed that
-`integration-authoring`, `skill-craft`, and `soul-craft` materialized for an
-authoring soul.
-
-## Two useful tasks
-
-The **Pi documentation worker**, `docs-expert-readme-claims`, corrected a
-claim that all captured conversations were signed. Native transcript turns
-have content hashes; signed aweb messages preserve their original
-signatures. Its code-review handoff led to the
-[documentation correction](https://github.com/awebai/oats/commit/ef4a1a6599da88e213b2a6a8f3918099aa5ba984).
-
-The **Claude Code worker**, `cli-dev-lock-fix`, fixed a stream-lock race.
-A late contender could classify a live holder's lock as stale and enter the
-same critical section. The fix uses holder liveness and an ownership token;
-review also caught an acquisition loop that could retry filesystem errors
-forever. See the [initial fix](https://github.com/awebai/oats/commit/1036381)
-and [review correction](https://github.com/awebai/oats/commit/81735f6e936d1b6aa0a3ad62d12953d494851cc8).
-
-Both workers used isolated worktrees, committed changes, and reported
-through aw. Review happened before integration. Claude needed its initial
-folder-trust and development-channels confirmations; Pi started directly.
-
-## What carried forward
-
-Each worker invoked OKF harvest. Its temporary harvester promoted a lesson
-into the source soul and committed it on the worker's branch:
-
-- [Content-addressed turn IDs do not authenticate native capture](https://github.com/awebai/oats/commit/91993a0b85db132c59c32d43ee2c90ec5569bd50).
-- [Lock ownership and the limits of comparing timeout thresholds](https://github.com/awebai/oats/commit/120e3474b93efc0d37f94c426327f802e27893ea).
-
-After the documentation promotion landed, the predecessor retired locally:
-its worktree, branch, and home were removed. Its aweb alias remained on the
-server despite the hook reporting success. A new Pi instance of the same
-soul with a different name, `docs-expert-capture-contract-check`, started a real
-follow-up task checking the capture contract documentation.
-
-Its first report named the promoted file:
-`soul/knowledge/lessons/content-addressed-turn-ids-not-authentication.md`.
-The worker said the lesson reinforced the distinction between unsigned
-native turns and preserved source signatures, and explicitly said it did
-not change what it was already about to do.
-
-That verifies useful work, reviewed promotion, local retirement, and a
-successor reading the updated soul. Remote identity retirement remains
-incomplete. The example does not establish a measured productivity
-improvement.
-
-## What the run exposed
-
-The run found first-use problems that unit tests alone had not resolved:
-
-- A fresh scope needed `mkdir -p agents` before `oats create`; the fix is in
-  the 0.22.1 changes.
-- The default harvester model assumed a provider absent on this machine.
-  The workspace now selects an authenticated model explicitly.
-- All four initial worker and harvester retirements reported successful
-  identity deletion but left their aweb aliases on the server. Local
-  cleanup completed; remote cleanup requires a team administrator, and
-  names cannot be reused until it succeeds. Temporary harvesters are now
-  excluded from messaging to avoid adding aliases while this is fixed.
-- A combined workspace roster did not make the workspace a spawn scope for
-  every child repository. Commands select the owning repository explicitly.
-
-The [first-team guide](first-team.md) now describes the prepared v2 setup;
-these historical v1 outcomes are not v2 acceptance evidence. The
-package owners are responsible for improving their defaults; the kernel
-continues to resolve capabilities through the same replaceable contracts.

package/docs/knowledge-migration.md

@@ -1,147 +0,0 @@
-# Migrating OKF v1 knowledge to v2
-
-> **Prepared, not a live migration.** These instructions target oats.okf 2.0.0
-> with OATS >=0.23.0 and the prepared framework v0.23.1 integration. Confirm the
-> final standalone source tag and dependencies are published before following
-> the acquisition path. See [release gates](release-notes/v0.23.1.md).
-
-This is **not** `oats migrate`: kernel lock/package migration and
-[OAS name migration](migration-from-oas.md) do not relocate knowledge, establish
-v2 ownership or preserve source cursors. Nor does upgrading npm activate a new
-knowledge layer. V2 uses external accepted bases and independent workers, not
-`soul/knowledge/`, attached harvest commits or source-home watermarks.
-
-## 1. Inventory and preserve before changing activation
-
-- Record each scope's package lock, active knowledge binding, effective settings,
-  soul instructions/skills and current knowledge bytes. Do not hand-edit locks.
-- Inventory live source homes, state/log/notes, v1 current/prepared watermark
-  files, active harvesters, unpublished commits and open PRs. Resolve or preserve
-  in-flight work deliberately; do not run old and new writers concurrently.
-- Back up source material outside disposable homes/worktrees. Keep v1 artifacts
-  available until accepted delivery, owner cutover and fresh-reader verification
-  have succeeded. A successful scaffold or command exit is not learned expertise.
-- Plan the deployment interruption and test the migration on isolated copies.
-  The required v2 spawn hook refuses a legacy `soul/knowledge/`; it never silently
-  substitutes an empty bundle.
-
-After publication, bump `packages.oats.okf` in the workspace file and run
-`oats sync`: the new version resolves to a commit and its executables are
-approved once. An existing lock never advances by itself. Package content is
-read from the catalog **Git** repository, never from an npm mirror (npm drops
-the source worker's canonical `CLAUDE.md` symlink).
-
-## 2. Bind and provision external destinations
-
-Follow [bindings and owner descriptors](knowledge.md#acquire-bind-and-provision-explicitly).
-Choose stable base IDs, stable owner IDs, nonoverlapping node paths and durable
-`stateDir`. `owns` routes responsibility; `reads` chooses starting context, not
-permissions. Confirm aliases and owners explicitly, rather than deriving them
-from an instance branch or name.
-
-Configure the absolute `bindings-file` **and** `state-dir` for each source soul
-— the oats.okf 2.1.x binding requires both as normalized absolute host paths
-(`setting state-dir is required (absolute host path)` is a refusal, not a
-default). Remove obsolete v1 settings such as `record-window-turns` and
-`record-window-bytes`; v2 accepts exactly `bindings-file`, `state-dir`,
-`harvest-runtime` and `harvest-model`. Under the 0.25 workspace model these live
-in `oats-local.yaml` `settings.oats.okf` ([configuration.md](configuration.md));
-a rebuilt deployment gets a **fresh** `state-dir`
-([rebuild-to-v2.md §7b](rebuild-to-v2.md#7b-okf-2-start-a-fresh-state-dir-do-not-re-point-the-old-one)).
-Provision **empty owned nodes** using `oats okf init`. Accept Git initialization
-through a reviewed PR before migration delivery; directory provisioning requires
-explicit confirmation and a genuinely non-Git location.
-
-## 3. Stage and deliver each legacy bundle
-
-From the deployment directory (the one holding `oats-local.yaml`) in an operator
-shell without inherited instance identity, selecting the source soul with
-`--soul` — the kernel resolves the command exactly as `oats spawn --soul <x>`
-would ([knowledge.md](knowledge.md#inspection-and-operator-commands)):
-
-```bash
-oats okf migrate --legacy /absolute/soul/knowledge --base project --node expert --output /absolute/empty-migration-stage --soul domain-expert --json
-# Use the exact migration.json path returned above:
-oats okf migrate --deliver /absolute/state/migrations/UUID/migration.json --soul domain-expert --json
-```
-
-Staging preserves the full original in migration custody, rewrites bundle-root
-Markdown links into the external node namespace and validates the whole base.
-The output must be disjoint from **every** configured accepted base and directory
-coordination artifact. The destination node must be empty; migration refuses
-ambiguous automatic merges.
-
-Delivery follows the actual provider protocol:
-
-- **Git:** a real PR, never a direct push to the accepted branch. Review and merge
-  it, then repeat `migrate --deliver` to confirm merge-visible acceptance.
-- **Directory:** recoverable publication with a cooperative lock, baseline check,
-  journal and validated acceptance receipt. Resolve any journal before proceeding.
-
-A staged bundle, delivered PR or proposed owner mapping is not cutover.
-
-## 4. Deliberate owner cutover
-
-```bash
-oats okf migrate --cutover /absolute/state/migrations/UUID/migration.json --soul-dir /absolute/soul --soul domain-expert --json
-```
-
-Cutover requires accepted delivery, unchanged legacy bytes and current bindings
-still pointing to the frozen delivered base. It verifies accepted readiness,
-node owner/path and delivered content, then renames the old bundle into durable
-custody and updates `soul/okf.json`. It changes no skills and leaves no permanent
-knowledge symlink in the soul. Cross-device rename fails safely: arrange an
-explicit operator cutover rather than deleting originals to force it. An
-incomplete cutover marker blocks new source registration until that recorded
-cutover is retried.
-
-Explicitly review old soul instruction references to `soul/knowledge/`, direct
-promotion and after-commit harvest. Point readers to the capability-provided
-accepted views; ordinary agents capture but never edit accepted knowledge. This
-instruction review is not an automatic rewrite performed by migration.
-
-## 5. Preserve and re-register existing sources
-
-For every surviving v1 source home:
-
-```bash
-oats okf migrate --source-home /absolute/legacy-instance-home --soul domain-expert --json
-```
-
-This copies allowlisted state/log/notes and old cursors into migration custody,
-**deleting nothing**. Old watermarks are retained as evidence, not trusted as v2
-processing proof. After soul migration, explicit `harvest` from that clean deployment context
-re-registers a source,
-captures visible notes and record, and idempotently verifies its per-source job:
-
-```bash
-oats okf harvest --home /absolute/legacy-instance-home --no-launch --soul domain-expert --json
-```
-
-`--no-launch` is a scaffold-only worker request, not a read-only operation: it
-captures and writes durable state/schedule definitions, but starts no model and
-installs no timer. Existing homes retain their composed capability snapshot;
-plan refresh/replacement or dispatch through the deliberately selected v2
-configuration context. Do not assume updating a package rewrites a running
-home's curriculum, trust or native session. Preserve evidence before retiring
-or replacing any old home. Replay may legitimately produce merge/drop judgments.
-
-## 6. Verify before retiring old custody
-
-Inspect the durable source descriptor and its receipts. Confirm frozen owners,
-accepted view paths, captured notes **and full record windows**, processing and
-provider acceptance separately. Verify live inspection only shows the matching
-source's state/log/notes. After safe source retirement, `--source` inspection and
-read/refresh must still work from durable context; new views belong in state,
-not the deleted home or invoking repository.
-
-Enable a host timer only with explicit operator consent after reviewing source
-jobs and available worker runtimes. Existing no-launch sources cannot cause
-scheduled model launches; do not turn an isolated rehearsal into a deployment.
-A source whose final capture is incomplete must retain its home for retry.
-
-Finally start a fresh, deliberately selected runtime instance and verify it can
-find **and use** the accepted lesson without the original source. A no-launch
-reader verifies layout and links, not model learning. Only then consider old
-custody cleanup under an explicit retention decision; v2 does not automatically
-remove preserved evidence, old views, migration archives or unresolved runs.

package/docs/migration-from-oas.md

@@ -1,103 +0,0 @@
-# Migrating from OAS to OATS
-
-> **0.25 status — this is a 0.22–0.24 procedure.** `oats migrate` and
-> `oats trust` are **removed verbs** in the 0.25 kernel (`E_UNKNOWN_COMMAND`
-> naming the replacement), and 0.25 reads none of the files this page
-> converts to (`oats-config.yaml`, `oats-lock.json` v2, the `installed/` tier).
-> An OAS deployment reaches 0.25 in two steps: run this page's commands with a
-> **0.24.x** kernel (`npm install -g @awebai/oats@0.24`), then rebuild for the
-> workspace model with [rebuild-to-v2.md](rebuild-to-v2.md) — which is a rewrite
-> of three shared files, not a conversion, so an operator comfortable with the
-> v2 declarations may skip straight to it and let the old files go.
-
-OATS is the successor to OAS. **OATS 0.22.0 was published on 2026-09-03**:
-the kernel, Pi adapter, and Desktop assets are available. The published
-kernel acquired the official OKF, aweb, authoring, and development packages
-from its catalog during the 2026-09-05 qualification. You no longer need a
-framework checkout to migrate.
-
-Use the migration command rather than renaming files by hand. The OATS
-kernel does not read `oas-*` configuration names or `oas.*` capability IDs.
-An unchanged agent-directory layout can make an old scope look familiar
-while its knowledge and messaging configuration remains unmigrated.
-
-> **Separate knowledge cutover:** OAS/package name migration does not migrate
-> soul knowledge, source memory or v1 watermarks to OKF v2. If the selected
-> catalog update acquires OKF 2.0.0, plan [knowledge preservation and cutover](knowledge-migration.md)
-> before activation/spawn. The v2 integration is [prepared](release-notes/v0.23.1.md),
-> not a claim that those dependencies or any deployment have already changed.
-
-## Upgrade one scope (0.24.x kernel)
-
-Finish or preserve active work before changing a daily-use deployment.
-Install OATS **0.24.x** alongside the old CLI (the 0.25 line has no `oats
-migrate`), then inspect the plan for the exact scope you intend to convert:
-
-```bash
-npm install -g @awebai/oats@0.24
-pi install npm:@awebai/oats-pi@0.24
-oats migrate --from-oas --dry-run --dir /path/to/scope
-```
-
-Read any held or unmapped package rows before applying. A dry run reports
-what can be converted; it is not a guarantee that every historical package
-version has a supported replacement. When the plan is correct:
-
-```bash
-oats migrate --from-oas --dir /path/to/scope
-oats doctor /path/to/scope
-```
-
-Run the exact `oats trust <capability> --dir <scope>` commands printed by
-migration for the executable capabilities you approve (0.24: per-artifact
-trust; under 0.25 approval is per package version through `oats sync`). Trust
-does not transfer automatically. Verify the team ID and messaging membership
-with `oats aweb setup --dir /path/to/scope`, then exercise a real task,
-harvest, and retirement as described in [Run your first team](first-team.md).
-
-For a multi-repository deployment, start with one scope. The explicit
-`--recursive --dir /path/to/workspace` form converts every discovered OAS
-scope, with a separate transaction for each; it is not one transaction for
-the whole workspace.
-
-If you use Desktop, install [OATS Desktop](desktop.md) too. The old OAS
-Desktop discovers the old package name and cannot operate the new CLI.
-OATS Desktop 0.22.0 accepts kernel versions `>=0.22.0 <0.23.0`.
-
-## What the command converts
-
-One transaction covers two phases within a scope:
-
-1. Rename `oas-config.yaml` and `oas-lock.json` to their `oats-` names;
-   convert the `oas:` defaults key and catalog-mapped capability IDs;
-   rename installed `oas.json` manifests and soul scaffold-owner files.
-2. Convert the old lock to official package lockfile version 2, acquiring
-   the replacement artifacts and removing superseded installed directories.
-
-The catalog includes aliases for the seven OAS 0.20 capability IDs, mapping
-`oas.*` names to the corresponding `oats.*` packages and capabilities.
-Aliases guide migration; they are not runtime compatibility shims.
-Comments and unrelated configuration text are preserved, including old
-names in comments. Those comments can be updated separately.
-
-A failure in either phase restores that scope's original OAS bytes. A
-second successful run finds nothing to convert. `oats doctor` and migration
-commands identify visible OAS-named scopes and give a remedy rather than
-silently declaring an unmigrated deployment ready.
-
-## Compatibility and remaining transition work
-
-The migration fixtures were built from an OAS 0.20.x deployment. OAS
-0.21.x uses the same file names and configuration keys, but may lock package
-versions outside the OATS catalog's mapped line. Inspect the dry run before
-converting those scopes; do not replace an unmapped version by guessing.
-
-The old `@oas-framework/*` packages have not been deprecated as part of
-this rollout. Their update checks therefore do not announce the OATS
-rename; deprecation belongs to their maintainer. An existing OAS deployment
-can keep running until its own migration plan is ready. This is no longer a
-requirement to wait for OATS publication.
-
-See the [0.22.0 release notes](release-notes/v0.22.0.md) for the rename,
-package versions, and compatibility changes, and the
-[first-team qualification](first-team-demo.md) for historical v1 operating evidence.

package/docs/oats-config.schema.json

@@ -1,172 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://oats.dev/schemas/oats-config.schema.json",
-  "title": "OATS scoped configuration",
-  "$defs": {
-    "settings": { "type": "object", "additionalProperties": true },
-    "binding": {
-      "oneOf": [
-        { "type": "boolean" },
-        {
-          "type": "object",
-          "properties": {
-            "enabled": { "type": "boolean" },
-            "settings": { "$ref": "#/$defs/settings" }
-          },
-          "additionalProperties": false
-        }
-      ]
-    },
-    "injection-override": { "type": "string", "description": "Override an instruction injection: a config-relative path, none, or default. Convention: .agents/injections/…" },
-    "capabilityTargets": {
-      "type": "object",
-      "properties": {
-        "from": { "type": "string", "description": "Enforced provenance: installed | owned | path:<dir>." },
-        "global": { "$ref": "#/$defs/binding" },
-        "agent-types": {
-          "oneOf": [
-            { "type": "array", "items": { "type": "string" }, "uniqueItems": true },
-            { "type": "object", "additionalProperties": { "$ref": "#/$defs/binding" } }
-          ]
-        },
-        "souls": { "type": "object", "additionalProperties": { "$ref": "#/$defs/binding" } },
-        "settings": { "$ref": "#/$defs/settings" },
-        "injection-override": { "$ref": "#/$defs/injection-override" }
-      }
-    },
-    "layerEntry": {
-      "oneOf": [
-        { "const": "none" },
-        {
-          "allOf": [{ "$ref": "#/$defs/capabilityTargets" }],
-          "type": "object",
-          "required": ["capability"],
-          "properties": {
-            "capability": { "type": "string" },
-            "from": true, "global": true, "agent-types": true, "souls": true, "settings": true, "injection-override": true
-          },
-          "additionalProperties": false
-        }
-      ]
-    },
-    "additiveEntry": {
-      "allOf": [{ "$ref": "#/$defs/capabilityTargets" }],
-      "type": "object",
-      "properties": {
-        "from": true, "global": true, "agent-types": true, "souls": true, "settings": true, "injection-override": true
-      },
-      "additionalProperties": false
-    },
-    "workMode": {
-      "oneOf": [
-        { "type": "null" },
-        {
-          "type": "object",
-          "properties": {
-            "setup": { "type": "string", "description": "Env-bootstrap command run inside each new worktree after creation (path relative to this config's directory). Only worktree mode runs setup." },
-            "retirement-disposable": { "type": "array", "items": { "type": "string" }, "description": "Relative disposable roots for worktree retirement. Directory mode has no disposable exemptions." }
-          },
-          "additionalProperties": false
-        }
-      ]
-    }
-  },
-  "type": "object",
-  "properties": {
-    "yolo": { "type": "boolean", "description": "Skip Codex/Claude permission prompts. Closest scope wins; soul and launch overrides take precedence." },
-    "name": { "type": "string" },
-    "team": {
-      "type": "object",
-      "description": "The deployment/team boundary. Closest scope declaring team: wins; used for identity, cross-repo agent discovery (oats status --team), and messaging providers.",
-      "properties": {
-        "name": { "type": "string" },
-        "id": { "type": "string", "description": "Explicit provider team id (e.g. aweb <name>:<namespace>)." }
-      },
-      "required": ["name"],
-      "additionalProperties": false
-    },
-    "launch-configs": {
-      "type": "object",
-      "description": "Named ways to start a harness, independent of any soul. The closest scope declaring a name provides the whole entry (no merging between scopes). Selected by name at spawn or session start/restart; explicit flags override its fields.",
-      "propertyNames": { "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$" },
-      "additionalProperties": {
-        "type": "object",
-        "additionalProperties": false,
-        "required": ["runtime"],
-        "properties": {
-          "runtime": { "type": "string", "enum": ["pi", "claude", "codex"], "description": "The harness family this configuration starts; it decides the kernel's own baseline arguments (skills, instructions, task) and how model/yolo are expressed." },
-          "executable": { "type": "string", "minLength": 1, "description": "The program to run instead of the runtime's default binary: a bare name is looked up on PATH on the execution host; a path containing a slash is resolved against the declaring scope's directory when relative. Checked to exist and be executable before any start; never executed just to probe it." },
-          "args": { "type": "array", "items": { "type": "string" }, "description": "Extra arguments, each passed literally (no shell interpretation): native configuration files or profiles go here as ordinary arguments." },
-          "env": {
-            "type": "object",
-            "propertyNames": { "pattern": "^[A-Za-z_][A-Za-z0-9_]*$" },
-            "additionalProperties": {
-              "oneOf": [
-                { "type": "string" },
-                { "type": "object", "additionalProperties": false, "required": ["fromEnv"], "properties": { "fromEnv": { "type": "string", "pattern": "^[A-Za-z_][A-Za-z0-9_]*$" } } }
-              ]
-            },
-            "description": "Environment for the harness. A string is a literal (non-secret by contract; still redacted in every answer). {fromEnv: NAME} is resolved from the execution host's environment at start time; the reference, never the value, is recorded. A missing reference refuses the start before anything stops."
-          },
-          "model": { "type": "string", "minLength": 1, "description": "Model for this configuration's runtime; overrides the soul default when this configuration is selected." },
-          "yolo": { "type": "boolean", "description": "Permission bypass for this configuration; overrides scope and soul defaults when selected." }
-        }
-      }
-    },
-    "agent-types": {
-      "type": "object",
-      "description": "Agent families declared by name; membership is `type: <name>` in each soul.yaml.",
-      "additionalProperties": {
-        "oneOf": [
-          { "type": "null" },
-          {
-            "type": "object",
-            "properties": { "description": { "type": "string" } },
-            "additionalProperties": false
-          }
-        ]
-      }
-    },
-    "capabilities": {
-      "type": "object",
-      "properties": {
-        "layers": {
-          "type": "object",
-          "description": "The three exclusive fundamental slots: a capability entry or an explicit none.",
-          "properties": {
-            "knowledge": { "$ref": "#/$defs/layerEntry" },
-            "messaging": { "$ref": "#/$defs/layerEntry" },
-            "tasks": { "$ref": "#/$defs/layerEntry" }
-          },
-          "additionalProperties": false
-        },
-        "additive": {
-          "type": "object",
-          "propertyNames": { "pattern": "^(?:@?[a-z0-9][a-z0-9._-]*[./])[a-z0-9][a-z0-9._/-]*$" },
-          "additionalProperties": { "$ref": "#/$defs/additiveEntry" }
-        }
-      },
-      "additionalProperties": false
-    },
-    "skill-overrides": { "type": "object", "additionalProperties": { "type": "string" } },
-    "templates": { "type": "object", "additionalProperties": { "type": "string" }, "description": "Named oats init templates: local config paths or git URLs whose main branch carries an oats-config.yaml." },
-    "agents-md-injection": { "oneOf": [{ "type": "string" }, { "type": "object", "additionalProperties": { "type": "string" } }], "description": "Extra unconditional instruction blocks (adds content; does not override packaged defaults)." },
-    "oats": {
-      "type": "object",
-      "properties": { "injection-override": { "$ref": "#/$defs/injection-override" } },
-      "additionalProperties": false
-    },
-    "work-modes": {
-      "type": "object",
-      "properties": {
-        "worktree": { "$ref": "#/$defs/workMode" },
-        "checkout": { "$ref": "#/$defs/workMode" },
-        "attached": { "$ref": "#/$defs/workMode" },
-        "workspace": { "$ref": "#/$defs/workMode" },
-        "directory": { "$ref": "#/$defs/workMode" }
-      },
-      "additionalProperties": false
-    }
-  },
-  "additionalProperties": false
-}

package/docs/oats-lock-v3.schema.json

@@ -1,7 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://oats.dev/schemas/selection-lock-v3.json",
-  "title": "Source-request selection lock v3",
-  "description": "New private wire boundary; public consumer activation requires the explicit preparation/migration integration. See portable-v1.json for semantic verification requirements.",
-  "$ref": "https://oats.dev/schemas/portable-v1.json#/$defs/Lock3"
-}