[Change] cross-repo-issue-realignment

[djm81]

Why

Active OpenSpec changes and linked GitHub issues still mix the old monolithic specfact-cli structure with the current lean-core plus specfact-cli-modules ownership model. That drift now blocks planning: some module-owned backlog, ceremony, and code-review work is still tracked in the core repo, while several active proposals describe obsolete in-repo module layouts and do not map cleanly to the canonical bundle boundaries.

What Changes

• Define a single decision framework for classifying active OpenSpec changes and linked GitHub issues as core, modules, or split/rescope.
• Require every affected active proposal in specfact-cli to be updated with the steps needed to fit the current architecture and repo assignment.
• Define the operational rule for handling GitHub issues that no longer belong in specfact-cli: either move the existing issue to specfact-cli-modules when the platform supports it, or close the old issue and create a replacement issue in specfact-cli-modules with updated scope and cross-links.
• Define how openspec/CHANGE_ORDER.md in specfact-cli and the corresponding planning inventory in specfact-cli-modules must be updated when ownership changes.
• Define the required Epic -> Feature -> User Story hierarchy to create in specfact-cli-modules so module-owned changes have the same planning structure now present in specfact-cli.
• Require a reconciled mapping from active core-repo user stories/change proposals to modules-repo epics/features when their implementation ownership is bundle-side.

Capabilities

New Capabilities

• cross-repo-backlog-alignment: Governance rules for assigning active changes and GitHub issues to the correct repository, reconciling issue migration or recreation, and maintaining aligned Epic -> Feature -> User Story planning hierarchies across specfact-cli and specfact-cli-modules.

Modified Capabilities

• backlog-module-ownership: Active backlog and ceremony changes must align their repository ownership, issue tracking, and proposal scope with the canonical specfact-backlog bundle boundary.
• project-codebase-ownership: Active changes that describe outdated module/package ownership must be reconciled to the canonical post-migration core-versus-bundle split before implementation proceeds.

Impact

• Affected systems: openspec/changes/* active proposals/tasks/designs, openspec/CHANGE_ORDER.md, GitHub issues in nold-ai/specfact-cli, and the corresponding issue/planning inventory in nold-ai/specfact-cli-modules.
• Operational impact: maintainers get an explicit move-vs-recreate workflow for issue reassignment and a required hierarchy creation plan for the modules repo.
• Cross-repo coordination: this change depends on inspecting both repositories together and documenting the resulting ownership mapping before further implementation work continues on stale proposals.

[djm81]

Classification inventory completed in the OpenSpec change artifact.

Summary:

• core: 18 active changes
• modules: 9 active changes
• split/rescope: 8 active changes

The matrix is captured in openspec/changes/cross-repo-issue-realignment/analysis.md and will drive the next step: deciding transfer vs close-and-recreate for the module-owned issues, then defining the required Epic/Feature hierarchy in specfact-cli-modules.

[djm81]

Modules-repo hierarchy and clear issue transfers are now complete.

Created in specfact-cli-modules:

• Epics: #145 specfact backlog, #144 specfact project
• Features: #151 Scrum Workflows, #149 Kanban Flow Metrics, #146 SAFe & PI Planning, #148 Policy Engine & Enforcement Modes, #150 Ceremony Command Layer, #147 Sync Engine

Transferred authoritative module-owned stories:

• #169 -> modules#152
• #170 -> modules#160
• #171 -> modules#153
• #183 -> modules#155
• #184 -> modules#154
• #182 -> modules#156
• #246 -> modules#158
• #245 -> modules#159
• #243 -> modules#157

Both CHANGE_ORDER.md files were updated so core now marks these as transferred and modules now lists them as pending authoritative work under the new Epic -> Feature -> User Story hierarchy.

Next remaining work in this change: rewrite the affected active OpenSpec proposals so their scope and implementation paths match the new repo ownership.

[djm81]

Cross-repo OpenSpec artifact alignment is now in place.

Completed:

• moved the nine transferred bundle-owned OpenSpec changes out of specfact-cli and into specfact-cli-modules
• copied the eight split changes into specfact-cli-modules as paired runtime follow-ups
• created concrete modules-side follow-up issues fix: improve ADO backlog refine error logging and user-facing error UX #164-#171 and attached them under the new modules Feature parents
• updated source tracking in both repos so core proposals point to paired modules runtime issues and modules proposals point back to their core counterparts where applicable
• updated both repos openspec/CHANGE_ORDER.md files so blocker/dependency tracking reflects the migrated and split ownership model
• cleaned up core CHANGE_ORDER.md references that still implied active core ownership for moved bundle changes

Current state:

• core repo keeps only core-owned changes plus the core-contract half of split changes
• modules repo now owns the migrated bundle runtime changes and the modules-runtime half of split changes
• issue hierarchy, OpenSpec folders, and planning inventories are aligned to the same repo split