chore(learning): ADR-014 knownFlags mechanism retired without ledger amendment

[dean0x]

Problem

ADR-014 ("knownFlags-snapshot mechanism") recorded an architectural decision about how the manifest stores feature flags. That mechanism was superseded by the FlagsRecord key-presence approach in PR #300 (feat/flags-typed-registry).

The decisions ledger still describes the retired mechanism, which misleads future developers consulting ADR-014.

Current Status

• Pre-existing mechanism: knownFlags-snapshot field in manifest
• New superseding mechanism: FlagsRecord key-presence (adopted in PR feat(flags): typed flag registry, settings-page TUI, new upstream flags #300)
• Ledger state: ADR-014 entry remains unchanged, still describes the old mechanism
• Impact: decisions.md renders from the ledger and continues to describe the retired approach

Implementation Constraint

This is a Learning-pipeline task, not a Code-agent edit:

• decisions.md is a rendered artifact generated from .devflow/learning/decisions-ledger.jsonl
• Direct edits to decisions.md are overwritten on the next Learning agent run
• Only the Learning agent can amend or retire the ADR via the retire-anchor or assign-anchor ledger operations (per LLM-vs-plumbing principle)

Solution

Route this work through the Learning agent:

1. Add an observation to the learning queue indicating that ADR-014 is stale
2. The Learning agent should either:
   • Retire ADR-014 (if the old mechanism is fully obsolete and no longer applicable)
   • Amend ADR-014 (add a note explaining how FlagsRecord supersedes the old mechanism, and describe the new approach)
3. Re-render decisions.md via the Learning agent's render-decisions operation

Acceptance Criteria

• Learning agent reviewed ADR-014 against the new FlagsRecord mechanism
• ADR-014 updated (amended or retired) to reflect current architecture
• decisions.md re-rendered from the amended ledger
• Future readers of decisions.md see the current mechanism, not the retired one
• Decision recorded as a Learning agent amendment with timestamp

Related

• PR feat(flags): typed flag registry, settings-page TUI, new upstream flags #300 (feat/flags-typed-registry) — introduces FlagsRecord
• Source: architecture.md suggestion, 2026-08-25
• Reference: .devflow/learning/decisions-ledger.jsonl (source of truth)
• Reference: .devflow/learning/decisions.md (rendered output)