# META — Known Issues (workspace meta-tooling)

For planned/actionable work see `META_TODO.md`.

Active issues for the workspace meta-tooling itself: protocol stack, skills, registry conventions, `.github/` files. Distinct from code-domain topics (LOG, BIN, SIG, etc.) which track code/feature concerns.

## In scope

- Skill correctness or coverage gaps (`docs-discovery`, `docs-check`, `protocol-audit`, `adr-author`, `docs-archive`)
- Registry / convention drift (`REPO_PREFIXES.md`, `TOPIC_CODES.md`, `protocol-audit/references/REPOS.md`)
- Protocol-stack inconsistencies (Rule #1-6 wording, `@repo` block format, ID-format edge cases)
- `.github/` infrastructure issues (folder structure, file naming conventions, generation rules)
- ADR / Decision Log governance issues (e.g., `Current protocol state` summary staleness)

## Out of scope

- Code-domain issues (those go to `LOG_ISSUES.md`, `BIN_ISSUES.md`, etc.)
- One-off historical events — those go to `LLM_PROTOCOL_DECISIONS.md` as decisions
- Forward-looking work that has been formally decided — that's a TODO (`META_TODO.md`) not an issue

## Active entries

*(No `ACCORE-META-I-*` entries yet — file just created (LLMP-DEC-62). Add the first entry below as concrete issues are observed.)*

## Issue entry template

```
## ACCORE-META-I-XXXX: Short title

**Severity:** Trivial / Low / Minor / Major / Critical · **Status:** Open / InProgress / Closed (YYYY-MM-DD) · **Area:** <skill / registry / convention name>

### Description
What's broken or inconsistent in the meta-tooling, with quotable evidence (file path + line number, or skill behaviour).

### Root cause
Why it's like that.

### Fix direction
Proposed approach.

### Resolution
(Filled when Status moves to `Closed` — what / where / why per `TOPIC_CODES.md` Status conventions.)

### Related
- Sibling: `META_TODO.md#accore-meta-t-xxxx` (if applicable)
- Cross-topic: `<other-topic>_ISSUES.md#accore-...` (if domain-spillover)
- LLMP-DEC: `LLMP-DEC-N` (if a decision documents the resolution)
```
