agent-workflow-memorylisted

# agent-workflow-memory Deploys a **portable AI-agent memory substrate** into a project, and upgrades it as the substrate evolves. After it runs, any future agent (including a fresh session of yourself) can reconstruct project context in ~60 seconds, find the current task, and avoid repeating past mistakes. The substrate is **stack-agnostic memory** — `docs/ai/` structure, entry-point doc, session protocols, frontmatter caps, one-file-per-ADR archive, index-freshness gate. Enforcement ships as **Node `.mjs` scripts** (the reference implementation; non-Node stacks follow the same policy manually). This skill is the **memory layer** of the `agent-workflow` family. It **knows nobody else** in the family. In particular it does **not** own the **workflow methodology** (plan → execute → review vocabulary, lifecycle, `docs/plans/queue.md`, mandatory Cleanup, plan-then-execute) **or the orchestration recipes** — those are injected into **two delimited pointer slots** in `AGENTS.md` (`workflow:methodology` + `workflow:orchestration`) by the family **composition root**, never by this skill. (This substrate does not name or depend on any specific sibling — it only honours the slot contract.) This skill only ever ships **both** slots **empty** and **preserves** whatever is already in them on upgrade. The substrate **artifacts** (this skill, the templates, the deployed `docs/ai/` files) stay in their **source language** — for cross-agent and cross-team portability. That is separate fr