@esoteric-logic/praxis-harness 2.2.0 → 2.3.1

package/README.md

@@ -74,11 +74,14 @@ For technical research: `/discover` (structured options evaluation before decisi
 | `verify-app` | End-to-end verification with regression analysis |
 | `session-retro` | End-of-session retrospective with learnings extraction |
 | `status-update` | Manual vault status.md update |
+| `repair` | Structured 3-attempt fix-and-verify loop for failed milestones |
+| `sync-memory` | Bridge auto-memory insights to Obsidian vault |
+| `context-probe` | Assess context health and recommend action |
 | `context-reset` | Reload context from vault without clearing session |
 
 ## Rules
 
-15 rules across universal and scoped categories. Universal rules load every session. Scoped rules load only when matching file patterns are detected.
+16 rules across universal and scoped categories. Universal rules load every session. Scoped rules load only when matching file patterns are detected.
 
 Key additions in this version:
 - **context-management** — context brackets (FRESH/MODERATE/DEPLETED/CRITICAL) adapt behavior to session stage
@@ -113,6 +116,9 @@ Key additions in this version:
 |-----|----------|-------------|
 | web-designer | `/kit:web-designer` | Design system init → component build → accessibility audit → production lint |
 | infrastructure | `/kit:infrastructure` | Terraform plan → apply → drift detection → compliance check |
+| api | `/kit:api` | RESTful conventions → OpenAPI specs → contract testing |
+| security | `/kit:security` | Threat modeling → IAM review → OWASP audit |
+| data | `/kit:data` | Schema design → migration planning → query optimization |
 
 More kits coming. See `docs/creating-a-kit.md` to build your own.
 
@@ -205,6 +211,12 @@ bash install.sh
 
 The git-clone + `install.sh` path uses symlinks instead of copies, so edits in the repo are immediately reflected.
 
+**Testing:**
+```bash
+bash scripts/lint-harness.sh .     # structure, frontmatter, placeholders, registry
+bash scripts/test-harness.sh .     # shellcheck, JSON, cross-skill refs, hook wiring, kit structure
+```
+
 ## Requirements
 
 - macOS or Linux

package/base/CLAUDE.md

@@ -130,7 +130,7 @@ Kit manifests live in `~/.claude/kits/<name>/KIT.md`.
 
 ## Rules Registry — Load on Demand Only
 
-### Universal — always active (6 rules)
+### Universal — always active (7 rules)
 | File | Purpose |
 |------|---------|
 | `~/.claude/rules/profile.md` | Who the user is, identities, working style |
@@ -139,6 +139,7 @@ Kit manifests live in `~/.claude/kits/<name>/KIT.md`.
 | `~/.claude/rules/git-workflow.md` | Commits, branches, identity verification, pre-commit checks |
 | `~/.claude/rules/vault.md` | Second brain integration — vault backend, file purposes |
 | `~/.claude/rules/context-management.md` | Context anti-rot, phase scoping, context reset protocol |
+| `~/.claude/rules/memory-boundary.md` | Auto-memory boundary, MEMORY.md cap, dream integration |
 
 ### Scoped — load only when paths match
 | File | Loads when |

package/base/rules/context-management.md

@@ -82,6 +82,18 @@ ls -la {vault_path}/plans/
 stat -f "%Sm" {vault_path}/status.md
 ```
 
+## Memory Hygiene — Conventions (WARN on violation)
+
+### Before starting a new kit or major task
+1. Run `/dream` (if available) to consolidate stale auto-memory
+2. Run `/sync-memory` to bridge durable insights to Obsidian vault
+3. Proceed with clean, consolidated context
+
+### MEMORY.md cap
+- Keep under 80 lines. Auto-dream and `/sync-memory` enforce this.
+- If MEMORY.md exceeds 80 lines: run `/sync-memory` before continuing.
+- See `~/.claude/rules/memory-boundary.md` for full boundary rules.
+
 ---
 
 ## Removal Condition

package/base/rules/memory-boundary.md

@@ -0,0 +1,56 @@
+# Memory Boundary — Rules
+# Scope: All projects, all sessions
+# Defines what goes where across CLAUDE.md, MEMORY.md, and Obsidian vault
+
+## Invariants — BLOCK on violation
+
+### CLAUDE.md rules always win
+- If a MEMORY.md entry conflicts with a CLAUDE.md rule or base/ rule, the rule wins.
+- Never override architectural decisions, coding standards, or workflow sequences via auto-memory.
+- Auto-memory supplements rules — it does not replace them.
+
+### No architectural decisions in MEMORY.md
+- Architecture decisions, design patterns, and system constraints belong in CLAUDE.md or Obsidian vault specs/.
+- If Claude discovers a decision-worthy pattern during a session, surface it to the user for CLAUDE.md or vault — do not write it to MEMORY.md.
+
+### MEMORY.md cap
+- Keep MEMORY.md under 80 lines. Use topic files for overflow.
+- Prefer linking to Obsidian vault notes over expanding MEMORY.md.
+- If MEMORY.md exceeds 80 lines: run `/sync-memory` before continuing.
+- The 200-line hard limit means lines beyond 200 are silently dropped — the 80-line cap leaves headroom for topic file index entries.
+
+## Conventions — WARN on violation
+
+### What belongs where
+
+| Content | Destination | Managed by |
+|---------|-------------|------------|
+| Coding standards, workflows, architecture | `CLAUDE.md` / `base/rules/` | User (Praxis) |
+| Build quirks, CLI flags, error patterns | `MEMORY.md` | Claude (auto-memory + auto-dream) |
+| Architecture decisions, project status, session summaries | Obsidian vault | User (via Praxis skills) |
+| Kit configs, path-scoped rules | `kits/` and `base/rules/` | User (Praxis) |
+| Stale or conflicting memory entries | Deleted | Auto-dream consolidation or `/sync-memory` |
+
+### Auto-memory territory (appropriate for MEMORY.md)
+- Build commands and environment quirks Claude discovers
+- Debugging insights specific to this working tree
+- API gotchas, error patterns, CLI flags that worked
+- User preferences Claude infers from corrections
+- Tool configuration that varies per machine
+
+### Not auto-memory territory (redirect elsewhere)
+- Decisions that affect system design → CLAUDE.md or vault specs/
+- Cross-project learnings → vault notes/learnings.md
+- Session summaries → vault notes/ (auto-documented by Stop hook)
+- Task tracking → vault tasks.md
+- Plans and milestones → vault plans/
+
+### Dream and consolidation
+- Run `/dream` (if available) between sessions to consolidate stale memory
+- Run `/sync-memory` to bridge durable insights from MEMORY.md to Obsidian vault
+- Auto-dream fires automatically after 24h + 5 sessions — the memory-boundary rules guide what it keeps vs prunes
+- After `/dream` or auto-dream runs: verify MEMORY.md is under 80 lines
+
+## Removal Condition
+Remove when Claude Code provides native memory scoping that respects rule hierarchies
+and vault integration without manual boundary enforcement.

package/base/skills/sync-memory/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: sync-memory
+disable-model-invocation: true
+description: "Bridge auto-memory insights to Obsidian vault. Reads MEMORY.md and topic files, syncs durable entries to vault learnings, prunes stale content. Side-effect skill — never auto-triggers."
+---
+
+# sync-memory Skill
+
+You are syncing Claude's auto-memory to the Obsidian vault.
+
+## Vault Path Resolution
+Read vault_path from `~/.claude/praxis.config.json`.
+
+## Acceptance
+- [ ] MEMORY.md and topic files read
+- [ ] Durable insights synced to vault
+- [ ] Stale entries pruned
+- [ ] MEMORY.md under 80 lines after sync
+
+---
+
+**Step 1 — Locate memory files**
+- Find the auto-memory directory for the current project:
+  `~/.claude/projects/-{escaped-cwd}/memory/`
+- Read `MEMORY.md` (the index file)
+- Read all topic files referenced by MEMORY.md (e.g., `user_preferences.md`, `feedback_testing.md`)
+- If no memory files exist: "No auto-memory to sync." Exit.
+
+**Step 2 — Classify each entry**
+
+For each entry in MEMORY.md and topic files, classify:
+
+| Classification | Action |
+|---------------|--------|
+| **Project-specific insight** (error pattern, build quirk, API gotcha) | Append to `vault/notes/learnings.md` as `[LEARN:memory-sync]` |
+| **Global preference** (coding style, tool preference) | Present to user: "Add to CLAUDE.md Error Learning? [entry]" |
+| **Architecture decision** | Present to user: "This belongs in vault specs/ or CLAUDE.md — not MEMORY.md" |
+| **Already in vault** | Skip — note as duplicate |
+| **Stale/outdated** (references deleted files, old versions, resolved bugs) | Mark for pruning |
+| **Machine-specific** (paths, env vars, tool locations) | Keep in MEMORY.md — appropriate for auto-memory |
+
+**Step 3 — Sync to vault**
+
+For project-specific insights, append to `vault/notes/learnings.md`:
+```markdown
+## [LEARN:memory-sync] [short title]
+- **What**: [the insight]
+- **So What**: [why it matters]
+- **Now What**: [how to apply it]
+- **Date**: [YYYY-MM-DD]
+- **Source**: auto-memory sync
+```
+
+**Step 4 — Prune MEMORY.md**
+
+After syncing:
+1. Remove entries that were synced to vault (they now live in the canonical store)
+2. Remove stale/outdated entries
+3. Keep machine-specific and active debugging entries
+4. Verify MEMORY.md is under 80 lines
+5. If still over 80 lines: consolidate further — merge similar entries, shorten descriptions
+
+**Step 5 — Report**
+
+```
+MEMORY SYNC
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Synced:    [n] entries → vault learnings
+Surfaced:  [n] entries for CLAUDE.md review
+Pruned:    [n] stale entries removed
+Kept:      [n] entries in MEMORY.md
+Lines:     [n] / 80 limit
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Error Handling
+
+| Condition | Action |
+|-----------|--------|
+| No memory files found | Exit cleanly |
+| Vault path missing | Warn, skip vault sync, still prune |
+| MEMORY.md empty | "Nothing to sync." Exit. |
+| Cannot classify an entry | Keep it — don't prune what you don't understand |
+
+## When to Run
+
+- Before starting a new kit (`/kit:<name>`)
+- Before `/context-reset` or `/clear`
+- At session end (optional — Stop prompt handles most vault writes)
+- When MEMORY.md exceeds 80 lines
+
+## Removal Condition
+Remove when Claude Code provides native memory-to-vault sync or when
+auto-dream learns to respect vault integration boundaries natively.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@esoteric-logic/praxis-harness",
-  "version": "2.2.0",
+  "version": "2.3.1",
   "description": "Layered Claude Code harness — workflow discipline, AI-Kits, persistent vault integration",
   "bin": {
     "praxis-harness": "./bin/praxis.js"