owlrunkit 0.19.2 → 0.21.0

package/CHANGELOG.md

@@ -1,5 +1,68 @@
 # Changelog
 
+## 0.21.0
+
+- Adds ExternalGateV1 as typed, source-hash-bound Project Driver truth. A due
+  pending, blocked, or deferred Gate becomes the dominant gap for its delivery
+  stage; superseding observations are append-only and raw capture cannot bypass
+  typed intake.
+- Adds DeliveryLifecycleV1 and Project Status V4 so source acceptance,
+  integration, materialization, deployment, live readback, and product acceptance are distinct
+  evidence facts. Work-ledger completion never auto-promotes a later stage.
+- Adds Team Delivery Status V2 with explicit known-but-unmodeled candidate
+  lanes while retaining one Project Driver graph and read-only, no-dispatch
+  Team coordination.
+- Adds optional WorkItem Quick-evidence policy and
+  `project checkpoint --from-quick-receipt`; ordinary WorkItems remain
+  lightweight and no assurance mode changes automatically.
+- Adds read-only `fleet skill-plan` for affected-project inventory, active
+  execution/lease blockers, and copyable dry-run, install, and rollback
+  commands. It grants no shared-Skill, project, Git, or release authority.
+- Adds a canonical candidate ledger with fixed Git object width, C-locale path
+  ordering, complete path/mode/size/content bindings, and a transport-only raw
+  binary diff. Object-store growth no longer changes the candidate identity.
+- Adds controller-owned `quick-verify --foreign-workspace` and Quick Receipt
+  V4. The target is copied into a disposable consumer; receipts remain under
+  the controller and bind target candidate, filesystem, dependency, command,
+  and before/after observed zero-write evidence without initializing RunKit in
+  the frozen target.
+- Doctor now reports the package-bound and discovered process-wide Skill versions and
+  absolute paths, labels drift as a visible non-blocking warning, and keeps the
+  actually loaded Skill version honest as `unknown`.
+- Replaces the temporal, candidate-only registry policy with a lifecycle-stable
+  registry-gated release artifact policy. The packed README, Skill, policy, and
+  SBOM no longer claim that the package is unpublished or that an older version
+  is still current; adoption still requires independent exact-registry evidence.
+- Treats formatting-only profile reconciliation as an apply-time no-op. The
+  result remains explicit through `normalizationOnly: true`, but owner JSON
+  bytes stay unchanged and no migration receipt or tracked diff is created.
+- Makes a version-mismatched bootstrap return the exact successor install and
+  dry-run commands instead of only reporting the older CLI's own exact spec.
+- Adds `inspect --json --compact`, a bounded projection of project truth,
+  progress, dominant gap, owner, next action, warning groups, execution counts,
+  and the unchanged authority boundary without full execution history.
+- Adds Team Delivery Status V2. Missing receipt warnings now carry severity,
+  blocking and gate semantics, an actionable recommendation, and deterministic
+  aggregation without retroactively requiring Formal evidence.
+- Shows project CLI/Core and process-level shared Skill versions in doctor.
+  Skill drift is explicitly non-blocking and includes a fleet activation
+  blocker when an active execution or lease prevents safe refresh.
+
+## 0.20.0
+
+- Adds read-only `team recommend` and `team status` projections over the
+  existing Project Driver. Ordinary single-owner work remains off; real
+  multi-lane coordination, owned-path conflicts, independent verification, and
+  owner transitions are explained without persisting a second task graph.
+- Publishes strict TeamTaskPacket V2, TeamAcceptancePacket V2, and
+  CandidateTransferPacket V1 contracts plus `team packet validate`. Project
+  bindings, exact WorkItem ownership, model-family independence, candidate
+  identity, handoff ACK, false-authority fields, and duplicate JSON keys fail
+  closed.
+- Keeps Team Delivery orthogonal to continuity and assurance. This phase does
+  not dispatch Agents, rank providers, federate vendor CLIs, grant authority,
+  or turn multi-Agent coordination into Formal Delivery.
+
 ## 0.19.2
 
 - Adds read-only `formal preflight` and reuses it before an envelope-backed

package/README.md

@@ -67,6 +67,42 @@ Independent verification requires a different assigned Agent. Append-only
 scope revision can widen or narrow a WorkItem after diagnosis without rewriting
 history, and missing Quick/Formal receipt references remain visible warnings.
 
