@ai-content-space/loopx 0.2.4 → 0.2.7

package/docs/loopx/memory/2026-06-09-stale-archive-hook-guidance.md

@@ -0,0 +1,15 @@
+# Stale Archive Hook Guidance
+
+Type: pitfall
+Domain: workflow hooks
+Date: 2026-06-09
+
+When removing a public workflow command, update generated guidance and also filter persisted runtime guidance. Old `.loopx/workflows/*/state.json` files can keep `recommended_next_action` text that outlives the current product flow.
+
+Evidence from `5285f99..1f11966`:
+
+- `scripts/codex-workflow-hook.mjs` and `scripts/claude-workflow-hook.mjs` now suppress stale `loopx archive` and `$archive` recommendations.
+- Done/archive/completed stale archive recommendations map to `$finish`.
+- Approved review stale archive recommendations map to `loopx approve <slug> --from review --to done`.
+- `test/trellis-hardening.test.mjs` covers both stale done and stale approved-review hook states.
+

package/docs/loopx/memory/README.md

@@ -0,0 +1,25 @@
+# Shared Memory
+
+`docs/loopx/memory/` is git-tracked shared memory for lightweight project knowledge that should follow a user across machines, but is not stable enough to become a spec.
+
+Use shared memory for concise, evidence-backed notes such as:
+
+- recurring project-specific pitfalls
+- agent handoff details that remain useful across sessions
+- personal or team working conventions that are not yet formal rules
+- context that helps avoid repeated investigation
+
+Do not use shared memory for:
+
+- temporary runtime state
+- raw conversation logs
+- secrets, credentials, or machine-local paths
+- stable workflow, API, migration, testing, or compatibility rules that belong in `docs/loopx/specs/`
+
+Memory layers:
+
+- `.loopx/memory/`: local memory, not tracked by git
+- `docs/loopx/memory/`: shared memory, tracked by git
+- `docs/loopx/specs/`: stable team rules, tracked by git
+
+Promote shared memory to `docs/loopx/specs/` when it becomes a durable rule that planning or review should depend on.