chore: 归档 final-closeout-refactor 变更

- 将变更移动到 openspec/changes/archive/2026-04-29-final-closeout-refactor/
- 同步 delta specs 到主 specs:
  - project-surface: 添加重复文件删除、BMad Skills 清理场景
  - project-governance: 添加 copilot 指令忽略场景

Author: shijiashuai

data/active_learning/active_learning_data.json

@@ -34,4 +34,4 @@
     "low_confidence_detected": 0,
     "feedback_collected": 4
   }
-}
+}

…s/final-closeout-refactor/.openspec.yaml …9-final-closeout-refactor/.openspec.yamlopenspec/changes/final-closeout-refactor/.openspec.yaml renamed to openspec/changes/archive/2026-04-29-final-closeout-refactor/.openspec.yaml openspec/changes/final-closeout-refactor/.openspec.yaml renamed to openspec/changes/archive/2026-04-29-final-closeout-refactor/.openspec.yaml

@@ -1,4 +1,4 @@
-## ADDED Requirements
+## Requirements
 
 ### Requirement: OpenSpec is the sole active specification workflow
 The repository MUST treat `openspec/` as the only normative specification system for planning, proposal, implementation, and archival workflows.
@@ -26,6 +26,12 @@ All maintained AI instruction files MUST communicate the same repository workflo
 - **WHEN** they describe workflow or repository conventions
 - **THEN** they MUST agree on OpenSpec-first governance, direct-push operation, and the authoritative project surface
 
+#### Scenario: Copilot instructions are ignored
+- **GIVEN** `.github/copilot-instructions.md` exists
+- **WHEN** the project is cleaned for final closeout
+- **THEN** the file MUST remain in `.gitignore` (already configured)
+- **AND** it MUST NOT be tracked in version control
+
 ### Requirement: Final closeout work proceeds through one umbrella change with ordered phases
 The repository MUST allow a final closeout initiative to run as one umbrella OpenSpec change, provided its internal tasks preserve explicit phase ordering and dependency tracking.
 
@@ -52,3 +58,4 @@ Governance documents MUST explain how `/review` or equivalent review steps are u
 - One umbrella closeout change does not imply unordered execution.
 - Review remains present as quality control without becoming a branching ritual.
 - Handoff expectations are explicit enough for a follow-up model or maintainer.
+- All zombie branches have been removed from the remote.

…hanges/final-closeout-refactor/design.md …-04-29-final-closeout-refactor/design.mdopenspec/changes/final-closeout-refactor/design.md renamed to openspec/changes/archive/2026-04-29-final-closeout-refactor/design.md openspec/changes/final-closeout-refactor/design.md renamed to openspec/changes/archive/2026-04-29-final-closeout-refactor/design.md

@@ -1,4 +1,4 @@
-## ADDED Requirements
+## Requirements
 
 ### Requirement: The public documentation surface is intentionally small
 The repository MUST keep a small set of maintained public-facing documents and MUST remove or retire low-value, redundant, or stale documentation that is not needed for users or maintainers.
@@ -9,6 +9,18 @@ The repository MUST keep a small set of maintained public-facing documents and M
 - **THEN** one canonical maintained document MUST remain
 - **AND** redundant documents MUST be removed, archived, or replaced with a brief migration breadcrumb
 
+#### Scenario: Duplicate source files are removed
+- **GIVEN** duplicate source files exist in the repository (e.g., `src/data_exporter.py` vs `src/data/exporter.py`)
+- **WHEN** the project surface is normalized
+- **THEN** only one version of each module MUST be retained
+- **AND** the retained version MUST be in the canonical location matching `pyproject.toml` package configuration
+
+#### Scenario: BMad Skills are removed
+- **GIVEN** the repository contains 46 BMad skills unrelated to the project
+- **WHEN** the project surface is cleaned
+- **THEN** all `bmad-*` skills MUST be removed
+- **AND** only OpenSpec-related skills (`opsx-*`) MAY be retained
+
 ### Requirement: README is the canonical repository entry point
 The root README MUST present the maintained product story, supported installation paths, and links to the essential documentation surface without duplicating the entire docs site.
 
@@ -53,3 +65,6 @@ The maintained docs site MUST keep only pages that serve the product landing sto
 - The docs source tree contains maintainable source, not large reproducible build outputs.
 - Pages content stays aligned with active product messaging.
 - Deep pages exist only when they still explain maintained behavior.
+- No duplicate source files exist in the codebase.
+- All source files match the package configuration in `pyproject.toml`.
+- Only project-relevant skills remain in `.claude/skills/`.