+RunKit 0.20 Phase 1 adds Team Delivery as a read-only coordination dimension
+over the existing Project Driver. `team recommend` exits for ordinary
+single-owner work, recommends Team only for real coordination facts, exposes
+owned-path conflicts and independent-acceptance gaps, and never dispatches an
+Agent. `team status` projects the existing project graph without storing a
+second graph. Three strict portable contracts—TeamTaskPacket V2,
+TeamAcceptancePacket V2, and CandidateTransferPacket V1—can be validated on a
+machine that does not have the local `manage-agent-team` Skill. This phase
+does not add automatic or assisted dispatch and does not change Quick or Formal
+assurance.
+
+RunKit 0.21.0 Phase 2 keeps Team Delivery read-only while making delivery truth
+explicit. Typed external Gates may block the relevant stage without parsing a
+domain product's documents. Source acceptance, integration, materialization, deployment, live
+readback, and product acceptance are separate evidence-bound lifecycle facts.
+Project Status V4 and Team Delivery Status V2 expose that progression and an
+explicit inventory of known-but-unmodeled candidates. An optional WorkItem
+policy can require a currently attested Quick receipt, and `fleet skill-plan`
+shows affected projects, active blockers, and copyable install/rollback commands
+without mutating the shared Skill. No command dispatches an Agent or raises
+assurance automatically.
+
+The same phase adds a fixed-width canonical candidate ledger and
+controller-owned Foreign Quick. A controller running 0.21 may verify a
+disjoint frozen Git worktree without installing RunKit, changing package/lock
+files, or creating `.owlcoda/runkit` in that target. Doctor also exposes the
+package-bound and discovered process-wide Skill identities; it cannot prove which
+instructions an already-running Agent process loaded, so that field remains
+`unknown`.
+
+This release also folds in the upgrade-usability patch: cross-version bootstrap
+failures return copyable install and retry commands; `inspect --json --compact`
+omits historical payloads; Team receipt warnings are non-blocking, actionable,
+and grouped; doctor reports project CLI/Core separately from a process-level
+shared Skill; and formatting-only profile reconciliation is a zero-write apply.
+
 The 0.18 Project Driver is a bounded surface for new projects and controlled
 dogfood. Its product name does not claim to be a general long-running,
 multi-phase, or enterprise control plane. Version 0.18 adds one bounded
@@ -80,13 +116,13 @@ separate authority boundaries.
 
 ## Install
 
-`owlrunkit@0.19.2` is an unpublished release candidate. Until registry
-publication is independently verified, the current installable release is
-`owlrunkit@0.19.1`; a locally packed 0.19.2 tarball is for candidate testing
-only and is not adoption provenance.
+This package is the lifecycle-stable `owlrunkit@0.21.0` release artifact.
+Registry adoption remains fail-closed until its exact official npm version,
+shasum, integrity, and tarball URL are independently verified. Local tarballs
+remain candidate-test inputs and are never adoption provenance.
 
 ```bash
-npm install --save-exact owlrunkit@0.19.1
+npm install --save-exact owlrunkit@0.21.0
 ```
 
 Use `npx --no-install owlrunkit` for project commands. The package bootstrap
@@ -102,11 +138,12 @@ the project Config must independently bind the same Core.
 ```bash
 npx --no-install owlrunkit --version
 npx --no-install owlrunkit bootstrap --workspace /absolute/path/to/project \
-  --exact owlrunkit@0.19.1 --dry-run
+  --exact owlrunkit@0.21.0 --dry-run
 npx --no-install owlrunkit bootstrap --workspace /absolute/path/to/project \
-  --exact owlrunkit@0.19.1 --apply
+  --exact owlrunkit@0.21.0 --apply
 npx --no-install owlrunkit init --workspace /absolute/path/to/project
 npx --no-install owlrunkit doctor --workspace /absolute/path/to/project
+npx --no-install owlrunkit inspect --workspace /absolute/path/to/project --json --compact
 npx --no-install owlrunkit mode recommend --workspace /absolute/path/to/project
 npx --no-install owlrunkit mode status --workspace /absolute/path/to/project
 ```
