known-issues-formatlisted

# Thin-Index Ledger Format **Purpose:** the single source of truth for the **format** of this framework's two hand-maintained **thin-index ledgers** — an index file whose every entry is one pointer line to its own record file: | | **Defects** | **Work-items** | |---|---|---| | Index | `docs/KNOWN_ISSUES.md` | `docs/BACKLOG.md` | | Records | `docs/issues/<slug>.md` | `docs/backlog/<slug>.md` | | Holds | reproducible wrong behavior | enhancement / polish / signal, no broken contract | | Read by | Analysis phase (avoid repeating bugs), `/heal-issues` | Planning phase, humans ranking work | | Written by | `run-feedback file --as defect` | `run-feedback file --as work-item` | `artifact-management` owns the *lifecycle* of both (living Global Artifacts, never archived, create-if-absent) and **delegates the format to this skill** — mirroring how it delegates `ARCHITECTURE.md` structure to `architecture-format-core`. > **On the name.** This skill began as the `KNOWN_ISSUES.md` contract and kept its name when the > backlog joined it (four repositories symlink this directory by name). One skill, because the > mechanics are one thing said once: two near-identical format contracts are exactly the drift that > produced the defect this generalization fixed (`run-feedback`'s two filing paths diverged ��� the > defect path wrote index + record, the work-item path inlined the whole body into the index). ## Execution Mode - **Mode:** hybrid — a prompt-first format contract, plus one mainte