Files

T

CI cf5e7695fd feat(P03): multi-project support, NFR milestone versioning, phase context reset, install scripts

---ci---
phase: 3
milestone: v0.3.0
status: complete
decisions:
  - id: D-006
    decision: Multi-project via .ci/<slug>/ subdirectories and config.json registry
    rationale: Backward compatible migration from flat files; slug-based namespacing for branches and commits
    confidence: 0.92
    alternatives: [Git worktrees, Separate repos with subtrees]
  - id: D-007
    decision: NFR milestones use progressive patch versioning (no minor tag)
    rationale: NFR phases (fix/chore/docs/perf/refactor/test) don't represent feature delivery; patch increments reflect incremental improvement only
    confidence: 0.90
    alternatives: [Treat all milestones uniformly, Skip versioning for NFR]
  - id: D-008
    decision: Phase context reset via git checkpoint + fresh agent spawn
    rationale: Git-native architecture makes full state serialization safe; fresh context prevents accumulated conversation drift
    confidence: 0.88
    alternatives: [Context compaction, Sliding window summarization]
  - id: D-009
    decision: Install via both npm postinstall and standalone bash script
    rationale: Postinstall only fires on npm install -g; standalone script covers manual/cloned installs
    confidence: 0.95
    alternatives: [Postinstall only, Makefile target]
---/ci---

Source code:
- Added ProjectEntry, projects[], active_project to CIConfig
- Added project?: string to CiMetadata, CommitScope, all commit input types
- CiFiles: multi-project support (projectSlug, listProjects, addProject, migrateFlatToProject, isNfrMilestone)
- GitContext: projectSlug support, detectProjectFromCommit(), isNfrMilestone()
- GitBranch: project-prefixed branch naming via prefix()
- commit-builder/parser: project field in ---ci--- blocks
- config.ts: initCI() accepts projectSlug/projectName
- Implemented parseRoadmapMd phase parsing
- 284 tests passing (66 new tests)

Install scripts:
- scripts/install.sh: Standalone bash installer
- scripts/postinstall.js: npm postinstall (global installs only)

OpenCode integration:
- All 18 agents updated with multi-project project_context
- All 11 workflows updated with Step 0: Confirm Active Project
- All 5 references updated (branch-strategy, ci-files-discipline, commit-schema, decision-engine, git-context-loading)
- All 3 contexts updated (dev, research, review)
- VERSION bumped to 0.3.0

Package:
- Added files field, postinstall script, install script alias
- Version bumped to 0.3.0

2026-05-29 14:11:49 +00:00

2.3 KiB

Raw Blame History

description

description
Rollback CI phase — revert the last phase or specified phase by resetting to its pre-phase state

CI Rollback

Rollback a CI phase by reverting to the state before the phase started. Uses git to find the exact commit to reset to.

Usage: ci-rollback [phase_number]

If no phase specified, rolls back the current (most recent) phase.

Step 0: Confirm Active Project

Check ci listProjects() or read .ci/config.json to determine if multi-project mode is active.

If .ci/config.json has projects[] with length > 0:

Confirm active_project is correct for this rollback
If not, set it with ci setActiveProject(<slug>)
Identify project-scoped branches (prefixed with <slug>/)
All commit messages must include project: <slug> in ---ci--- block

If single-project mode: proceed with existing conventions (branches without slug prefix).

Step 1: Load Git Context

git log --max-count=30
git branch -a

Find the phase branch and its merge commit.

Step 2: Identify Rollback Point

For the specified phase:

Find the merge commit that completed the phase
Find the commit just before the phase branch was created
This is the rollback point

git log --grep="P##" --format="%H %s" | head -20

Step 3: Confirm (Safety Gate)

Even in full autonomy mode, destructive operations need confirmation:

⚠ ROLLBACK: This will revert Phase [N] — [name]

Rollback point: [commit hash] [subject]
Changes to be lost: [N] commits

Proceed? (y/n)

Wait for confirmation. This is a safety gate — always confirm destructive operations.

Step 4: Execute Rollback

git revert [merge_commit_hash]

Or for a hard rollback (not recommended, only if explicitly requested):

git reset --hard [rollback_point]

Step 5: Update State

Delete the phase branch (if not already removed)
Update .ci/REQUIREMENTS.md — mark phase requirements as blocked
Update .ci/ROADMAP.md — mark phase as not_started

Commit the rollback:

chore(P##): rollback [phase-name] — [reason]

---ci---
phase: [N]
milestone: [vX.X]
status: specify
escalations:
  - id: E-XXX
    type: rollback
    description: Phase rolled back
    resolution: auto
---/ci---

Step 6: Report

Report rollback complete, rollback point, and next steps.

2.3 KiB Raw Blame History