@haposoft/cafekit 0.18.0 → 0.18.1

package/src/claude/skills/ui-ux-pro-max/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cf:ui-ux-pro-max
-description: "UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples."
+description: "Searchable UI/UX lookup database for web and mobile products: 50+ visual styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, 25 chart types, Google Fonts, and React Native stack guidance. Use to pick or justify a palette, font pairing, visual style, chart type, or UX guideline for a product type. It does not build, review, or redesign screens; that is cf:ui-ux, which can consult this skill for lookups."
 user-invocable: true
 when_to_use: "Invoke to look up color palettes, font pairings, product-type styles, or UX guidelines; to build or review a screen use cf:ui-ux."
 category: frontend
@@ -11,45 +11,13 @@ metadata:
 ---
 # UI/UX Pro Max - Design Intelligence
 
-Comprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations.
+Searchable design database for web and mobile products: 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, 25 chart types, and stack guidance for React Native only.
 
 ## When to Apply
 
-This Skill should be used when the task involves **UI structure, visual design decisions, interaction patterns, or user experience quality control**.
+Use this skill to look something up: a palette, font pairing, or visual style for a product type, a chart type, or the UX guideline that applies to a pattern.
 
-### Must Use
-
-This Skill must be invoked in the following situations:
-
-- Designing new pages (Landing Page, Dashboard, Admin, SaaS, Mobile App)
-- Creating or refactoring UI components (buttons, modals, forms, tables, charts, etc.)
-- Choosing color schemes, typography systems, spacing standards, or layout systems
-- Reviewing UI code for user experience, accessibility, or visual consistency
-- Implementing navigation structures, animations, or responsive behavior
-- Making product-level design decisions (style, information hierarchy, brand expression)
-- Improving perceived quality, clarity, or usability of interfaces
-
-### Recommended
-
-This Skill is recommended in the following situations:
-
-- UI looks "not professional enough" but the reason is unclear
-- Receiving feedback on usability or experience
-- Pre-launch UI quality optimization
-- Aligning cross-platform design (Web / iOS / Android)
-- Building design systems or reusable component libraries
-
-### Skip
-
-This Skill is not needed in the following situations:
-
-- Pure backend logic development
-- Only involving API or database design
-- Performance optimization unrelated to the interface
-- Infrastructure or DevOps work
-- Non-visual scripts or automation tasks
-
-**Decision criteria**: If the task will change how a feature **looks, feels, moves, or is interacted with**, this Skill should be used.
+Building, reviewing, or redesigning a screen belongs to `cf:ui-ux`, which follows the project's own components and measures the page; it can call this skill when it needs a lookup. Backend, API, infrastructure, and non-visual work need neither skill.
 
 ## Rule Categories by Priority
 
@@ -313,28 +281,7 @@ Search specific domains using the CLI tool below.
 
 ## Prerequisites
 
-Check if Python is installed:
-
-```bash
-python3 --version || python --version
-```
-
-If Python is not installed, install it based on user's OS:
-
-**macOS:**
-```bash
-brew install python3
-```
-
-**Ubuntu/Debian:**
-```bash
-sudo apt update && sudo apt install python3
-```
-
-**Windows:**
-```powershell
-winget install Python.Python.3.12
-```
+Run `search.py` from the project root with `python3 .claude/skills/ui-ux-pro-max/scripts/search.py` (Windows: `python .claude\skills\ui-ux-pro-max\scripts\search.py`). It uses only the Python standard library, so no venv or extra install is needed.
 
 ---
 
@@ -362,14 +309,14 @@ Extract key information from user request:
 - **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid
 - **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work)
 - **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc.