@@ -118,11 +155,45 @@ back doctor. Dry-run is zero-write; failed apply restores the governed preimage
 and keeps a failure receipt. It reports shared Skill drift but never silently
 updates a user or fleet Skill.
 
+When an older CLI receives a different exact successor spec, bootstrap returns
+two bounded repair commands: install that exact project dependency, then rerun
+the successor's project-local bootstrap dry-run. Doctor keeps shared Skill
+drift non-blocking and reports why fleet-safe activation must wait when an
+active execution or lease is present.
+
 `mode recommend` is read-only and defaults to human output; add `--json` for a
 machine contract. The five user modes are presets over `continuity`
 (`none | project_driver`) and `assurance` (`none | quick | formal`). They never
 grant Git, release, deployment, production, or business authority.
 
+## Team Delivery: Recommend coordination without dispatch
+
+Team Delivery is separate from continuity and assurance. It reads the current
+Project Driver, recommends whether Team coordination is useful, and validates
+self-contained packets without importing model-specific routing policy:
+
+```bash
+npx --no-install owlrunkit team recommend --workspace .
+npx --no-install owlrunkit team status --workspace .
+npx --no-install owlrunkit team packet validate --workspace . \
+  --packet ./team-task-packet.json
+```
+
+No initialized project, no actionable work, and one ordinary ready WorkItem
+remain `off`. Two disjoint actionable WorkItems may be parallel-eligible.
+Overlapping owned paths recommend Team but block parallel writing and point to
+append-only scope revision or serialization. Verification, handoff, rework,
+candidate transfer, or multiple active owners keep coordination visible without
+raising assurance. Every result keeps Agent dispatch and all external authority
+false. Phase 1 contains no launcher, scheduler, model ranking, or vendor CLI
+federation.
+
+`team status` emits Team Delivery Status V2. Each
+`no_bound_verification_receipt` entry includes `severity`, `blocking`,
+`requiredAtGate`, and `recommendedAction`, plus an aggregated warning summary.
+Completed historical WorkItems whose evidence policy did not require a reusable
+receipt are not retroactively told to add Formal evidence.
+
 ## Project Driver: Coordinate a multi-Agent project
 
 RunKit 0.18 keeps the project alive independently of any one Agent or chat.
@@ -338,7 +409,9 @@ and launchers that do not resolve to exact local files. Detection directly
 supports lock-bound npm plus exact project-installed pnpm, Yarn, and Bun
 launchers. A PATH-only package manager remains review-required. A dry-run that
 only canonicalizes JSON formatting reports `normalizationOnly: true` instead of
-showing unexplained hash drift with an empty update list.
+showing unexplained hash drift with an empty update list. Applying that plan is
+a zero-write `profiles_already_current` result: owner bytes remain unchanged and
+no migration receipt or tracked formatting diff is created.
 
 The dry-run is the V2 detection contract. It reports `profiles_insufficient`
 instead of `profiles_detected` when Git-visible source paths are uncovered or
@@ -394,6 +467,9 @@ npx --no-install owlrunkit quick-verify --workspace . --stdin-file ./remote-chec
   -- ssh test-host /bin/sh
 npx --no-install owlrunkit quick-verify --workspace . --isolate \
   --dependency-root /absolute/dependency-consumer -- npm test
+npx --no-install owlrunkit quick-verify --workspace /absolute/controller \
+  --foreign-workspace /absolute/frozen-target \
+  --dependency-root /absolute/dependency-consumer -- npm test
 npx --no-install owlrunkit quick-verify --workspace . \
   --bind-ignored .generated/audit.json -- node ./verify-generated.mjs
 npx --no-install owlrunkit quick-reuse --workspace . \
@@ -428,6 +504,16 @@ into the consumer, prepends its binary directory, and hash-binds package, lock,
 installed-package, and executable metadata before and after execution. RunKit
 does not install dependencies or contact a registry for this command.
 
+`--foreign-workspace` emits Quick Receipt V4 and always uses a disposable
+consumer. The exact project-local CLI, receipt store, stdout/stderr, and any
+stdin material remain under the controller `--workspace`; the target receives
+no RunKit initialization. The receipt records the target realpath, HEAD,
+fixed-width status ledger, path/mode/size/content hashes, before/after governed
+filesystem identity, command argv/cwd, and dependency environment. A permanent
+observed target change invalidates the receipt. This is before/after evidence,
+not an OS write sandbox or proof that no transient write was restored between
+observations.
+
 Repeatable literal `--bind-ignored` paths opt specific ignored workspace bytes
 into Workspace Snapshot V2. Missing is a bound state; file or directory changes
 invalidate Quick. Unrequested ignored paths remain explicitly outside the

