[Roadmap] Track phased delivery and implementation backlog

[phamhungptithcm]

Purpose

Track the phased delivery plan for gig in one place and keep implementation work tied back to roadmap scope.

Phase Issues

• [Phase 0] Complete foundation hardening and repository governance #1 Foundation hardening and repository governance
• [Phase 1] Harden MVP CLI behavior and regression coverage #2 MVP CLI hardening and regression coverage
• [Phase 2] Implement guided promotion planning and dry-run flow #3 Guided promotion planning and dry-run flow
• [Phase 3] Add dependency parsing and snapshot support #4 Dependency parsing and snapshot support
• [Phase 4] Add SVN, Jira, Mendix, and enterprise reporting #5 Enterprise integrations and reporting
• [Bug Backlog] Track defects and regressions across releases #6 Rolling defect and regression backlog

Supporting Epics

• [Epic] Model ticket journey, environment state, and release manifest #8 Model ticket journey, environment state, and release manifest
• [Epic] Add repository catalog, env mapping, and team configuration #9 Add repository catalog, env mapping, and team configuration
• [Epic] Add JSON output and release manifest generation #10 Add JSON output and release manifest generation
• [Epic] Add risk engine for DB, Mendix, config, and manual steps #11 Add risk engine for DB, Mendix, config, and manual steps
• [Epic] Integrate Jira and GitHub or GitLab evidence #12 Integrate Jira and GitHub or GitLab evidence
• [Epic] Add inspect, env-status, verify, and release planning commands #13 Add inspect, env-status, verify, and release planning commands
• [Epic] Publish team adoption guide and governance templates #14 Publish team adoption guide and governance templates

Release Mapping

• v0.1.x: stabilize foundation and MVP behavior
• v0.2.x: config, catalog, JSON output, and report structure
• v0.3.x: inspect, release manifest, and dry-run planning
• v0.4.x: dependency, snapshot, deployment evidence, and bundle planning
• v0.5.x: controlled promote execution and follow-up reporting
• v0.6.x: SVN, Jira enrichment, Mendix heuristics, and enterprise reporting

Working Notes

• feature branches should continue to branch from staging and return to staging
• promotion from staging to main should remain explicit and reviewable
• bug issues should link back to the relevant phase issue whenever possible
• epic issues should translate the strategy docs into concrete implementation slices