[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CF273B5FEF9VP08F8BK7VT":3,"skill-same:01M6CF273B5FEF9VP08F8BK7VT":80},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6CF273B5FEF9VP08F8BK7VT","epsilon",null,"ε role in CDR. Iterates the CDR protocol itself — observes research-protocol gaps from the receipt stream, applies MCA discipline, writes the CDR-iteration artifact.","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.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[5,24,25,26,27,28,29,30],"research","protocol","risk","CDR","how","discipline","embedded","2026-11-10 10:12:30",false,"---\nname: epsilon\ndescription: ε role in CDR. Iterates the CDR protocol itself — observes research-protocol gaps from the receipt stream, applies MCA discipline, writes the CDR-iteration artifact.\nartifact_class: skill\nparent: cdr\nscope: role-local\ngoverning_question: How does ε turn research-protocol-gap findings from the receipt stream into durable CDR-protocol improvements without accumulating undeclared overclaim risk?\ntriggers:\n  - epsilon\n  - cdr-iteration\n  - protocol-iteration\nkata_surface: embedded\ninputs:\n  - the CDR receipt stream\n  - research-protocol-gap findings\noutputs:\n  - a CDR-iteration artifact recording durable protocol improvements under MCA discipline\n---\n\n# Epsilon (research ε)\n\n> **This is the CDR-specific instantiation of the generic ε doctrine declared in\n> [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).** The kernel grammar —\n> ε-as-protocol-reviewer in the scope ladder, the watched receipt fields\n> (`protocol_gap_count`, `protocol_gap_refs`), the gap-class instantiation\n> pattern (`{protocol}-{axis}-gap`), the iteration-artifact rule (required\n> only when `protocol_gap_count > 0`), the MCA discipline (ship-now \u002F\n> next-MCA \u002F no-patch), and the ε=δ collapse rule for small-protocol\n> regimes — is inherited by reference. Only the **trigger classes**\n> (research-failure classes per [`CDR.md`](..\u002FCDR.md) Field 5, not\n> engineering-failure classes) and the **output-artifact location** (the\n> CDR-iteration artifact under the project binding's wave surface) diverge\n> for the research loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction).\n\n## §1 ε's CDR-side scope\n\nε's domain in CDR is **protocol-iteration**: the work of observing whether the CDR protocol is itself coherent — whether it selects the right research gaps, closes them with correctly-calibrated typed receipts, and produces a research-claim transmission discipline that learns from its own waves rather than repeating the same overclaim class.\n\nThe canonical output artifact is the **CDR-iteration record** (the research analogue of `cdd-iteration.md`). Per the inherited cadence rule ([`ROLES.md §4b.4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)), the artifact is required only when the wave's receipt has `protocol_gap_count > 0` — i.e. when the wave produced ≥1 finding tagged with one of the `cdr-*-gap` classes below. The receipt's `protocol_gap_count == 0` is the no-gap signal; no iteration file is required when the wave ran cleanly. The artifact's concrete location is project-binding-dependent (typically `\u003Cproject>\u002F.cdr\u002Fwaves\u002F{wave-id}\u002Fcdr-iteration.md` or an equivalent under the project's wave surface); the protocol-overlay layer declares the artifact's existence and shape, not its file path.\n\nFor waves that produce findings, the trigger classes the artifact enumerates are CDR-specific (per [`CDR.md §\"Field 5\"`](..\u002FCDR.md)):\n\n- **`cdr-data-gate-gap`** — receipts shipping `observed` or `computed` claims with under-specified `data_refs` (no manifest, no checksum, no data-use compliance record). Signals the data-policy oracle (Field 2) is not being enforced.\n- **`cdr-overclaim-gap`** — receipts whose `claim_status: observed` evidence supports only `inferred`. Signals β's claim\u002Fevidence-alignment oracle is too lenient or under-specified; the procedural skill (`cnos.cdr\u002Fskills\u002Fcdr\u002Fbeta\u002FSKILL.md`) needs a sharper calibration-determination procedure.\n- **`cdr-reproduction-gap`** — receipts with `reproduction.output_match: false`, or receipts that should have a reproduction record (per Field 2 + per `cnos.cdr\u002Fskills\u002Fcdr\u002Falpha\u002FSKILL.md` §\"Evidence-ref completeness rule\") but lack one. Signals reproduction-from-clean is not running or is failing silently.\n- **`cdr-citation-gap`** — receipts with claims that should cite external work but do not, or citations that do not support the claim they are invoked for. Signals the citation-integrity oracle is drifting.\n- **`cdr-oracle-ambiguity-gap`** — the same review-oracle interpretation question appears across multiple waves (β cannot decide; γ has to adjudicate). Signals oracle under-specification at the protocol layer; `CDR.md` or the per-role skills need additional procedural detail.\n- **`cdr-construct-drift-gap`** — a key research construct's definition shifts across receipts without explicit deprecation. Signals the project binding (cph or downstream) needs a construct-stability artifact (a glossary, a deprecation registry); the protocol-layer surface ε patches may declare a placeholder convention.\n\nThese are the research-failure trigger classes, distinct from engineering's `cdd-skill-gap`, `cdd-protocol-gap`, `cdd-tooling-gap`, `cdd-metric-gap`. The MCA-discipline shape (ship now \u002F next-MCA \u002F drop) is identical.\n\nThe MCA discipline governs what ε does with each finding (per the generic doctrine):\n\n- **MCA available** (skill patch, gate, schema refinement) → ship it now as an immediate output in the same session.\n- **No MCA yet, pattern real** → file a protocol MCI (entry in the project binding's iteration INDEX + an issue against `cnos.cdr` if the patch crosses the protocol boundary).\n- **One-off, no pattern** → drop; note the drop explicitly.\n\nε cross-references [`ROLES.md §1`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#1-the-role-ladder) row 5 (ε iterates the δ-discipline) and [`CDR.md §\"Field 5\"`](..\u002FCDR.md) (the authoring procedure and per-finding shape for the CDR-iteration artifact).\n\n## §2 ε's relationship to δ\n\nε and δ are often the same actor for research, just as for engineering. In small-protocol regimes — one active research operator running a handful of waves — protocol-iteration volume does not justify a dedicated reviewer of the protocol. The operator (δ) naturally accumulates the longitudinal view ε requires and performs ε work as part of wave close-out triage.\n\nSeparation becomes warranted when protocol-iteration volume justifies dedicated attention: when the CDR-iteration artifact is written on most waves with non-empty findings; when the iteration INDEX accumulates faster than one actor can triage; when the operator's operational load crowds out the reflective work. At that point, ε may be a distinct actor — a second agent or a dedicated human — who reads receipts across waves and drives protocol patches independently.\n\nNo claim is made here that ε is required as a separate human or agent. ε is a structural role in the scope-escalation ladder ([`ROLES.md §1`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#1-the-role-ladder)), not a headcount requirement. The role may collapse onto δ indefinitely in small-protocol regimes; the obligation is that ε work happens and is attributed, not that it is performed by a distinct person.\n\nSee [`ROLES.md §4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4-hats-vs-actors-roles-as-behavioral-contracts) for the general principle governing role collapse rules, and [`CDR.md §\"Field 6\"`](..\u002FCDR.md) for CDR's specific collapse rule — note that the α=β collapse is **never** safe for research-claim cycles (overclaim is the precise failure mode α cannot self-detect), while ε=δ and γ=δ are conditionally permitted.\n\n## §3 Persona \u002F protocol \u002F project boundary\n\nThis overlay declares **what research ε does at the protocol layer**. It does not declare:\n\n- **Who enacts ε** (persona — layer 1; lives in `\u003Cpersona-hub>\u002Fspec\u002F`).\n- **What concrete iteration-INDEX path or wave directory ε writes to** (project — layer 4; lives in `\u003Cproject>\u002F.cdr\u002F`). The trigger classes are protocol-bound (`cdr-*-gap` enumerated above); the storage path is project-bound.\n\nIf a project chooses additional trigger classes (e.g. `cdr-ethics-gap` for waves whose data raises ethics-review issues, or `cdr-stats-gap` for statistical-method drift), those are project-binding extensions; this overlay declares the minimum set per `CDR.md §\"Field 5\"`.\n","# Epsilon (research ε)\n\n> **This is the CDR-specific instantiation of the generic ε doctrine declared in\n> [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).** The kernel grammar —\n> ε-as-protocol-reviewer in the scope ladder, the watched receipt fields\n> (`protocol_gap_count`, `protocol_gap_refs`), the gap-class instantiation\n> pattern (`{protocol}-{axis}-gap`), the iteration-artifact rule (required\n> only when `protocol_gap_count > 0`), the MCA discipline (ship-now \u002F\n> next-MCA \u002F no-patch), and the ε=δ collapse rule for small-protocol\n> regimes — is inherited by reference. Only the **trigger classes**\n> (research-failure classes per [`CDR.md`](..\u002FCDR.md) Field 5, not\n> engineering-failure classes) and the **output-artifact location** (the\n> CDR-iteration artifact under the project binding's wave surface) diverge\n> for the research loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction).\n\n## §1 ε's CDR-side scope\n\nε's domain in CDR is **protocol-iteration**: the work of observing whether the CDR protocol is itself coherent — whether it selects the right research gaps, closes them with correctly-calibrated typed receipts, and produces a research-claim transmission discipline that learns from its own waves rather than repeating the same overclaim class.\n\nThe canonical output artifact is the **CDR-iteration record** (the research analogue of `cdd-iteration.md`). Per the inherited cadence rule ([`ROLES.md §4b.4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)), the artifact is required only when the wave's receipt has `protocol_gap_count > 0` — i.e. when the wave produced ≥1 finding tagged with one of the `cdr-*-gap` classes below. The receipt's `protocol_gap_count == 0` is the no-gap signal; no iteration file is required when the wave ran cleanly. The artifact's concrete location is project-binding-dependent (typically `\u003Cproject>\u002F.cdr\u002Fwaves\u002F{wave-id}\u002Fcdr-iteration.md` or an equivalent under the project's wave surface); the protocol-overlay layer declares the artifact's existence and shape, not its file path.\n\nFor waves that produce findings, the trigger classes the artifact enumerates are CDR-specific (per [`CDR.md §\"Field 5\"`](..\u002FCDR.md)):\n\n- **`cdr-data-gate-gap`** — receipts shipping `observed` or `computed` claims with under-specified `data_refs` (no manifest, no checksum, no data-use compliance record). Signals the data-policy oracle (Field 2) is not being enforced.\n- **`cdr-overclaim-gap`** — receipts whose `claim_status: observed` evidence supports only `inferred`. Signals β's claim\u002Fevidence-alignment oracle is too lenient or under-specified; the procedural skill (`cnos.cdr\u002Fskills\u002Fcdr\u002Fbeta\u002FSKILL.md`) needs a sharper calibration-determination procedure.\n- **`cdr-reproduction-gap`** — receipts with `reproduction.output_match: false`, or receipts that should have a reproduction record (per Field 2 + per `cnos.cdr\u002Fskills\u002Fcdr\u002Falpha\u002FSKILL.md` §\"Evidence-ref completeness rule\") but lack one. Signals reproduction-from-clean is not running or is failing silently.\n- **`cdr-citation-gap`** — receipts with claims that should cite external work but do not, or citations that do not support the claim they are invoked for. Signals the citation-integrity oracle is drifting.\n- **`cdr-oracle-ambiguity-gap`** — the same review-oracle interpretation question appears across multiple waves (β cannot decide; γ has to adjudicate). Signals oracle under-specification at the protocol layer; `CDR.md` or the per-role skills need additional procedural detail.\n- **`cdr-construct-drift-gap`** — a key research construct's definition shifts across receipts without explicit deprecation. Signals the project binding (cph or downstream) needs a construct-stability artifact (a glossary, a deprecation registry); the protocol-layer surface ε patches may declare a placeholder convention.\n\nThese are the research-failure trigger classes, distinct from engineering's `cdd-skill-gap`, `cdd-protocol-gap`, `cdd-tooling-gap`, `cdd-metric-gap`. The MCA-discipline shape (ship now \u002F next-MCA \u002F drop) is identical.\n\nThe MCA discipline governs what ε does with each finding (per the generic doctrine):\n\n- **MCA available** (skill patch, gate, schema refinement) → ship it now as an immediate output in the same session.\n- **No MCA yet, pattern real** → file a protocol MCI (entry in the project binding's iteration INDEX + an issue against `cnos.cdr` if the patch crosses the protocol boundary).\n- **One-off, no pattern** → drop; note the drop explicitly.\n\nε cross-references [`ROLES.md §1`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#1-the-role-ladder) row 5 (ε iterates the δ-discipline) and [`CDR.md §\"Field 5\"`](..\u002FCDR.md) (the authoring procedure and per-finding shape for the CDR-iteration artifact).\n\n## §2 ε's relationship to δ\n\nε and δ are often the same actor for research, just as for engineering. In small-protocol regimes — one active research operator running a handful of waves — protocol-iteration volume does not justify a dedicated reviewer of the protocol. The operator (δ) naturally accumulates the longitudinal view ε requires and performs ε work as part of wave close-out triage.\n\nSeparation becomes warranted when protocol-iteration volume justifies dedicated attention: when the CDR-iteration artifact is written on most waves with non-empty findings; when the iteration INDEX accumulates faster than one actor can triage; when the operator's operational load crowds out the reflective work. At that point, ε may be a distinct actor — a second agent or a dedicated human — who reads receipts across waves and drives protocol patches independently.\n\nNo claim is made here that ε is required as a separate human or agent. ε is a structural role in the scope-escalation ladder ([`ROLES.md §1`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#1-the-role-ladder)), not a headcount requirement. The role may collapse onto δ indefinitely in small-protocol regimes; the obligation is that ε work happens and is attributed, not that it is performed by a distinct person.\n\nSee [`ROLES.md §4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4-hats-vs-actors-roles-as-behavioral-contracts) for the general principle governing role collapse rules, and [`CDR.md §\"Field 6\"`](..\u002FCDR.md) for CDR's specific collapse rule — note that the α=β collapse is **never** safe for research-claim cycles (overclaim is the precise failure mode α cannot self-detect), while ε=δ and γ=δ are conditionally permitted.\n\n## §3 Persona \u002F protocol \u002F project boundary\n\nThis overlay declares **what research ε does at the protocol layer**. It does not declare:\n\n- **Who enacts ε** (persona — layer 1; lives in `\u003Cpersona-hub>\u002Fspec\u002F`).\n- **What concrete iteration-INDEX path or wave directory ε writes to** (project — layer 4; lives in `\u003Cproject>\u002F.cdr\u002F`). The trigger classes are protocol-bound (`cdr-*-gap` enumerated above); the storage path is project-bound.\n\nIf a project chooses additional trigger classes (e.g. `cdr-ethics-gap` for waves whose data raises ethics-review issues, or `cdr-stats-gap` for statistical-method drift), those are project-binding extensions; this overlay declares the minimum set per `CDR.md §\"Field 5\"`.\n",{"name":5,"scope":36,"inputs":37,"parent":40,"outputs":41,"triggers":43,"description":7,"kata_surface":30,"artifact_class":46,"governing_question":47},"role-local",[38,39],"the CDR receipt stream","research-protocol-gap findings","cdr",[42],"a CDR-iteration artifact recording durable protocol improvements under MCA discipline",[5,44,45],"cdr-iteration","protocol-iteration","skill","How does ε turn research-protocol-gap findings from the receipt stream into durable CDR-protocol improvements without accumulating undeclared overclaim risk?","main","fb527e6c4bfb75c71fa75d6471b3aa3da32106d4","src\u002Fpackages\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add usurobor\u002Fcnos --skill epsilon",{"tool":62,"command":63},"bunx","bunx skills add usurobor\u002Fcnos --skill epsilon",{"tool":65,"command":66},"pnpm","pnpm dlx skills add usurobor\u002Fcnos --skill epsilon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fcheck_inbox.py","SCRIPT","脚本",1379,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fhot-skills\u002Fskills\u002Fagent-mail\u002Fscripts\u002Fcheck_inbox.py",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fsend_email.py",1537,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fhot-skills\u002Fskills\u002Fagent-mail\u002Fscripts\u002Fsend_email.py",[81,99,114,140,157,177],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":31},"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",[],[88,89,90,91,92,28,93,94,95,96,97,98],"triage","issues","issues triage","issue triage","SET","decision","public","use","dispatch","issue","doctrine",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":31},"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",[],[89,106,107,108,109,25,92,110,94,111,95,96,112,97,113],"taxonomy","issues taxonomy","github","status","open","board","github issue","issue labels",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":128,"publishedAt":31},"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",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[89,129,108,130,131,132,92,133,106,110,28,134,135,111,136,137,138,139,95,97],"issues map","reasoning","data","pipeline","api","json","README","edit","interactive","fetch","generated",{"skillNo":141,"name":89,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":31},"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",[],[89,108,146,147,148,149,150,151,152,106,110,28,93,153,135,154,95,155,96,156],"pr","current state","run","artifacts","state","package","boundary","branch","command","only","cds",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":31},"01M6CF896XKSRQVB1CSHY8GSXB","receipt-stream","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",[],[164,165,149,25,166,28,167,168,169,94,170,171,172,173,95,30,174,175,176,98],"receipt stream","handoff","index","learning","format","trace","repo","closeout","read","channel","patch","shape","cdd",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":31},"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",[],[184,108,185,186,187,188,28,189,190,153,170,172,95,155,96,191,112,192,193,194],"mid flight","change","sessions","file","cache","pin","coordination","up","Legacy","gamma","artifact channel"]