You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation brought in line with the TDD workflow and the test skills.docs/getting-started
(en/ja) gains the characterization step on the legacy path, what gate stages 2 and 4 hold the
scaffold to, and the delivery path described as test-driven (walking-skeleton Issue, the test: → feat: → refactor: series, Fakes and injected Clock, reproduce-first fixes);
README's delivery paragraph says the same; docs/architect-input-requirements (en/ja) lists a
runnable legacy system — or a test-only datasource substitution — as an input for
characterization tests; docs/scalardb-development (en/ja) documents the scaffold's test tree;
OMNIGENT's quality-gate section names the stage 2/4 tasks and the clean-build rule; the
skill-reference rows for export-backlog, implement-backlog and review-issue describe the
current behaviour.