package/docs/architecture/OWLCODA_RUNKIT_0201_RELEASE_TRUTH_AND_PROFILE_NORMALIZATION_PATCH_DECISION_20260813.md

@@ -0,0 +1,95 @@
+# OwlRunKit 0.20.1 Release Truth and Profile Normalization Patch Decision
+
+Date: 2026-08-13
+Status: `release_artifact_registry_gated`
+
+## Decision
+
+OwlRunKit 0.20.1 is a bounded patch over 0.20.0. It fixes six defects found by
+installing the official 0.20.0 registry package into an isolated consumer and
+then running bootstrap, doctor, profile validation, Team recommendation, and
+Quick attestation.
+
+The patch does not add Team dispatch, new assurance gates, deployment
+authority, or any other product branch.
+
+## Verified 0.20.0 dogfood facts
+
+- Exact registry installation and project-local bootstrap completed.
+- Doctor was ready, 28 profiles validated, Team recommendation remained
+  read-only, and Quick attestation returned GO.
+- The installed 0.20.0 README, Skill, and release policy still carried stale
+  candidate-lifecycle wording and a stale 0.19.2 registry pointer.
+- Applying profile reconciliation rewrote tracked `profiles.json` bytes for a
+  formatting-only normalization even though the update list was empty.
+- An older bootstrap receiving the 0.20.0 exact spec reported only its own
+  0.19.1 exact spec and a generic issue code instead of the install-and-retry
+  correction.
+- `inspect --json` retained complete execution and Project Driver history for
+  a routine blank-session status read.
+- Five historical `no_bound_verification_receipt` warnings were non-blocking
+  but lacked severity, gate semantics, a recommended action, and aggregation.
+- Doctor was ready while the project CLI/Core and process-level shared Skill
+  were on different versions, with no visible reason why fleet activation was
+  deferred.
+
+## Product contract
+
+### Lifecycle-stable release artifacts
+
+`OwlCodaRunKitRegistryReleasePolicyV2` describes immutable artifact behavior,
+not mutable registry time:
+
+- `status=release_artifact_registry_gated`;
+- `artifactVersion` is the package version;
+- `rollbackRelease` is the exact already-published rollback baseline;
+- adoption requires external exact-registry version, shasum, integrity, and
+  tarball evidence;
+- the artifact does not encode mutable publication state or name a moving
+  latest release.
+
+The V1 policy remains historical and is not reinterpreted in place.
+
+### Formatting-only profile reconciliation
+
+A dry-run may still report `normalizationOnly: true` and show the canonical
+proposal. Applying that same plan is a semantic no-op:
+
+- status is `profiles_already_current`;
+- `writesPerformed=0`;
+- the owner profile bytes remain unchanged;
+- no reconcile receipt is created.
+
+Real profile additions or command/path updates retain the existing atomic
+write, receipt, and rollback behavior.
+
+### Compact, actionable upgrade and recovery output
+
+- A version-mismatched bootstrap returns the exact `npm install --save-exact`
+  command for the requested successor and the matching project-local bootstrap
+  dry-run command.
+- `inspect --json --compact` emits `OwlCodaRunKitInspectCompactV1`: project
+  truth hash, progress, dominant gap, owner, next action, warning groups,
+  execution counts, and the false authority boundary only.
+- Existing full inspect remains unchanged; compact cannot be combined with
+  history, a selected run, or verbose output.
+
+### Team warning and shared Skill diagnosis
+
+Team Delivery Status V2 enriches and groups Project Driver warnings while
+leaving Status V1 unchanged. A missing Quick/Formal reference remains
+non-blocking, does not prove that any receipt was attested, and does not impose
+retroactive Formal work on a completed historical WorkItem.
+
+Doctor reports project-local CLI, project Core, and process-level shared Skill
+versions separately. Shared Skill drift does not change `ready`; if fleet-safe
+activation is blocked by an active execution or lease, the blocker and the
+wait-then-refresh action are visible.
+
+## Authority boundary
+
+This document and the packaged artifact grant no npm publication, project
+adoption, Git integration, deployment, production, or business authority.
+All authorization fields remain false. Registry adoption becomes eligible only
+after separate external evidence binds the exact official-registry version,
+shasum, integrity, and tarball URL.

