[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CF7P0008ZJB58RCZ8ZESRB":3,"skill-same:01M6CF7P0008ZJB58RCZ8ZESRB":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":78,"commitSha":79,"skillDirectory":80,"forksCount":81,"repositoryHtmlUrl":82,"repositoryHomepageUrl":6,"ownerHtmlUrl":83,"ownerBlogUrl":6,"ownerDescription":84,"updatedAt":85,"install":86,"resources":99},"01M6CF7P0008ZJB58RCZ8ZESRB","handoff",null,"Inter-agent \u002F inter-activation \u002F inter-repo handoff. Use when work, state, or messages cross a boundary between two cells, two roles, two activations of the same role, two repos, or two coherence-cell-shaped protocol packages. Owns the wire format; consumers (cnos.cdd, cnos.cds, cnos.cdr, future c-d-X) own the binding.","usurobor\u002Fcnos","usurobor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182342826?v=4","01M6CEXJCRMYD8HB2315FGB1Q8","Peter Lisovin","01M6CEXJH2RW04GQ2SNXY40F5S",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"system","cdd","cds","dispatch","use","channel","repo","public","work","format","how","boundary","enrichment","messages","package","protocol","state","packages","repos","2026-11-10 10:12:30",false,"---\nname: handoff\ndescription: Inter-agent \u002F inter-activation \u002F inter-repo handoff. Use when work, state, or messages cross a boundary between two cells, two roles, two activations of the same role, two repos, or two coherence-cell-shaped protocol packages. Owns the wire format; consumers (cnos.cdd, cnos.cds, cnos.cdr, future c-d-X) own the binding.\nartifact_class: skill\nkata_surface: embedded\ngoverning_question: How do two parts of the system that are not co-located in time, role, repo, or activation transfer state coherently, without inventing the protocol per cycle?\nvisibility: public\ntriggers:\n  - handoff\n  - dispatch\n  - cross-repo\n  - bundle\n  - proposal\n  - clarification\n  - artifact-channel\n  - receipt-stream\n  - inter-activation\n  - inter-agent\nscope: global\ninputs:\n  - handoff event (intra-cycle \u002F inter-cycle \u002F inter-activation \u002F inter-repo)\n  - active role (γ for cross-repo; δ for dispatch enrichment; ε for receipt-stream)\n  - consumer protocol package (cnos.cdd \u002F cnos.cds \u002F cnos.cdr \u002F future c-d-X)\noutputs:\n  - canonical handoff contract loaded (HANDOFF.md)\n  - active sub-skill loaded (cross-repo \u002F dispatch \u002F mid-flight \u002F artifact-channel \u002F receipt-stream)\n  - required Tier 3 skills selected\nrequires:\n  - handoff applies (the matter crosses a cell \u002F role \u002F activation \u002F repo boundary)\ncalls:\n  - HANDOFF.md\n  - cross-repo\u002FSKILL.md\n  - dispatch\u002FSKILL.md\n  - mid-flight\u002FSKILL.md\n  - artifact-channel\u002FSKILL.md\n  - receipt-stream\u002FSKILL.md\n---\n\n# Handoff\n\n## Load order\n\nThis skill is the package-visible loader entrypoint for `cnos.handoff`. External dispatch enters through `handoff` only — internal sub-skill triggers (`cross-repo`, `dispatch`, `mid-flight`, `artifact-channel`, `receipt-stream`) are advisory and are used only after `handoff` and the active sub-skill have been loaded.\n\n**v0.1 status.** `HANDOFF.md` and the five per-surface sub-skill files named in this loader's `calls:` frontmatter are **landed and canonical**. v0.1 is complete; the cnos#404 wave closed on 2026-05-22 via cnos#420. See [`HANDOFF.md`](HANDOFF.md) for the package contract and [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the per-surface source pin and migration provenance.\n\nWhen handoff applies (the matter crosses a cell \u002F role \u002F activation \u002F repo boundary; not \"I am writing matter for my own scope at my own time on my own branch\"):\n\n1. Load [`HANDOFF.md`](HANDOFF.md) in this directory as the canonical wire-format contract. HANDOFF.md declares the package contract (what cnos.handoff owns; what it does not own) and indexes the five Landed sub-surfaces.\n2. Load the sub-skill for the active handoff event:\n   - cross-repo (proposal intake, outbound iteration, bilateral iteration, operator-pending): [`cross-repo\u002FSKILL.md`](cross-repo\u002FSKILL.md)\n   - dispatch (operator → α\u002Fβ\u002Fγ\u002Fδ prompt + implementation-contract enrichment): [`dispatch\u002FSKILL.md`](dispatch\u002FSKILL.md)\n   - mid-flight (γ → in-flight α re-pinning; `gamma-clarification.md` mechanism): [`mid-flight\u002FSKILL.md`](mid-flight\u002FSKILL.md)\n   - artifact-channel (intra-cycle α→β→γ sequential handoff over `.cdd\u002Funreleased\u002F{N}\u002F`): [`artifact-channel\u002FSKILL.md`](artifact-channel\u002FSKILL.md)\n   - receipt-stream (cross-cycle `cdd-iteration.md` + INDEX.md aggregator; ε reader feed): [`receipt-stream\u002FSKILL.md`](receipt-stream\u002FSKILL.md)\n\n   All five v0.1 sub-skills are canonical at their `cnos.handoff` homes — landed via cnos#416 (cross-repo), cnos#417 (dispatch), cnos#418 (mid-flight + artifact-channel), cnos#419 (receipt-stream), with the cross-reference sweep closed via cnos#420. See [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the per-surface source pin.\n\n3. Load Tier 2 (process \u002F role-local) and Tier 3 (lifecycle \u002F kata) skills as directed by the sub-skill and the event shape.\n\n4. Read the consumer protocol package's loader for any binding-specific overrides (e.g., CDS's `.cdd\u002Funreleased\u002F{N}\u002F` rooting; CDR's wave-shaped `.cdr\u002F` rooting; CDD's generic instantiation rules).\n\n## Rule\n\n[`HANDOFF.md`](HANDOFF.md) is the only normative source for:\n\n- the directional case taxonomy (intra-cycle \u002F inter-cycle \u002F inter-activation \u002F inter-repo)\n- the wire-format artifacts per case (bundle file sets; dispatch prompts; clarification files; artifact-channel rules; receipt-stream records)\n- the typed schemas (if any are lifted from Markdown into `schemas\u002Fhandoff\u002F`)\n- the consumer protocol (how a CDD\u002FCDS\u002FCDR\u002Ffuture-c-d-X package binds the wire format)\n\nPer-sub-skill files may add:\n\n- per-case operational detail (e.g., specific bundle file sets per directional case)\n- per-event evidence requirements\n- checklists, examples, katas\n- execution detail for the steps the sub-skill owns\n\nPer-sub-skill files may **not** redefine:\n\n- the directional case taxonomy\n- the wire-format artifact families\n- the consumer-protocol binding contract\n- the boundary against CCNF-O (the orchestration grammar — `cnos.handoff` transports work; CCNF-O composes cells; see \"Cross-protocol relationship\" below)\n\n## Sub-skills\n\nAll five v0.1 sub-skills are Landed; the [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) handoff extraction wave closed on 2026-05-22 via [cnos#420](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F420):\n\n- [`cross-repo\u002F`](cross-repo\u002FSKILL.md) — cross-repo state machine (8-event STATUS lifecycle: drafted\u002Fsubmitted\u002Faccepted\u002Fmodified\u002Frejected\u002Flanded\u002Fwithdrawn\u002Frevised); bundle file sets per directional case (a\u002Fb\u002Fc\u002Fd); LINEAGE.md schemas per case; feedback-patch format; bundle archival rule; hat-collapse attribution. **Migrated wholesale from `cnos.cdd\u002Fskills\u002Fcdd\u002Fcross-repo\u002FSKILL.md` by Sub 2 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#416](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F416).**\n- [`dispatch\u002F`](dispatch\u002FSKILL.md) — dispatch-prompt template (operator → α\u002Fβ\u002Fγ\u002Fδ); implementation-contract 7-axes schema; δ-as-inward-membrane enrichment doctrine; γ template ↔ δ enrichment ↔ α constraint ↔ β verification four-surface mesh. **Migrated from `cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md §2.5` + `cnos.cdd\u002Fskills\u002Fcdd\u002Foperator\u002FSKILL.md §3a` + `cnos.cdd\u002Fskills\u002Fcdd\u002Fdelta\u002FSKILL.md §2` by Sub 3 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#417](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F417).**\n- [`mid-flight\u002F`](mid-flight\u002FSKILL.md) — `gamma-clarification.md` mechanism for intra-cycle re-pinning of axis values; γ-to-in-flight-α channel; cache-bust semantics; spec-staleness propagation. **Authored from cnos#391 empirical anchor by Sub 4 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418).**\n- [`artifact-channel\u002F`](artifact-channel\u002FSKILL.md) — intra-cycle α→β→γ sequential handoff rules over `.cdd\u002Funreleased\u002F{N}\u002F`; per-role artifact write ownership; frozen-snapshot rule on merge; release-time directory move. **Migrated from `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Artifact contract\"` wire-format invariants by Sub 4 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418).** Per-artifact filename set, ownership matrix, and 13-stage Ordered flow remain canonical at cnos.cds (consumer-protocol-specific); the wire-format pattern (channel-shape, sequential rule, frozen-snapshot, release-time move) lives here.\n- [`receipt-stream\u002F`](receipt-stream\u002FSKILL.md) — cross-cycle `cdd-iteration.md` receipt-stream; per-finding shape (F1, F2, …); `.cdd\u002Fiterations\u002FINDEX.md` aggregator; ε reader feed; cross-repo trace bundle on `patch-landed` with `Cross-repo` disposition. **Migrated from `cnos.cdd\u002Fskills\u002Fcdd\u002Fpost-release\u002FSKILL.md §5.6b` by Sub 5 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#419](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F419).**\n\nEach sub-skill is a handoff-specific extension of the wire-format contract in `HANDOFF.md`. The kernel grammar (cell-cell composition, scope-lift projections) is inherited from `cnos.cdd` by reference; the wire format itself is the substrate-independent piece this package owns.\n\n## Cross-protocol relationship\n\n`cnos.handoff` owns **wire formats and handoff doctrine for inter-agent \u002F inter-activation \u002F inter-repo transport.** Three current consumers — [`cnos.cdd`](..\u002F..\u002F..\u002Fcnos.cdd\u002F) (which uses handoff doctrine natively for its own coordination layer), [`cnos.cdr`](..\u002F..\u002F..\u002Fcnos.cdr\u002F) (which has loaded `cross-repo\u002FSKILL.md` via cross-package reference since v0.1 per [cnos#376](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F376)), and [`cnos.cds`](..\u002F..\u002F..\u002Fcnos.cds\u002F) (which absorbed some surfaces during the [cnos#403](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F403) wave and continues to cite others from `cnos.cdd`) — and an open class of future c-d-X protocol packages that will consume the same primitives once the extraction lands.\n\n**Boundary vs CCNF-O (Track A of [cnos#405](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F405)):** `cnos.handoff` transports work between cells; CCNF-O composes cells into cycles, waves, roadmaps, gates, joins. The two have **different reasons to change**: handoff changes when the wire format changes; CCNF-O changes when the composition grammar changes. Each has one reason to change. Sub 1 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) preserves this boundary by explicitly not preempting CCNF-O surfaces — no orchestration-composition grammar appears in this package; Track A of [cnos#405](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F405) is gated on the `cnos#404` wave closing.\n\n**Boundary vs the domain protocols (CDD \u002F CDS \u002F CDR \u002F future c-d-X):** handoff is the *wire format*; the domain protocols are the *cycle lifecycles*. CDD changes when the generic kernel changes; CDS changes when the software-engineering cycle shape changes; CDR changes when the research-cycle shape changes. None of those changes ought to ripple into handoff doctrine, and vice versa.\n\n**`cnos.handoff` is not CDD-with-different-words.** CDD owns the cycle lifecycle and the CCNF kernel; `cnos.handoff` owns the wire format by which cycles talk to each other and the wire format by which roles within a cycle talk to each other. Loading the `handoff` skill is a class-routing act — the matter is a boundary-crossing event (intra-cycle, inter-cycle, inter-activation, or inter-repo); not \"I am writing α-matter for my own scope at my own time on my own branch\" (that's a domain-protocol activity, not a handoff event).\n\n## Conflict rule\n\nIf this file and [`HANDOFF.md`](HANDOFF.md) disagree, `HANDOFF.md` governs.\n\nIf a sub-skill and `HANDOFF.md` disagree on the directional case taxonomy, the wire-format artifact families, or the consumer-protocol binding contract, `HANDOFF.md` governs.\n\nIf a sub-skill adds execution detail, evidence requirements, or operational gates for a wire-format case **without** changing that case's taxonomy or artifact family, the sub-skill governs for that local execution detail.\n\nIf `HANDOFF.md` and a consumer protocol (CDD \u002F CDS \u002F CDR \u002F future c-d-X) disagree on the wire format for a handoff event, `HANDOFF.md` governs (consumers bind the wire format; the wire format does not adapt to its consumers). The consumer may add binding-specific overrides (e.g., directory rooting; filename conventions) but must do so in its own loader, not by re-stating handoff doctrine.\n\nIf `HANDOFF.md` and `cnos.cdd` (CCNF kernel) disagree on the cell-cell composition or scope-lift projections, `cnos.cdd` governs (handoff transports between cells; cell grammar lives in the kernel).\n\n## v0.1 surface\n\n`HANDOFF.md` and the five sub-skill files named in this loader's `calls:` frontmatter are all **landed and canonical** as of 2026-05-22 (cnos#404 wave closed via cnos#420). See [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the surface-by-surface migration provenance.\n\nThe canonical homes are:\n\n- Cross-repo doctrine: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](cross-repo\u002FSKILL.md) (landed under Sub 2 \u002F [cnos#416](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F416); compatibility pointer at `cnos.cdd\u002Fskills\u002Fcdd\u002Fcross-repo\u002FSKILL.md`)\n- Dispatch + implementation-contract: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fdispatch\u002FSKILL.md`](dispatch\u002FSKILL.md) (landed under Sub 3 \u002F [cnos#417](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F417); consumer-side role-skill realizations at `cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md §2.5`, `delta\u002FSKILL.md §2`, `alpha\u002FSKILL.md §3.6`, `beta\u002FSKILL.md` Rule 7)\n- Mid-flight rescue: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fmid-flight\u002FSKILL.md`](mid-flight\u002FSKILL.md) (landed under Sub 4 \u002F [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418); v0.1 software-cycle operational realization at `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Coordination surfaces\" → \"Mid-flight clarification\"`)\n- Artifact channel: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fartifact-channel\u002FSKILL.md`](artifact-channel\u002FSKILL.md) (landed under Sub 4 \u002F [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418); CDS-specific per-artifact contract at `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Artifact contract\"`)\n- Receipt-stream: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](receipt-stream\u002FSKILL.md) (landed under Sub 5 \u002F [cnos#419](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F419); cdd-side runbook pointer at `cnos.cdd\u002Fskills\u002Fcdd\u002Fpost-release\u002FSKILL.md §5.6b`; live aggregator data at `.cdd\u002Fiterations\u002FINDEX.md`)\n","# Handoff\n\n## Load order\n\nThis skill is the package-visible loader entrypoint for `cnos.handoff`. External dispatch enters through `handoff` only — internal sub-skill triggers (`cross-repo`, `dispatch`, `mid-flight`, `artifact-channel`, `receipt-stream`) are advisory and are used only after `handoff` and the active sub-skill have been loaded.\n\n**v0.1 status.** `HANDOFF.md` and the five per-surface sub-skill files named in this loader's `calls:` frontmatter are **landed and canonical**. v0.1 is complete; the cnos#404 wave closed on 2026-05-22 via cnos#420. See [`HANDOFF.md`](HANDOFF.md) for the package contract and [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the per-surface source pin and migration provenance.\n\nWhen handoff applies (the matter crosses a cell \u002F role \u002F activation \u002F repo boundary; not \"I am writing matter for my own scope at my own time on my own branch\"):\n\n1. Load [`HANDOFF.md`](HANDOFF.md) in this directory as the canonical wire-format contract. HANDOFF.md declares the package contract (what cnos.handoff owns; what it does not own) and indexes the five Landed sub-surfaces.\n2. Load the sub-skill for the active handoff event:\n   - cross-repo (proposal intake, outbound iteration, bilateral iteration, operator-pending): [`cross-repo\u002FSKILL.md`](cross-repo\u002FSKILL.md)\n   - dispatch (operator → α\u002Fβ\u002Fγ\u002Fδ prompt + implementation-contract enrichment): [`dispatch\u002FSKILL.md`](dispatch\u002FSKILL.md)\n   - mid-flight (γ → in-flight α re-pinning; `gamma-clarification.md` mechanism): [`mid-flight\u002FSKILL.md`](mid-flight\u002FSKILL.md)\n   - artifact-channel (intra-cycle α→β→γ sequential handoff over `.cdd\u002Funreleased\u002F{N}\u002F`): [`artifact-channel\u002FSKILL.md`](artifact-channel\u002FSKILL.md)\n   - receipt-stream (cross-cycle `cdd-iteration.md` + INDEX.md aggregator; ε reader feed): [`receipt-stream\u002FSKILL.md`](receipt-stream\u002FSKILL.md)\n\n   All five v0.1 sub-skills are canonical at their `cnos.handoff` homes — landed via cnos#416 (cross-repo), cnos#417 (dispatch), cnos#418 (mid-flight + artifact-channel), cnos#419 (receipt-stream), with the cross-reference sweep closed via cnos#420. See [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the per-surface source pin.\n\n3. Load Tier 2 (process \u002F role-local) and Tier 3 (lifecycle \u002F kata) skills as directed by the sub-skill and the event shape.\n\n4. Read the consumer protocol package's loader for any binding-specific overrides (e.g., CDS's `.cdd\u002Funreleased\u002F{N}\u002F` rooting; CDR's wave-shaped `.cdr\u002F` rooting; CDD's generic instantiation rules).\n\n## Rule\n\n[`HANDOFF.md`](HANDOFF.md) is the only normative source for:\n\n- the directional case taxonomy (intra-cycle \u002F inter-cycle \u002F inter-activation \u002F inter-repo)\n- the wire-format artifacts per case (bundle file sets; dispatch prompts; clarification files; artifact-channel rules; receipt-stream records)\n- the typed schemas (if any are lifted from Markdown into `schemas\u002Fhandoff\u002F`)\n- the consumer protocol (how a CDD\u002FCDS\u002FCDR\u002Ffuture-c-d-X package binds the wire format)\n\nPer-sub-skill files may add:\n\n- per-case operational detail (e.g., specific bundle file sets per directional case)\n- per-event evidence requirements\n- checklists, examples, katas\n- execution detail for the steps the sub-skill owns\n\nPer-sub-skill files may **not** redefine:\n\n- the directional case taxonomy\n- the wire-format artifact families\n- the consumer-protocol binding contract\n- the boundary against CCNF-O (the orchestration grammar — `cnos.handoff` transports work; CCNF-O composes cells; see \"Cross-protocol relationship\" below)\n\n## Sub-skills\n\nAll five v0.1 sub-skills are Landed; the [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) handoff extraction wave closed on 2026-05-22 via [cnos#420](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F420):\n\n- [`cross-repo\u002F`](cross-repo\u002FSKILL.md) — cross-repo state machine (8-event STATUS lifecycle: drafted\u002Fsubmitted\u002Faccepted\u002Fmodified\u002Frejected\u002Flanded\u002Fwithdrawn\u002Frevised); bundle file sets per directional case (a\u002Fb\u002Fc\u002Fd); LINEAGE.md schemas per case; feedback-patch format; bundle archival rule; hat-collapse attribution. **Migrated wholesale from `cnos.cdd\u002Fskills\u002Fcdd\u002Fcross-repo\u002FSKILL.md` by Sub 2 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#416](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F416).**\n- [`dispatch\u002F`](dispatch\u002FSKILL.md) — dispatch-prompt template (operator → α\u002Fβ\u002Fγ\u002Fδ); implementation-contract 7-axes schema; δ-as-inward-membrane enrichment doctrine; γ template ↔ δ enrichment ↔ α constraint ↔ β verification four-surface mesh. **Migrated from `cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md §2.5` + `cnos.cdd\u002Fskills\u002Fcdd\u002Foperator\u002FSKILL.md §3a` + `cnos.cdd\u002Fskills\u002Fcdd\u002Fdelta\u002FSKILL.md §2` by Sub 3 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#417](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F417).**\n- [`mid-flight\u002F`](mid-flight\u002FSKILL.md) — `gamma-clarification.md` mechanism for intra-cycle re-pinning of axis values; γ-to-in-flight-α channel; cache-bust semantics; spec-staleness propagation. **Authored from cnos#391 empirical anchor by Sub 4 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418).**\n- [`artifact-channel\u002F`](artifact-channel\u002FSKILL.md) — intra-cycle α→β→γ sequential handoff rules over `.cdd\u002Funreleased\u002F{N}\u002F`; per-role artifact write ownership; frozen-snapshot rule on merge; release-time directory move. **Migrated from `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Artifact contract\"` wire-format invariants by Sub 4 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418).** Per-artifact filename set, ownership matrix, and 13-stage Ordered flow remain canonical at cnos.cds (consumer-protocol-specific); the wire-format pattern (channel-shape, sequential rule, frozen-snapshot, release-time move) lives here.\n- [`receipt-stream\u002F`](receipt-stream\u002FSKILL.md) — cross-cycle `cdd-iteration.md` receipt-stream; per-finding shape (F1, F2, …); `.cdd\u002Fiterations\u002FINDEX.md` aggregator; ε reader feed; cross-repo trace bundle on `patch-landed` with `Cross-repo` disposition. **Migrated from `cnos.cdd\u002Fskills\u002Fcdd\u002Fpost-release\u002FSKILL.md §5.6b` by Sub 5 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) — landed under [cnos#419](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F419).**\n\nEach sub-skill is a handoff-specific extension of the wire-format contract in `HANDOFF.md`. The kernel grammar (cell-cell composition, scope-lift projections) is inherited from `cnos.cdd` by reference; the wire format itself is the substrate-independent piece this package owns.\n\n## Cross-protocol relationship\n\n`cnos.handoff` owns **wire formats and handoff doctrine for inter-agent \u002F inter-activation \u002F inter-repo transport.** Three current consumers — [`cnos.cdd`](..\u002F..\u002F..\u002Fcnos.cdd\u002F) (which uses handoff doctrine natively for its own coordination layer), [`cnos.cdr`](..\u002F..\u002F..\u002Fcnos.cdr\u002F) (which has loaded `cross-repo\u002FSKILL.md` via cross-package reference since v0.1 per [cnos#376](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F376)), and [`cnos.cds`](..\u002F..\u002F..\u002Fcnos.cds\u002F) (which absorbed some surfaces during the [cnos#403](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F403) wave and continues to cite others from `cnos.cdd`) — and an open class of future c-d-X protocol packages that will consume the same primitives once the extraction lands.\n\n**Boundary vs CCNF-O (Track A of [cnos#405](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F405)):** `cnos.handoff` transports work between cells; CCNF-O composes cells into cycles, waves, roadmaps, gates, joins. The two have **different reasons to change**: handoff changes when the wire format changes; CCNF-O changes when the composition grammar changes. Each has one reason to change. Sub 1 of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404) preserves this boundary by explicitly not preempting CCNF-O surfaces — no orchestration-composition grammar appears in this package; Track A of [cnos#405](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F405) is gated on the `cnos#404` wave closing.\n\n**Boundary vs the domain protocols (CDD \u002F CDS \u002F CDR \u002F future c-d-X):** handoff is the *wire format*; the domain protocols are the *cycle lifecycles*. CDD changes when the generic kernel changes; CDS changes when the software-engineering cycle shape changes; CDR changes when the research-cycle shape changes. None of those changes ought to ripple into handoff doctrine, and vice versa.\n\n**`cnos.handoff` is not CDD-with-different-words.** CDD owns the cycle lifecycle and the CCNF kernel; `cnos.handoff` owns the wire format by which cycles talk to each other and the wire format by which roles within a cycle talk to each other. Loading the `handoff` skill is a class-routing act — the matter is a boundary-crossing event (intra-cycle, inter-cycle, inter-activation, or inter-repo); not \"I am writing α-matter for my own scope at my own time on my own branch\" (that's a domain-protocol activity, not a handoff event).\n\n## Conflict rule\n\nIf this file and [`HANDOFF.md`](HANDOFF.md) disagree, `HANDOFF.md` governs.\n\nIf a sub-skill and `HANDOFF.md` disagree on the directional case taxonomy, the wire-format artifact families, or the consumer-protocol binding contract, `HANDOFF.md` governs.\n\nIf a sub-skill adds execution detail, evidence requirements, or operational gates for a wire-format case **without** changing that case's taxonomy or artifact family, the sub-skill governs for that local execution detail.\n\nIf `HANDOFF.md` and a consumer protocol (CDD \u002F CDS \u002F CDR \u002F future c-d-X) disagree on the wire format for a handoff event, `HANDOFF.md` governs (consumers bind the wire format; the wire format does not adapt to its consumers). The consumer may add binding-specific overrides (e.g., directory rooting; filename conventions) but must do so in its own loader, not by re-stating handoff doctrine.\n\nIf `HANDOFF.md` and `cnos.cdd` (CCNF kernel) disagree on the cell-cell composition or scope-lift projections, `cnos.cdd` governs (handoff transports between cells; cell grammar lives in the kernel).\n\n## v0.1 surface\n\n`HANDOFF.md` and the five sub-skill files named in this loader's `calls:` frontmatter are all **landed and canonical** as of 2026-05-22 (cnos#404 wave closed via cnos#420). See [`docs\u002Fextraction-map.md`](..\u002F..\u002Fdocs\u002Fextraction-map.md) for the surface-by-surface migration provenance.\n\nThe canonical homes are:\n\n- Cross-repo doctrine: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](cross-repo\u002FSKILL.md) (landed under Sub 2 \u002F [cnos#416](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F416); compatibility pointer at `cnos.cdd\u002Fskills\u002Fcdd\u002Fcross-repo\u002FSKILL.md`)\n- Dispatch + implementation-contract: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fdispatch\u002FSKILL.md`](dispatch\u002FSKILL.md) (landed under Sub 3 \u002F [cnos#417](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F417); consumer-side role-skill realizations at `cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md §2.5`, `delta\u002FSKILL.md §2`, `alpha\u002FSKILL.md §3.6`, `beta\u002FSKILL.md` Rule 7)\n- Mid-flight rescue: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fmid-flight\u002FSKILL.md`](mid-flight\u002FSKILL.md) (landed under Sub 4 \u002F [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418); v0.1 software-cycle operational realization at `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Coordination surfaces\" → \"Mid-flight clarification\"`)\n- Artifact channel: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fartifact-channel\u002FSKILL.md`](artifact-channel\u002FSKILL.md) (landed under Sub 4 \u002F [cnos#418](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F418); CDS-specific per-artifact contract at `cnos.cds\u002Fskills\u002Fcds\u002FCDS.md §\"Artifact contract\"`)\n- Receipt-stream: [`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](receipt-stream\u002FSKILL.md) (landed under Sub 5 \u002F [cnos#419](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F419); cdd-side runbook pointer at `cnos.cdd\u002Fskills\u002Fcdd\u002Fpost-release\u002FSKILL.md §5.6b`; live aggregator data at `.cdd\u002Fiterations\u002FINDEX.md`)\n",{"name":5,"calls":48,"scope":55,"inputs":56,"outputs":60,"requires":64,"triggers":66,"visibility":31,"description":7,"kata_surface":75,"artifact_class":76,"governing_question":77},[49,50,51,52,53,54],"HANDOFF.md","cross-repo\u002FSKILL.md","dispatch\u002FSKILL.md","mid-flight\u002FSKILL.md","artifact-channel\u002FSKILL.md","receipt-stream\u002FSKILL.md","global",[57,58,59],"handoff event (intra-cycle \u002F inter-cycle \u002F inter-activation \u002F inter-repo)","active role (γ for cross-repo; δ for dispatch enrichment; ε for receipt-stream)","consumer protocol package (cnos.cdd \u002F cnos.cds \u002F cnos.cdr \u002F future c-d-X)",[61,62,63],"canonical handoff contract loaded (HANDOFF.md)","active sub-skill loaded (cross-repo \u002F dispatch \u002F mid-flight \u002F artifact-channel \u002F receipt-stream)","required Tier 3 skills selected",[65],"handoff applies (the matter crosses a cell \u002F role \u002F activation \u002F repo boundary)",[5,27,67,68,69,70,71,72,73,74],"cross-repo","bundle","proposal","clarification","artifact-channel","receipt-stream","inter-activation","inter-agent","embedded","skill","How do two parts of the system that are not co-located in time, role, repo, or activation transfer state coherently, without inventing the protocol per cycle?","main","fb527e6c4bfb75c71fa75d6471b3aa3da32106d4","src\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff",0,"https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos","https:\u002F\u002Fgithub.com\u002Fusurobor","Coherence engineer. Building git-CN.","2026-11-07 14:25:44",{"source":8,"skillName":5,"commands":87,"prompt":97,"zipAvailable":98},[88,91,94],{"tool":89,"command":90},"npx","npx skills add usurobor\u002Fcnos --skill handoff",{"tool":92,"command":93},"bunx","bunx skills add usurobor\u002Fcnos --skill handoff",{"tool":95,"command":96},"pnpm","pnpm dlx skills add usurobor\u002Fcnos --skill handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002FSKILL.md",true,[100],{"path":49,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"REFERENCE","参考文档",4733,"https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002FHANDOFF.md",[106,121,136,162,175,189],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":43},"01M6CF8RWQPM0VXZG06XMR0FFX","issues\u002Ftriage","Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close\u002Fsupersede\u002Fdefer.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Ftriage\u002FSKILL.md",[],[113,114,115,116,117,34,118,31,28,27,119,120],"triage","issues","issues triage","issue triage","SET","decision","issue","doctrine",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":43},"01M6CF8PJ812DD4APZ3WE8X67B","issues\u002Ftaxonomy","Issue label taxonomy pointer. Use when classifying an issue's kind\u002Farea\u002Fpriority\u002Feffort\u002Fstatus\u002Fprotocol\u002Fdispatch labels, or when the board needs to interpret them.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Ftaxonomy\u002FSKILL.md",[],[114,128,129,130,131,39,117,132,31,133,28,27,134,119,135],"taxonomy","issues taxonomy","github","status","open","board","github issue","issue labels",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":150,"publishedAt":43},"01M6CF8KBMZ4D0CDJQ3PF1YVTP","issues\u002Fmap","Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON\u002FHTML output contract.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Fmap\u002FSKILL.md",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[114,151,130,152,153,154,117,155,128,132,34,156,157,133,158,159,160,161,28,119],"issues map","reasoning","data","pipeline","api","json","README","edit","interactive","fetch","generated",{"skillNo":163,"name":114,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":43},"01M6CF8CZQH7G7B7RZPANQWR4G","cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot \u002F issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002FSKILL.md",[],[114,130,168,169,170,171,40,38,35,128,132,34,118,172,157,173,28,174,27,26],"pr","current state","run","artifacts","branch","command","only",{"skillNo":176,"name":72,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":43},"01M6CF896XKSRQVB1CSHY8GSXB","Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd\u002Fiterations\u002FINDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md",[],[181,5,171,39,182,34,183,33,184,31,30,185,186,29,28,75,187,188,25,120],"receipt stream","index","learning","trace","closeout","read","patch","shape",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":43},"01M6CF84VCBME6RK8V6HAVDM8Z","mid-flight","Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin\u002Fmain while α\u002Fβ polling sessions are in-flight.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fmid-flight\u002FSKILL.md",[],[196,130,197,198,199,200,34,201,202,172,30,186,28,174,27,203,134,204,205,206],"mid flight","change","sessions","file","cache","pin","coordination","up","Legacy","gamma","artifact channel"]