docs: strengthen ADR governance and implement design pack

[dapi]

What changed

• strengthen the generic ADR template with separate publication/decision statuses, MADR-aligned structure, E.C.A.D.R. quality criteria, Confirmation planning, revisit conditions, and downstream ownership handoff;
• accept project ADR-001 defining design layer, documentary design pack, root design.md, aggregate/direct ownership, and the root / constituent / derived-view / external-dependency relations;
• implement the decision in generic and project-local Feature Flow, artifact catalog, design/contract/brief/plan/support templates, testing policy, and glossary;
• make Solution Ready, Plan Ready, Execution, and implementation review validate the complete design pack and referenced external dependencies, including non-document assets;
• synchronize the project-local managed-file lock with the final template revisions.

Why

The previous guidance sometimes treated design.md as the sole owner even when canonical contract facts were delegated, and later lifecycle gates revalidated only the root document. The implemented model keeps one aggregate solution-space package while preserving one direct canonical owner per stable ID and explicit readiness for every dependency.

Impact

ADR-001 is now status: active / decision_status: accepted. The glossary and living governance rules use the same terminology and manifest schema. Additional design artifacts remain conditional; compact features can still use only root design.md.

Validation

• independent codex review --base main: clean verdict;
• memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md;
• memory-bank-cli lint --scope-root memory-bank --entrypoint memory-bank/README.md;
• memory-bank-cli doctor --profile template: 0 errors, 0 warnings;
• memory-bank-cli doctor: 0 errors, 0 warnings;
• E.C.A.D.R. completeness review with no unresolved [INVESTIGATE: ...] markers;
• git diff --check main...HEAD.