-- **Stack**: React Native (this project's only tech stack)
+- **Stack**: the target project's stack; `--stack` guidance exists only for `react-native`
 
-### Step 2: Generate Design System (REQUIRED)
+### Step 2: Generate Design System
 
-**Always start with `--design-system`** to get comprehensive recommendations with reasoning:
+Start with `--design-system` when choosing a whole direction (style, palette, type) for a new product or page; for a single lookup go straight to Step 3:
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
 ```
 
 This command:
@@ -380,7 +327,7 @@ This command:
 
 **Example:**
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
 ```
 
 ### Step 2b: Persist Design System (Master + Overrides Pattern)
@@ -388,7 +335,7 @@ python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --d
 To save the design system for **hierarchical retrieval across sessions**, add `--persist`:
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
 ```
 
 This creates:
@@ -397,7 +344,7 @@ This creates:
 
 **With page-specific override:**
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
 ```
 
 This also creates:
@@ -422,7 +369,7 @@ Now, generate the code...
 After getting the design system, use domain searches to get additional details:
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
 ```
 
 **When to use detailed searches:**
@@ -440,14 +387,13 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n
 | Landing structure | `landing` | `--domain landing "hero social-proof"` |
 | React Native perf | `react` | `--domain react "rerender memo list"` |
 | App interface a11y | `web` | `--domain web "accessibilityLabel touch safe-areas"` |
-| AI prompt / CSS keywords | `prompt` | `--domain prompt "minimalism"` |
 
-### Step 4: Stack Guidelines (React Native)
+### Step 4: Stack Guidelines (React Native projects only)
 
-Get React Native implementation-specific best practices:
+For a React Native project, get implementation-specific best practices:
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack react-native
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack react-native
 ```
 
 ---
@@ -468,7 +414,6 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack react-native
 | `google-fonts` | Individual Google Fonts lookup | sans serif, monospace, japanese, variable font, popular |
 | `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |
 | `web` | App interface guidelines (iOS/Android/React Native) | accessibilityLabel, touch targets, safe areas, Dynamic Type |
-| `prompt` | AI prompts, CSS keywords | (style name) |
 
 ### Available Stacks
 
@@ -488,10 +433,10 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack react-native
 - Style keywords: modern, minimal, content-first, dark mode
 - Stack: React Native
 
-### Step 2: Generate Design System (REQUIRED)
+### Step 2: Generate Design System
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "AI search tool modern minimal" --design-system -p "AI Search"
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "AI search tool modern minimal" --design-system -p "AI Search"
 ```
 
 **Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
@@ -500,16 +445,16 @@ python3 skills/ui-ux-pro-max/scripts/search.py "AI search tool modern minimal" -
 
 ```bash
 # Get style options for a modern tool product
-python3 skills/ui-ux-pro-max/scripts/search.py "minimalism dark mode" --domain style
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "minimalism dark mode" --domain style
 
 # Get UX best practices for search interaction and loading
-python3 skills/ui-ux-pro-max/scripts/search.py "search loading animation" --domain ux
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "search loading animation" --domain ux
 ```
 
 ### Step 4: Stack Guidelines
 
 ```bash
-python3 skills/ui-ux-pro-max/scripts/search.py "list performance navigation" --stack react-native
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "list performance navigation" --stack react-native
 ```
 
 **Then:** Synthesize design system + detailed searches and implement the design.
@@ -522,10 +467,10 @@ The `--design-system` flag supports two output formats:
 
 ```bash
 # ASCII box (default) - best for terminal display
-python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
 
 # Markdown - best for documentation
-python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
+python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
 ```
 
 ---
@@ -537,7 +482,7 @@ python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
 - Use **multi-dimensional keywords** — combine product + industry + tone + density: `"entertainment social vibrant content-dense"` not just `"app"`
 - Try different keywords for the same need: `"playful neon"` → `"vibrant dark"` → `"content-first minimal"`
 - Use `--design-system` first for full recommendations, then `--domain` to deep-dive any dimension you're unsure about
-- Always add `--stack react-native` for implementation-specific guidance
+- Add `--stack react-native` only when the target project is React Native
 
 ### Common Sticking Points
 

package/src/claude/skills/web-testing/SKILL.md

@@ -26,15 +26,9 @@ npx @axe-core/cli https://example.com  # Accessibility
 npx lighthouse https://example.com     # Performance
 ```
 
-## Testing Strategy (Choose Your Model)
+## Testing Strategy
 
-| Model | Structure | Best For |
-|-------|-----------|----------|
-| Pyramid | Unit 70% > Integration 20% > E2E 10% | Monoliths |
-| Trophy | Integration-heavy | Modern SPAs |
-| Honeycomb | Contract-centric | Microservices |
-
-→ `./references/testing-pyramid-strategy.md`
+Choosing between pyramid, trophy, and honeycomb: `./references/testing-pyramid-strategy.md`
 
 ## Reference Documentation
 
@@ -88,15 +82,3 @@ node ./scripts/analyze-test-results.js \
   --output markdown
 ```
 Parses Playwright/Vitest/JUnit results into unified summary.
-
-## CI/CD Integration
-
-```yaml
-jobs:
-  test:
-    steps:
-      - run: npm run test:unit      # Gate 1: Fast fail
-      - run: npm run test:e2e       # Gate 2: After unit pass
-      - run: npm run test:a11y      # Accessibility
-      - run: npx lhci autorun       # Performance
-```

package/src/codex/hooks/lib/spec-receipt.cjs

@@ -37,8 +37,8 @@ function loadSharedReceipt() {
     'spec-receipt.cjs',
     'spec-receipt.cjs',
     (receipt) => {
-      if (typeof receipt?.checkTaskReceipt !== 'function') {
-        throw new Error('shared spec receipt helper has no checkTaskReceipt function');
+      if (typeof receipt?.checkWorkflowTaskReceipt !== 'function') {
+        throw new Error('shared spec receipt helper has no checkWorkflowTaskReceipt function');
       }
     },
     'shared spec receipt helper is missing'
@@ -55,7 +55,6 @@ function receiptHelper() {
   return loaded.receipt;
 }
 
-function evidenceBody(text) { return receiptHelper().evidenceBody(text, getSharedPolicy() || {}); }
 function safeTaskFile(featureDir, taskPath) {
   const result = receiptHelper().safeRead(featureDir, taskPath);
   return result.status === 'ok' ? result.path : null;
@@ -64,11 +63,6 @@ function validateCanonicalReceipt(body, options = {}) {
   const validate = getSharedValidate();
   return validate ? validate(body, options) : ['shared_validator'];
 }
-function checkReceiptDetails(featureDir, taskPath, task, runtimeContext) {
-  const policy = getSharedPolicy();
-  if (!policy) return { failures: ['shared_validator'], status: 'missing' };
-  return receiptHelper().checkTaskReceipt(featureDir, taskPath, task, runtimeContext, policy);
-}
 function checkWorkflowReceiptDetails(featureDir, taskPath, runtimeContext) {
   const policy = getSharedPolicy();
   const receipt = receiptHelper();
@@ -85,40 +79,18 @@ function checkWorkflowReceiptSet(candidates, projectRoot, runtimeSession) {
   }
   return receipt.checkWorkflowReceiptSet(candidates, projectRoot, runtimeSession, policy);
 }
-function checkReceipt(featureDir, taskPath, task, runtimeContext) {
-  const map = {
-    unsafe_path: 'a', missing_receipt: 'b', task_status: 'a', completed_at: 'd',
-    verification_state: 'c', placeholder: 'c', validator_unavailable: 'c',
-    command: 'e', command_identity: 'e', exit_result: 'f', provenance: 'g',
-    artifact_hash: 'h', artifact_declaration: 'h',
-  };
-  return [...new Set(checkReceiptDetails(featureDir, taskPath, task, runtimeContext).failures.map((failure) => map[failure] || failure))];
-}
-function checkFeatureReceipt(featureDir, runtimeContext) {
-  const policy = getSharedPolicy();
-  if (!policy) return { failures: ['shared_validator'], status: 'missing' };
-  return receiptHelper().checkFeatureReceipt(featureDir, runtimeContext, policy);
-}
 function receiptFixHint(failures, body) {
   const helper = receiptHelper();
   return typeof helper.receiptFixHint === 'function' ? helper.receiptFixHint(failures, body) : null;
 }
-function readTaskProof(featureDir, taskPath) {
-  return receiptHelper().readTaskProof(featureDir, taskPath, getSharedPolicy() || {});
-}
 
 module.exports = {
-  checkFeatureReceipt,
-  checkReceipt,
-  checkReceiptDetails,
   checkWorkflowReceiptDetails,
   checkWorkflowReceiptSet,
-  evidenceBody,
   getSharedPolicy,
   getSharedValidate,
   loadSharedPolicy,
   loadSharedReceipt,
-  readTaskProof,
   receiptFixHint,
   safeTaskFile,
   validateCanonicalReceipt,

package/src/codex/hooks/lib/spec-utils.cjs

@@ -66,8 +66,8 @@ function sharedResolver() {
     // Use canonical realpath for require to avoid symlink hijack
     const realCandidate = canonicalRealpath(candidate);
     const resolver = require(realCandidate);
-    if (typeof resolver?.resolveActiveSpec !== 'function') {
-      throw new Error('shared spec resolver has no resolveActiveSpec function');
+    if (typeof resolver?.resolveWorkflowCandidate !== 'function') {
+      throw new Error('shared spec resolver has no resolveWorkflowCandidate function');
     }
     return resolver;
   } catch (error) {
@@ -80,31 +80,13 @@ function specsDirectory(projectRoot, runtime) {
   return sharedResolver().specsDirectory(projectRoot, runtime);
 }
 
-function findAllActiveSpecs(projectRoot, runtime) {
-  return sharedResolver().findAllActiveSpecs(projectRoot, runtime);
-}
-
-function findAllSpecCandidates(projectRoot, runtime) {
-  return sharedResolver().findAllSpecCandidates(projectRoot, runtime);
-}
-
-function resolveActiveSpec(projectRoot, runtime, explicitFeature, explicitPath) {
-  if (projectRoot && typeof projectRoot === 'object') {
-    return sharedResolver().resolveActiveSpec(projectRoot);
-  }
-  return sharedResolver().resolveActiveSpec({
-    projectRoot,
-    runtime,
-    explicitFeature,
-    explicitPath,
-  });
+function findLegacyPackets(projectRoot, runtime) {
+  const resolver = sharedResolver();
+  return typeof resolver.findLegacyPackets === 'function' ? resolver.findLegacyPackets(projectRoot, runtime) : [];
 }
 
 function resolveWorkflowCandidate(projectRoot, runtime, explicitFeature, explicitPath) {
   const resolver = sharedResolver();
-  if (typeof resolver.resolveWorkflowCandidate !== 'function') {
-    return resolveActiveSpec(projectRoot, runtime, explicitFeature, explicitPath);
-  }
   if (projectRoot && typeof projectRoot === 'object') {
     return resolver.resolveWorkflowCandidate(projectRoot);
   }
@@ -123,23 +105,6 @@ function refineWorkflowGateResolution(resolved) {
     : resolved;
 }
 
-function findActiveSpec(projectRoot, runtime) {
-  const resolved = resolveActiveSpec(projectRoot, runtime);
-  if (!resolved) return null;
-  if (resolved.error === 'multiple_active' || resolved.error === 'invalid_specs') return resolved;
-  if (resolved.error) return null;
-  return resolved;
-}
-
-function taskStatusMap(spec) {
-  return Object.fromEntries(
-    Object.entries(spec.task_registry || {}).map(([taskPath, task]) => [
-      taskPath,
-      task?.status || 'pending',
-    ]),
-  );
-}
-
 function extractExplicitTarget(...sources) {
   const resolver = sharedResolver();
   if (typeof resolver.extractExplicitTarget !== 'function') return null;
@@ -153,14 +118,10 @@ function readActiveFeatureTarget(options) {
 }
 
 module.exports = {
-  findActiveSpec,
   extractExplicitTarget,
+  findLegacyPackets,
   readActiveFeatureTarget,
-  findAllActiveSpecs,
-  findAllSpecCandidates,
-  resolveActiveSpec,
   resolveWorkflowCandidate,
   refineWorkflowGateResolution,
   specsDirectory,
-  taskStatusMap,
 };

package/src/codex/hooks/spec-gate.cjs

@@ -11,14 +11,11 @@ const {
   readPayload
 } = require('./lib/hook-context.cjs');
 const {
-  checkFeatureReceipt,
-  checkReceiptDetails,
   checkWorkflowReceiptDetails,
   checkWorkflowReceiptSet,
   loadSharedPolicy,
   receiptFixHint,
 } = require('./lib/spec-receipt.cjs');
-const { taskStatusMap } = require('./lib/spec-utils.cjs');
 
 function emitBlock(reason) {
   process.stdout.write(`${JSON.stringify({ decision: 'block', reason })}\n`);
@@ -45,7 +42,7 @@ try {
   }
   const POLICY = loaded.policy;
   const { projectRoot, runtime } = getHookContext(payload);
-  if (typeof POLICY.completionDecisionForSpec !== 'function') {
+  if (typeof POLICY.deriveRuntimeContext !== 'function') {
     throw new Error('shared workflow policy lacks completion authority functions');
   }
   const resolver = require('./lib/spec-utils.cjs');
@@ -88,7 +85,7 @@ try {
   if (resolved.error === 'invalid_specs') {
     process.stdout.write(`${JSON.stringify({
       decision: 'block',
-      reason: `Completion gate: invalid spec JSON detected (${resolved.candidates.join(', ')}): ${resolved.reason}. Fix or remove malformed spec.json before completing tasks.`
+      reason: `Completion gate: invalid workflow packet detected (${resolved.candidates.join(', ')}): ${resolved.reason}. Fix the packet's plan.md or task files before completing tasks.`
     })}\n`);
     process.exit(0);
   }
@@ -101,20 +98,10 @@ try {
   }
   if (resolved.error) process.exit(0);
   const active = resolved;
-  const activeSpec = active.spec || {};
-  const processWorkflow = active.layoutKind === 'process-v3';
-  const lifecyclePhase = activeSpec.current_phase || activeSpec.phase;
-  const explicitCloseout = ['done', 'completed', 'complete'].includes(activeSpec.status)
-    || ['closeout', 'completion', 'completed', 'complete'].includes(lifecyclePhase);
-  // Legacy 2.1 closeout is retired; a 2.1 packet mid-execution keeps the ordinary receipt checks.
-  if (!processWorkflow && activeSpec.schema_version === '2.1' && explicitCloseout) {
-    emitBlock('Completion gate: Legacy spec.json closeout is no longer supported; move the packet to plan.md with flat task files');
-    process.exit(0);
-  }
   const runtimeContext = POLICY.deriveRuntimeContext({
     projectRoot,
     specsRoot: active.specsDir,
-    specFile: active.stateFile || active.specFile || path.join(active.specsDir, active.featureName, 'spec.json'),
+    specFile: active.stateFile,
     featureName: active.featureName,
     runtimeSession: sessionIdentity(payload),
   });
@@ -123,10 +110,10 @@ try {
     emitBlock('Completion gate: runtime.spec.completion_gate is a worker-writable flag, not an authorization; no completion-gate bypass is supported. Remove the flag and satisfy the gate.');
     process.exit(0);
   }
-  const registry = active.taskRegistry || activeSpec.task_registry || {};
-  const currentStatuses = processWorkflow
-    ? Object.fromEntries(Object.entries(registry).map(([taskPath, task]) => [taskPath, task?.status || 'pending']))
-    : taskStatusMap(activeSpec);
+  const registry = active.taskRegistry || {};
+  const currentStatuses = Object.fromEntries(
+    Object.entries(registry).map(([taskPath, task]) => [taskPath, task?.status || 'pending']),
+  );
   const cacheFile = path.join(hookStateDir(projectRoot), 'spec-gate-last.json');
   const cacheExists = fs.existsSync(cacheFile);
   let cache = {};
@@ -152,16 +139,6 @@ try {
   const previous = cacheExists && cacheEntries[runtimeContext.context_id]
     ? cacheEntries[runtimeContext.context_id].tasks || {}
     : {};
-  const staleFlashTasks = processWorkflow ? [] : Object.entries(registry)
-    .filter(([, task]) => POLICY.isStaleFlashDone(task))
-    .map(([taskPath]) => taskPath);
-  if (staleFlashTasks.length > 0) {
-    process.stdout.write(`${JSON.stringify({
-      decision: 'block',
-      reason: `Completion gate: ${staleFlashTasks.length} task(s) marked done with FLASH_UNVERIFIED (${staleFlashTasks.join(', ')}). Run /cf:test, then use explicit sync-finalize.`
-    })}\n`);
-    process.exit(0);
-  }
   const allDoneTasks = Object.keys(registry).filter((taskPath) => (
     currentStatuses[taskPath] === 'done'
   ));
@@ -169,9 +146,7 @@ try {
   const receiptBodies = new Map();
   const failures = allDoneTasks
     .map((taskPath) => {
-      const proof = processWorkflow
-        ? checkWorkflowReceiptDetails(featureDir, taskPath, runtimeContext)
-        : checkReceiptDetails(featureDir, taskPath, registry[taskPath], runtimeContext);
+      const proof = checkWorkflowReceiptDetails(featureDir, taskPath, runtimeContext);
       if (proof.body) receiptBodies.set(taskPath, proof.body);
       return {
         taskPath,
@@ -180,52 +155,20 @@ try {
     })
     .filter((result) => result.failures.length);
 
-  const featureCloseoutRequired = !processWorkflow && explicitCloseout && allDoneTasks.length > 0;
-  const featureReceipt = featureCloseoutRequired
-    ? checkFeatureReceipt(featureDir, runtimeContext)
-    : null;
-  if (featureReceipt && featureReceipt.failures.length) {
-    failures.push({ taskPath: 'feature-receipt.md', failures: featureReceipt.failures });
-  }
-  const completion = featureCloseoutRequired && featureReceipt?.failures.length === 0
-    && Object.prototype.hasOwnProperty.call(active.spec, 'workflow_policy')
-    ? POLICY.completionDecisionForSpec(active.spec, {
-      runtimeContext,
-      executionReceipt: featureReceipt.body,
-      taskContext: {},
-    })
-    : null;
-
   const next = { ...previous, ...currentStatuses };
   for (const result of failures) {
     if (previous[result.taskPath] === undefined) delete next[result.taskPath];
     else next[result.taskPath] = previous[result.taskPath];
   }
   atomicWrite(cacheFile, `${JSON.stringify({
-    schema_version: '2',
     entries: { ...cacheEntries, [runtimeContext.context_id]: { identity: cacheIdentity, tasks: next } },
   })}\n`);
 
-  const completionBlocked = completion && completion.completion !== 'complete' && completion.completion !== 'not_applicable';
-  if (!failures.length && !completionBlocked) process.exit(0);
-  const lines = [
-    failures.length > 0
-      ? `Completion gate: ${failures.length} done task(s) lack a verification receipt.`
-      : 'Completion gate: workflow completion proof is incomplete.'
-  ];
+  if (!failures.length) process.exit(0);
+  const lines = [`Completion gate: ${failures.length} done task(s) lack a verification receipt.`];
   for (const result of failures) {
     lines.push(`- \`${result.taskPath}\`: failed check(s) ${result.failures.join(', ')}`);
-    lines.push(result.taskPath === 'feature-receipt.md'
-      ? `  Run final integration proof, then write \`specs/${active.featureName}/feature-receipt.md\`.`
-      : processWorkflow
-        ? `  In \`specs/${active.featureName}/${path.posix.basename(result.taskPath)}\`: ${receiptFixHint(result.failures, result.body) || 'write a runtime-bound `## Receipt` with command output'}.`
-        : `  Write canonical proof to \`specs/${active.featureName}/receipts/${path.posix.basename(result.taskPath)}\`; legacy \`## Evidence\` remains read-compatible.`);
-  }
-  if (completionBlocked) {
-    lines.push(`- Completion decision unfinished: ${completion.blocker || 'required workflow proof is missing.'}`);
-    if (Array.isArray(completion.missingProof) && completion.missingProof.length > 0) {
-      lines.push(`  Missing proof: ${completion.missingProof.join(', ')}`);
-    }
+    lines.push(`  In \`specs/${active.featureName}/${path.posix.basename(result.taskPath)}\`: ${receiptFixHint(result.failures, result.body) || 'write a runtime-bound `## Receipt` with command output'}.`);
   }
   process.stdout.write(`${JSON.stringify({
     decision: 'block',