ace-pm 35dc87ef53 chore: sync workspace state after rebrand

- Rebrand commits already in history (gsd → forge)
- Sync pre-existing doc, docker, and CI config updates
- All rebrand artifacts verified in place:
  * Native crates: forge-engine, forge-ast, forge-grep
  * Log prefixes: [forge] across 22+ files
  * Binary: ~/bin/sf-run
  * Workspace scopes: @sf-run/*, @singularity-forge/*
  * Nix flake: Rust toolchain ready

System ready for: nix develop && bun run build:native

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-15 14:54:20 +02:00

1.3 KiB

Raw Blame History

Migration from v1

If you have projects with .planning directories from the original Singularity Forge (v1), you can migrate them to SF's .gsd format.

Running the Migration

# From within the project directory
/gsd migrate

# Or specify a path
/gsd migrate ~/projects/my-old-project

What Gets Migrated

The migration tool:

Parses your old PROJECT.md, ROADMAP.md, REQUIREMENTS.md, phase directories, plans, summaries, and research
Maps phases → slices, plans → tasks, milestones → milestones
Preserves completion state ([x] phases stay done, summaries carry over)
Consolidates research files into the new structure
Shows a preview before writing anything
Optionally runs an AI-driven review for quality assurance

Supported Formats

The migration handles various v1 format variations:

Milestone-sectioned roadmaps with <details> blocks
Bold phase entries
Bullet-format requirements
Decimal phase numbering
Duplicate phase numbers across milestones

Requirements

Migration works best with a ROADMAP.md file for milestone structure. Without one, milestones are inferred from the phases/ directory.

Post-Migration

After migrating, verify the output:

/gsd doctor

This checks .gsd/ integrity and flags any structural issues.

1.3 KiB Raw Blame History