@haposoft/cafekit 0.18.0 → 0.18.1

package/src/claude/skills/code-review/references/verification-gate.md

@@ -1,41 +0,0 @@
----
-name: verification-gate
-description: Legacy proof consumption. Defines what supplied execution proof contains when a review of a legacy packet consumes it; the reviewer never produces that proof.
----
-
-# Verification Gate: legacy proof consumption
-
-This reference applies only to a legacy packet. A
-review never runs tests, builds, or linters to produce proof; `cf:test` owns
-execution, and the test-run boundary in `SKILL.md` applies here as well.
-
-## 1. What supplied proof contains
-
-Proof reaches the review from the test owner, never from the review itself. It
-may be:
-
-- **Test suite logs:** output showing which tests ran and their result.
-- **Compilation or build status:** compiler or bundler output with its exit code.
-- **Linter completion:** output showing the lint run and its result.
-- **Multimodal visual evidence:** `cf:ai-multimodal` when installed, or another
-  available runtime visual capability; otherwise visual parity is `UNPROVEN`.
-
-For Specs v2, accepted proof must be persisted by the test owner at
-`receipts/<task-basename>.md`; legacy `## Evidence` remains fallback-only. The
-receipt includes identity/path, exact command, exit/result, expected versus
-observed behavior, applicable negative/reachability/artifact proof, and bound
-Base/Head. Closing a legacy `spec.json` packet that has no `schema_version` still
-requires `feature-receipt.md`. A receipt never grants approval, readiness, audit
-status, or product semantics.
-
-For v2.1, the semantic receipt is reviewed input, not execution proof. It binds
-exact criteria and counterexamples shaped as `criterion`, `case_kind`,
-`scenario`, `expected`, `decision_refs`, and `verification_ref`. Deterministic
-validator success is never a semantic-review verdict.
-
-## 2. When supplied proof is missing or failed
-
-A missing legacy receipt leaves the closeout unfinished: the review still
-returns its correctness verdict and states execution proof as unavailable (owned
-by `cf:test`). Supplied proof that failed is a finding the review reports. Never
-rerun or retry anything to fill the gap.

package/src/claude/skills/specs/templates/design.md

