msd-core/docs/features/phase-lifecycle-status-line-read-side.md at 12ee75a509cbfd8fe2ae2871056fa81777d7dcf5

Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

1.2 KiB

Raw Blame History

id, title, group

id	title	group
125	Phase-Lifecycle Status-Line Read-Side	v1.40.0 Features

Purpose: Surface phase orchestration state on the status-line. parseStateMd() reads four new STATE.md frontmatter fields and formatMsdState() renders in-flight, idle, and progress scenes. Write-side wiring follows in a later RC.

Requirements:

REQ-LIFECYCLE-01: parseStateMd() reads four optional fields:
- active_phase — phase number when an orchestrator is in flight
- next_action — recommended next command when idle
- next_phases — YAML flow array of next phase numbers
- progress — nested total_phases / completed_phases / percent block
REQ-LIFECYCLE-02: formatMsdState() checks the lifecycle fields in priority order and emits the first matching scene (Phase active → Idle next-recommended → Milestone complete → Default fallback).
REQ-LIFECYCLE-03: All four fields default to undefined; existing STATE.md files render byte-for-byte identically.

Reference issue: #2833 — see docs/STATE-MD-LIFECYCLE.md for the full field reference and rendering rules.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History