AXP Magisk resurrection track: Speckit 009 port AXP/LOS22 to LOS23.

Ship Magisk like GOLDEN; KernelSU optional recycle only; parallel to sunfish-a16-rom standby.

specs/007-kernelsu-sunfish/checklists/requirements.md

@@ -0,0 +1,41 @@
+# Specification Quality Checklist: KernelSU-Next on sunfish (LAB)
+
+**Purpose**: Validate specification completeness and quality before planning  
+**Created**: 2026-09-15  
+**Feature**: [spec.md](../spec.md)
+
+## Content Quality
+
+- [x] No implementation details (languages, frameworks, APIs)
+- [x] Focused on user value and business needs
+- [x] Written for non-technical stakeholders
+- [x] All mandatory sections completed
+
+## Requirement Completeness
+
+- [x] No [NEEDS CLARIFICATION] markers remain
+- [x] Requirements are testable and unambiguous
+- [x] Success criteria are measurable
+- [x] Success criteria are technology-agnostic (no implementation details)
+- [x] All acceptance scenarios are defined
+- [x] Edge cases are identified
+- [x] Scope is clearly bounded
+- [x] Dependencies and assumptions identified
+
+## Feature Readiness
+
+- [x] All functional requirements have clear acceptance criteria
+- [x] User scenarios cover primary flows
+- [x] Feature meets measurable outcomes defined in Success Criteria
+- [x] No implementation details leak into specification
+
+## Notes
+
+- Product names required by constitution (KernelSU-Next, SusFS, Magisk-as-non-default,
+  TrickyStore-class *experiment*) appear as **capability choices**, not code design.
+- Checklist item “non-technical stakeholders”: banking PASS/FAIL and LAB-only
+  constraints are written for the owner; kernel revision pinning is an audit need.
+- SC-002 “≥95% checklist rows” assumes a concrete verification checklist in
+  `/speckit-plan` / tasks — acceptable at specify stage.
+- Ready for `/speckit-plan`. **Yuh PASS is a hard-gate** (owner 2026-09-15):
+  without it, root is not justified vs NeoBackup + native call-rec / FLAG_SECURE.