@@ -1,82 +0,0 @@
-# Design
-
-<!-- Delete every optional section that is not relevant. Compact keeps only the four core sections. -->
-
-## Boundary
-
-- **Owns:** {{Behavior/state this design owns}}
-- **Reads:** {{Relevant inputs or existing state, or none}}
-- **Writes/exposes:** {{Outputs, state, route, artifact, or none}}
-- **Outside boundary:** {{Explicit non-goal or delegated responsibility}}
-
-## Typed Anchors
-
-<!-- Files-first. IDs are unique across the whole spec. Design-owned anchors use A-D-NN. Access/Action are machine authority; Role never implies lifecycle. -->
-
-| ID | Type | Target | Role | Access | Action |
-|---|---|---|---|---|---|
-| A-D-01 | file | `{{path/to/existing-or-planned-file}}` | {{owner / consumer / entrypoint / proof / constraint}} | {{read / write}} | {{read / create / modify / delete}} |
-<!-- For a typed proof boundary, add: | A-D-02 | artifact | `{{path/to/proof-artifact}}` | proof evidence owner | write | create | -->
-
-## Decisions and Invariants
-
-<!-- Keep stable D/I/C IDs: every RN.M semantic-review counterexample cites one exact design reference. -->
-
-### D1 — {{Decision name}}
-
-- **Decision:** {{Canonical behavior or boundary}}
-- **Rejects ambiguity:** {{Alternative interpretation implementers must not choose}}
-- **Negative path:** {{Failure/error behavior when relevant}}
-- **Anchors:** A-D-01
-
-### I1 — {{Invariant name}}
-
-{{Property that must remain true across implementation and verification.}}
-
-### Named Contracts (conditional)
-
-<!-- Define each implementation-significant contract once. Tasks reference IDs and never copy bodies. For any public, replay, or operator API contract, include method, route, auth, required headers, request schema, success response, error semantics, and idempotency/concurrency behavior. -->
-
-#### C1 — {{Contract name}}
-
-- **Owner:** {{boundary or future owner task}}
-- **Consumers:** {{boundaries or future consumer tasks}}
-- **Shape/behavior:** {{typed request, response, event, schema, state, or error contract}}
-- **Compatibility:** {{versioning or migration constraint when relevant}}
-
-## Verification Definitions
-
-<!--
-Canonical parser syntax is one single-line definition per V ID. Keep every
-label on the same line; do not replace this with a table or a V heading.
--->
-
-- **V1**: Criteria R{{SUBJECT_REQ}}.{{X}}; Owner A-D-01; Decision refs D1, I1, C1; Method command `{{exact command}}`; Expected {{concrete observable result}}; Negative/failure {{concrete rejected or recovery case}}; Reachability/grounding entrypoint `{{exact/repository/entrypoint}}` via A-D-01.
-
-<!-- Only for a typed proof boundary, insert after Owner: Proof criteria Rn.m; Proof owner <distinct owner>; Evidence anchor <proof-owned anchor>; -->
-
-<!-- Full-only conditional sections follow. Keep only those relevant to this feature. -->
-
-## Flow (Full, conditional)
-
-{{Only multi-step, branching, asynchronous, or cross-boundary flow decisions.}}
-
-## Data and Consistency (Full, conditional)
-
-{{Ownership, schema, constraints, concurrency, lifecycle, or idempotency. For any retention/lifecycle policy, state clock anchor, clock source, timezone/precision, cutoff comparator/inclusivity, enforcement boundary, and a wrong-clock/boundary counterexample.}}
-
-## Errors and Recovery (Full, conditional)
-
-{{Trigger, error contract, retry/rollback/reconciliation, and terminal state.}}
-
-## Security and Privacy (Full, conditional)
-
-{{Trust boundary, authorization, sensitive data, deletion, and retention decisions.}}
-
-## Migration and Compatibility (Full, conditional)
-
-{{Ordering, compatibility window, rollback trigger, and migration proof.}}
-
-## Unresolved Questions
-
-- None.

package/src/claude/skills/specs/templates/requirements-init.md

@@ -1,8 +0,0 @@
-# Requirements Document
-
-## Project Description (Input)
-{{PROJECT_DESCRIPTION}}
-
-## Requirements
-<!-- Will be generated during the cf:specs requirements phase -->
-

package/src/claude/skills/specs/templates/requirements.md

@@ -1,42 +0,0 @@
-# Requirements
-
-## Outcomes
-
-- {{Observable product or system outcome}}
-
-## Scope
-
-### In scope
-
-- {{Approved behavior or boundary}}
-
-### Non-goals
-
-- {{Explicit exclusion that prevents scope inference}}
-
-## Requirements
-
-### Requirement 1: {{Outcome area}}
-
-<!-- Keep Objective/User Story only when role and benefit remove ambiguity. -->
-{{Optional: **Objective:** As a <role>, I want <capability>, so that <benefit>.}}
-
-#### Acceptance Criteria
-
-- **R1.1** When {{event}}, the {{system}} shall {{measurable subject response}}.
-
-<!-- Add a separate proof criterion only when a typed proof boundary exists. -->
-
-<!-- Add state, optional-feature, or ubiquitous EARS criteria only when relevant. -->
-<!-- Add a concrete example only when values, order, boundaries, or transformation could be interpreted differently. -->
-
-#### Examples (conditional)
-
-- {{Input/state}} → {{expected output/state}}
-
-<!-- Repeat Requirement N with literal RN.M acceptance IDs. -->
-<!-- Add feature-specific NFRs in the same numeric sequence only when measurable and relevant. -->
-
-## Unresolved Questions
-
-- None.

package/src/claude/skills/specs/templates/spec-state.json

