Implement the approved Kiro SDD introduced by merged spec-only PR #557.
Spec: .kiro/specs/pre-oss-core-slimming/
Current implementation status
The production implementation and runtime verification are effectively complete on current main:
Authoritative Linux race run 33891386913 executed the exact required package scope against #591's merged main SHA and completed successfully. The #571 closeout comment also records generator/check, SDK/featurebundle/archtest/speccheck, external fixture, runtime-sensitive/migrated-feature suites, PR CI/QA, and benchmark allocation/B-op evidence as green.
Remaining closeout gate
This work order is not yet truthfully complete in repository state. On current main:
.kiro/specs/pre-oss-core-slimming/tasks.md still leaves Task 8.4 unchecked;
.kiro/specs/pre-oss-core-slimming/spec.json still has phase: tasks-generated, ready_for_implementation: true, and completed: false;
- the spec remains under the active
.kiro/specs/ location rather than being archived as Task 8.4 requires.
Therefore the earlier completed-state closure was premature. The remaining work is final Kiro/repository closeout: reconcile Task 8.4 with the already-green merged-main evidence, ensure the required independent architecture/code-review disposition is recorded, archive the spec while retaining the residual ownership inventory, and mark the canonical spec completed.
Do not reopen production scope merely to satisfy bookkeeping; only repair missing evidence/closeout required by Task 8.4. Close #571 once those canonical artifacts truthfully represent the completed implementation.
Tracker relationship
Dependencies / coordination
Follow-up boundary
Merged spec PR #559 / post-split task #572 is the second/final architecture-completion phase. Its Task 0 requires an implemented and certified predecessor. Production implementation and exact race evidence are present, but canonical pre-OSS completion/archive is not yet recorded. Keep #572 planned until this closeout is complete.
Because #572 is in the later milestone, do not model #571 → #572 as a GitHub dependency edge; milestone sequencing supplies that prerequisite.
Implement the approved Kiro SDD introduced by merged spec-only PR #557.
Spec:
.kiro/specs/pre-oss-core-slimming/Current implementation status
The production implementation and runtime verification are effectively complete on current
main:d784a8344888dd9de2141a13d4bf723125d4b08c.Authoritative Linux race run
33891386913executed the exact required package scope against #591's mergedmainSHA and completed successfully. The #571 closeout comment also records generator/check, SDK/featurebundle/archtest/speccheck, external fixture, runtime-sensitive/migrated-feature suites, PR CI/QA, and benchmark allocation/B-op evidence as green.Remaining closeout gate
This work order is not yet truthfully complete in repository state. On current
main:.kiro/specs/pre-oss-core-slimming/tasks.mdstill leaves Task 8.4 unchecked;.kiro/specs/pre-oss-core-slimming/spec.jsonstill hasphase: tasks-generated,ready_for_implementation: true, andcompleted: false;.kiro/specs/location rather than being archived as Task 8.4 requires.Therefore the earlier completed-state closure was premature. The remaining work is final Kiro/repository closeout: reconcile Task 8.4 with the already-green merged-main evidence, ensure the required independent architecture/code-review disposition is recorded, archive the spec while retaining the residual ownership inventory, and mark the canonical spec completed.
Do not reopen production scope merely to satisfy bookkeeping; only repair missing evidence/closeout required by Task 8.4. Close #571 once those canonical artifacts truthfully represent the completed implementation.
Tracker relationship
Dependencies / coordination
Follow-up boundary
Merged spec PR #559 / post-split task #572 is the second/final architecture-completion phase. Its Task 0 requires an implemented and certified predecessor. Production implementation and exact race evidence are present, but canonical pre-OSS completion/archive is not yet recorded. Keep #572 planned until this closeout is complete.
Because #572 is in the later milestone, do not model #571 → #572 as a GitHub dependency edge; milestone sequencing supplies that prerequisite.