package/docs/architecture/OWLCODA_RUNKIT_020_TEAM_DELIVERY_PHASE1_PRODUCT_DECISION_20260813.md

@@ -0,0 +1,296 @@
+# OwlRunKit 0.20 Team Delivery Phase 1 Product Decision
+
+Date: 2026-08-13
+Status: `source_candidate_implemented_and_verified / initial_read_only_dogfood_passed / owner_release_authorized / registry_publication_pending`
+
+## Decision
+
+OwlRunKit 0.20 Phase 1 adds a read-only Team Delivery projection and portable
+team packet contracts on top of the existing Project Driver. It does not add a
+second task graph, start Agents, route vendors, dispatch work, or change Quick
+or Formal assurance.
+
+The product sequence is fixed:
+
+1. publish and stabilize 0.19.2;
+2. implement 0.20 Phase 1 as read-only recommendation plus native contracts;
+3. dogfood it in at least two real projects;
+4. only if measured net value is positive, ask the Owner whether opt-in assisted
+   dispatch should be designed.
+
+Steps 1 and 2 are complete through a repository source candidate. Step 3 has
+started with read-only recommendation and status projection; transfer and
+acceptance value have not yet been proven through a complete live lifecycle.
+The Owner separately authorized the 0.20 publication transition after the
+initial read-only dogfood. That authorization does not pre-authorize assisted
+dispatch, project adoption, deployment, production, business, funds, or any
+other permission transition.
+
+## Current source-candidate evidence
+
+- Focused Team Delivery and public-contract checks: 25 passed, 0 failed.
+- Compatibility, CLI, project-local binding, and neighboring Formal checks:
+  129 passed, 0 failed.
+- Standalone pack, isolated install, initialization, Team packet validation,
+  and Quick attestation: 6 passed, 0 failed.
+- Complete RunKit gate: 853 tests, 841 passed, 0 failed, 12 skipped.
+- Root build and production dependency audit passed; the production audit
+  reported 0 vulnerabilities.
+- Core, Skill candidate, package config, public attester, and distribution
+  manifest resolve to
+  `sha256:30098aa9344c17c1ed0b5ed45ef1c590b3214b824402f584029c1ecb38ca7a70`.
+
+These facts establish a source candidate only. They do not establish dogfood
+value, registry publication, project adoption, runtime activation, or release
+authority.
+
+## Initial read-only dogfood
+
+The candidate was run directly against current Project Driver truth without
+installing or modifying either target project.
+
+- OwlFootball had one actionable owned lane and one dependency-blocked future
+  lane. Recommendation: `off + project_driver`, assurance unchanged.
+- The active Sierac MES control project had one actionable writer and several
+  dependency-blocked future lanes. Recommendation: `off + project_driver`,
+  assurance unchanged.
+- A real Sierac MES parallel worktree had two simultaneously actionable,
+  disjoint, unassigned lanes. Recommendation: `team + project_driver_team`,
+  both lanes parallel-eligible, no path conflict, assurance unchanged.
+- The first Team result exposed a self-referential `team status` next action.
+  The candidate was corrected so unassigned actionable lanes now point to
+  `project assign --help`; focused and complete gates were rerun afterward.
+- For each directly tested project/worktree, the Project Driver tree
+  fingerprint and Git status fingerprint were byte-identical before and after.
+  Dispatch remained disabled and every authority field remained false.
+
+This establishes correct initial admission and exit behavior. It does not yet
+establish lower handoff time, candidate transfer value, independent acceptance
+value, or eligibility for assisted dispatch.
+
+## Verified starting facts
+
+- `owlrunkit@0.19.2` is published and exact-registry verified.
+- Project Driver already owns durable WorkItems, dependencies, owned paths,
+  assignments, decisions, checkpoints, handoffs, rework, integration gates,
+  source delivery, takeover, and project truth hashing.
+- Usage Mode already keeps continuity and assurance separate.
+- Quick and Formal already own evidence strength; multi-Agent work does not by
+  itself imply Formal.
+- The local `manage-agent-team` Skill contains useful operating policy, but it
+  is not available on every machine and is not an acceptable product runtime
+  dependency.
+- Real dogfood shows Team coordination is useful for multiple writers,
+  independent acceptance, candidate transfer, and cross-session ownership; it
+  is negative value for ordinary single-owner closure.
+
+## Stable product model
+
+Team Delivery adds one orthogonal dimension:
+
+```text
+continuity   none | project_driver
+coordination none | team_delivery
+assurance    none | quick | formal
+acceptance   L0 | L1 | L2 | L3
+authority    always externally granted; never inferred by RunKit
+```
+
+`team_delivery` is a read-only coordination recommendation in Phase 1. It is
+not a continuity mode, assurance level, acceptance verdict, or authority.
+
+Project Driver remains the sole active project and task truth. Team Delivery
+may project WorkItems into lanes, but it cannot create a parallel team/task
+database or reinterpret project events.
+
+## User-visible Phase 1 surface
+
+```text
+npx --no-install owlrunkit team recommend --workspace "$PWD"
+npx --no-install owlrunkit team status --workspace "$PWD"
+npx --no-install owlrunkit team packet validate --workspace "$PWD" --packet <file>
+```
+
+All commands are read-only and support `--json`. Human output is the default.
+Every result includes the authority boundary and
+`authorizationGranted=false`.
+
+### `team recommend`
+
+The recommendation is derived only from current Project Driver truth:
+
+- no initialized project, no ready work, or one ordinary ready WorkItem:
+  `off`;
+- two or more simultaneously actionable WorkItems with disjoint owned paths:
+  `team`;
+- overlapping owned paths: `team`, but parallel writing is blocked and the
+  unique next action is to revise ownership or serialize the lanes;
+- a WorkItem in independent verification: `team`;
+- a pending handoff, rework return, or live candidate ownership transfer:
+  `team`;
+- multiple active owners: `team`.
+
+The result explains trigger reasons, rejected lighter handling, projected
+overhead, path conflicts, acceptance gaps, and one next command. It never
+chooses a model vendor or starts an Agent.
+
+### `team status`
+
+Status projects the current Project Driver into:
+
+- current project identity and truth hash;
+- incomplete lanes with current owner, dependencies, owned paths, and explicit
+  actionable state;
+- which lanes may run concurrently;
+- path conflicts;
+- independent-acceptance gaps;
+- handoff, rework, and source-delivery continuity facts;
+- the current Team recommendation and unique coordination next action.
+
+The next command must not loop back to `team status`. An unassigned actionable
+lane points to assignment help, a path conflict points to immutable scope
+revision help, an owner transition points to takeover help, and an already
+owned Team candidate points to portable packet validation help.
+
+It does not copy or persist a second task graph.
+
+### `team packet validate`
+
+The validator accepts one bounded regular non-symlink JSON file, rejects
+duplicate keys and extra fields, validates the native packet contract, and
+binds project-aware packets to the current `projectId`, `projectTruthHash`,
+WorkItem, and owned paths. Validation performs no packet creation or project
+mutation.
+
+## Native portable contracts
+
+Phase 1 publishes three strict Draft 2020-12 contracts and matching runtime
+validators.
+
+### TeamTaskPacket V2
+
+The task packet binds one Project Driver WorkItem and Gate. It carries:
+
+- actual launcher-declared Agent, model family, and model version;
+- risk axes and required acceptance level;
+- exact worktree and candidate-entry identity;
+- allowed and prohibited paths/actions;
+- evidence plan, verification cadence, handoff requirement, escalation budget,
+  and exact stop point;
+- project identity and project truth hash;
+- an explicit all-false authority boundary.
+
+Model family is opaque declared identity. Core does not contain Sol, Luna,
+Grok, Kimi, capacity ratios, retries, or routing preferences.
+
+### TeamAcceptancePacket V2
+
+The acceptance packet binds one Gate and candidate, records implementation and
+verification identities, acceptance level, fresh adversarial families,
+candidate identity before and after, evidence reuse, findings, verdict, and
+remaining levels. Medium or high second-order risk cannot claim independent
+acceptance when implementation and verification model families are equal.
+
+`ACCEPT`, `REWORK`, and `BLOCKED` remain distinct. One packet accepts one Gate;
+it does not grant the next external transition.
+
+### CandidateTransferPacket V1
+
+The transfer packet preserves a live candidate across writer ownership change:
+
+```text
+candidate_active
+  -> transfer_requested
+  -> packet_generated
+  -> new_owner_validation
+  -> handoff_ack
+  -> old_writer_release
+```
+
+It binds candidate identity, dirty manifest, reconstruction sources, protected
+artifacts, previous and next owner, verification state, and handoff ACK. A
+packet at `old_writer_release` is invalid unless the new owner has accepted the
+handoff with evidence. The packet does not itself assign Project Driver
+authority or release the prior writer.
+
+## Admission and exit rules
+
+Team Mode is recommended only when coordination changes the outcome or critical
+path. Parallelism being possible is insufficient.
+
+The recommendation must explicitly exit Team Mode for a single authorized
+owner with a bounded, reversible, directly verifiable task. Production or
+release labels alone do not force Team Mode. Long duration alone selects
+continuity, not coordination. Multiple Agents alone do not force Formal.
+
+Path conflict does not authorize parallel writers. It creates a visible
+coordination blocker.
+
+## Acceptance scenarios
+
+1. No Project Driver definition returns `off`, zero lanes, no dispatch, and no
+   authority.
+2. One ordinary ready WorkItem returns `off` even though Project Driver exists.
+3. Two independent ready WorkItems with disjoint owned paths return `team` and
+   both lanes are parallel-eligible.
+4. Two actionable WorkItems with overlapping owned paths return `team`, expose
+   the exact conflict, and mark both lanes non-parallel.
+5. Independent verification, pending handoff/rework, candidate transfer, or
+   multiple active owners recommends `team` without changing assurance.
+6. `team recommend`, `team status`, and packet validation write zero project,
+   source, Git, or RunKit bytes.
+7. A valid TeamTaskPacket is bound to the current Project Driver WorkItem and
+   owned paths; stale project truth or widened scope is rejected.
+8. Same-family verification at medium/high second-order risk cannot claim
+   independent acceptance.
+9. Candidate transfer cannot reach `old_writer_release` before accepted
+   handoff ACK with evidence.
+10. Packet schemas and runtime validators reject missing, extra, duplicate-key,
+    authority-looking, and malformed identity fields consistently.
+11. Installed-package help, CLI JSON, public schemas, Core manifest, and the
+    Skill describe the same Phase 1 surface without requiring the local
+    `manage-agent-team` Skill.
+12. No output authorizes Git, release, deployment, production, business,
+    automation, money, credentials, or Agent dispatch.
+
+## Phase 1 non-goals
+
+- no automatic or assisted Agent launch;
+- no vendor CLI federation or general swarm;
+- no model ranking, scorecard, capacity allocation, retry policy, or
+  model-specific prompt logic in Core;
+- no second project/task graph;
+- no packet generator that silently assigns ownership;
+- no new Quick or Formal Gate;
+- no replacement for COM-019 or any domain product decision;
+- no 0.20 publication claim before a separately verified release transition.
+
+## Dogfood Gate before assisted dispatch
+
+At least two real projects must demonstrate all of the following:
+
+- ordinary single-owner work reliably exits Team Mode;
+- multiple writers and independent acceptance produce correct lanes, path
+  conflicts, and independence gaps;
+- a machine without the local Skill can validate and continue from the npm
+  package and self-contained packets;
+- writer transfer preserves the candidate through ACK;
+- measured handoff time, controller intervention, or duplicate verification
+  decreases;
+- the benefit is not merely more packets or receipts.
+
+Only after these facts exist may the Owner decide whether to design opt-in
+assisted dispatch. General automatic federation remains a separate product and
+authority decision.
+
+## What cannot be claimed now
+
+- 0.20 has not completed transfer or independent-acceptance dogfood and has not
+  yet been committed, tagged, registry-published, adopted, or made active;
+  source-candidate verification is not registry publication proof.
+- Team Delivery does not dispatch or supervise Agents.
+- The local Skill is not part of the product runtime contract.
+- Team recommendation is not acceptance or authority.
+- Phase 1 is not the selected COM-019 Primary AI Value Loop.
+- No business, production, deployment, or release outcome follows from this
+  product decision.