@aperant/framework 0.6.7 → 0.7.3

package/templates/aperant-claude-md-appendix.md

@@ -0,0 +1,37 @@
+This project uses the [Aperant Framework](https://github.com/Mikalsen-AI/aperant-cloud-desktop/tree/main/packages/framework) for AI-assisted development.
+
+### Fast Path Guarantee (Pocock adoption ID-05)
+
+QUICK track is **hard-exempt** from PRD-shaped spec.md, HITL/AFK metadata,
+vertical-slice subtask schema, TDD iron law (`apt:execute --tdd`), triage
+prompts, and any new heavy interaction discipline. `apt:quick` and any
+task router-classified as QUICK run the existing one-shot pattern
+unchanged. This is a **constraint on every implementing change**, not a
+configuration toggle. Dedicated `*-quick-exempt.test.ts` regression tests
+in `packages/framework/src/__tests__/` enforce the exemption.
+
+### Discoverability — `apt-tools modes list`
+
+Power-user surface that enumerates every skill's `modes`, `flags`,
+`content_formats` (from optional `produces:` frontmatter), and
+`config_keys`. Adding a new skill auto-appears via filesystem scan
+without code changes. Mental-model builder for "what can the framework
+do?" without reading 30 SKILL.md files.
+
+### Feature Registry
+The feature registry (`.aperant/features/`) is a living inventory of every interactive
+feature in the app. It's the source of truth for what to verify and review.
+
+- **Created by:** `/apt:scan` (initial scan or full refresh)
+- **Updated by:** `/apt:execute` post-step (`apt-tools features-audit --apply-stubs` auto-registers new UI/core/hook/IPC files per the docs-coherence policy)
+- **Consumed by:** `/apt:verify-proof` (generates test cases from registry)
+- **Checked by:** `/apt:review` Pass 6 (flags unregistered new components, applies stubs for auto-update policies)
+
+Run `/apt:scan` after setting up Aperant on a brownfield project, or after major changes.
+
+### Config
+- Settings: `.aperant/config.json` (run `/apt:setup` to change)
+- Features: `.aperant/features/` (feature registry -- run `/apt:scan` to create)
+- State: `.aperant/state.json` (execution state)
+- Evidence: `.aperant/proof/` (proof reports and screenshots)
+- Prompts: `.aperant/prompts/` (agent prompt templates)

package/templates/config.json

@@ -39,7 +39,6 @@
 		"safe_paths": ["**/*.css", "**/*.md", "**/*.test.*", "**/*.spec.*"]
 	},
 	"verification": {
-		"open_report": true,
 		"report_formats": ["html", "md"],
 		"evidence_capture": true,
 		"max_iterations": 3,
@@ -47,8 +46,7 @@
 	},
 	"multi_model": {
 		"cross_verification": {
-			"enabled": false,
-			"tools": []
+			"enabled": false
 		},
 		"video_review": {
 			"enabled": false,
@@ -92,14 +90,11 @@
 		"cleanup_on_close": "ask"
 	},
 	"preferences": {
-		"date_format": "YY-MM-DD",
-		"time_format": "24h",
 		"task_index": true,
 		"health_check": {
 			"enabled": false,
 			"interval_minutes": 30
-		},
-		"quick_task_post_verify": "ask"
+		}
 	},
 	"orchestration": {
 		"phase_delegation": "auto",

package/workflows/verify-proof.md

@@ -21,10 +21,15 @@ OUTPUT FORMAT: verification.json (NOT VERIFICATION.md). JSON is the source of tr
 <step name="load_config" priority="first">
 ## 1. Load Config and Context
 
-Read `.aperant/config.json` for verification preferences:
+Read the merged Aperant config for verification preferences (AUDIT-001 — the per-device `verification.open_report` field lives in `.aperant/config.local.json`; the rest in shared `.aperant/config.json`). Use the framework's merged loader so local overrides win:
 ```bash
-cat .aperant/config.json 2>/dev/null || echo "{}"
+node .aperant/deps/node_modules/@aperant/framework/bin/apt-tools.mjs config read . 2>/dev/null || echo "{}"
 ```
+If `apt-tools config read` is unavailable, fall back to overlaying the two files in JS:
+```bash
+node -e "const fs=require('fs'); const s=(p)=>{try{return JSON.parse(fs.readFileSync(p,'utf-8'))}catch{return {}}}; function merge(a,b){if(a===null||typeof a!=='object'||Array.isArray(a))return b;if(b===null||typeof b!=='object'||Array.isArray(b))return b;const out={...a};for(const k of Object.keys(b))out[k]=(k in a)?merge(a[k],b[k]):b[k];return out}; const merged=merge(s('.aperant/config.json'),s('.aperant/config.local.json')); console.log(JSON.stringify(merged))"
+```
+Do NOT read `.aperant/config.json` directly — that misses per-device overrides like `verification.open_report` and `multi_model.cross_verification.tools`.
 
 Read project constitution:
 ```bash
@@ -396,7 +401,7 @@ ln -sf "${PROOF_DIR}/report.html" .aperant/proof-report.html
 <step name="open_report">
 ## 11. Open Report
 
-If `config.verification.open_report` is true (default):
+Read `verification.open_report` from the MERGED config (per-device override lives in `.aperant/config.local.json` per AUDIT-001; do not read raw `.aperant/config.json`). If true (default):
 ```bash
 open "${PROOF_DIR}/report.html"
 ```