@@ -1,56 +0,0 @@
-{
-  "schema_version": "2.1",
-  "feature_name": "{{FEATURE_NAME}}",
-  "created_at": "{{TIMESTAMP}}",
-  "updated_at": "{{TIMESTAMP}}",
-  "language": "en",
-  "status": "in_progress",
-  "scope_lock": {
-    "source": "{{PROJECT_DESCRIPTION}}",
-    "in_scope": [],
-    "out_of_scope": [],
-    "expansion_policy": "requires-user-approval"
-  },
-  "authoring": {
-    "requirements": "draft",
-    "design": "draft",
-    "research": "absent",
-    "tasks": "absent"
-  },
-  "coordination": {
-    "boundaries": []
-  },
-  "validation": {
-    "status": "not-run",
-    "semantic_review": {
-      "status": "not-run",
-      "semantic_digest": null,
-      "verdict": null,
-      "lifecycle_disposition": null,
-      "findings": [],
-      "unresolved_decisions": [],
-      "graph_coverage": [],
-      "repair_round": 0,
-      "reviewed_criteria": [],
-      "counterexamples": [],
-      "reviewer_evidence": null
-    },
-    "semantic_review_history": {
-      "lineage_id": "{{LINEAGE_ID}}",
-      "entries": []
-    },
-    "authoring_validation": null
-  },
-  "semantic_model": null,
-  "ready_for_implementation": false,
-  "workflow_policy": {
-    "version": "2.1",
-    "planning_depth": "Compact",
-    "assurance_level": "Routine",
-    "classified_minimum": {
-      "planning_depth": "Compact",
-      "assurance_level": "Routine"
-    },
-    "risks": []
-  }
-}

package/src/claude/skills/specs/templates/task.md

@@ -1,47 +0,0 @@
-# Task R{{REQ_NUMBER}}-{{SEQ}}: {{TITLE}}
-**Status:** pending
-
-## Outcome
-
-{{Concrete observable vertical outcome, named entrypoint, and resulting state delivered by this task.}}
-
-## Scope
-
-- **In scope:** {{Exact behavior owned by this task}}
-- **Out of scope:** {{Explicit exclusions or delegated behavior}}
-
-## Anchors and Ownership
-
-<!-- Compact core: one owned anchor is enough; proof artifact/owner exists only for a typed proof boundary (see Verification Plan). -->
-| ID | Type | Target | Role | Access | Action |
-|---|---|---|---|---|---|
-| A-R{{REQ_NUMBER}}-{{SEQ}}-01 | file | `{{exact/path/to/file}}` | owner | write | modify |
-<!-- For a typed proof boundary, add: | A-R{{REQ_NUMBER}}-{{SEQ}}-02 | file | `{{exact/path/to/test-file}}` | proof | write | create | and set Task role accordingly; otherwise omit. Every executable task must own a concrete test file/artifact anchor or share proof via that typed boundary; bare command is not ownership. -->
-
-## Changes
-
-<!-- Every checkbox maps exact RN.M IDs; the set must equal Acceptance below. -->
-- [ ] {{Implement behavior at the exact owned boundary.}} _Requirements: {{REQ_NUMBER}}.{{X}}_
-- [ ] {{Handle the concrete negative or recovery path.}} _Requirements: {{REQ_NUMBER}}.{{Y}}_
-
-## Acceptance
-
-<!-- Declare each mapped RN.M once with a measurable output/state and negative behavior. -->
-- **R{{REQ_NUMBER}}.{{X}}:** {{Measurable observable outcome}}
-- **R{{REQ_NUMBER}}.{{Y}}:** {{Concrete negative or recovery outcome}}
-
-## Dependencies
-
-- {{DEPENDENCIES}}
-
-## Verification Plan
-
-<!-- Ownership invariant: a bare npm test command without a concrete file/artifact anchor is not ownership; shared proof must use a typed proof boundary. -->
-- **Verification ref:** {{V reference whose structured subject/proof owner matches this task}}
-- **Task role:** {{subject | verifier}}
-- **Command:** `{{Exact project command}}`
-- **Expected:** {{Exit, output, state, artifact, or UI result}}
-- **Negative path:** {{Contract-preserving failure check}}
-- **Reachability:** `{{Real entrypoint/caller or generated artifact}}`
-
-<!-- The table above is the only task anchor/ownership table. Access read requires Action read. Access write requires create, modify, or delete. Targets are exact; globs and parent-directory claims are invalid. A verifier must not repeat the subject's Acceptance criterion. Specs-only never creates or updates docs and never fabricates execution proof; record doc impact as a brief recommendation only. -->