Milestone and Sprint Patterns

This sprint built the core include form without touching the bundled pattern set. The brief asked for syntax, recursive composition, parameter substitution, collision refusals, cross-file branch validation, and run-local override resolution all at once. Its gate went red and needed a repair, which fits a boundary where parser, resolver, substitution, and validation assumptions all met. Once fixed, it left the following sprint a callable composition entry point instead of an idea in a plan.

This sprint moved inclusion from discovery into the run lifecycle. The agent was asked to make frozen closures contain included files and to make resume, runtime invocation, prompt discovery, script materialization, and diagram reads compose from those frozen bytes. The gate went red after review and was repaired, showing that the boundary was not syntax but every secondary reader of pattern source. The sprint still finished without a retry, leaving a stable run pin for shipped inclusion to rely on.

This sprint deliberately carried documentation only after the runtime behavior had been proven. Its brief told the worker to read the code as built, reconcile older claims about private namespaces, and leave conformance slicing intact. The unit stayed green, which matches a task whose risk was precision rather than integration. It closed the milestone by turning the implementation into the language contract the next milestone could cite.

This sprint prepared the tree for a fragment before the real fragment existed. The worker had to teach registry-listing, rendering, diagram, and selectable-pattern surfaces that a registry entry can be included-only material, then capture the old build unit as a structural baseline. Its green run meant the later split could change files against a recorded fixed point rather than inventing policy mid-migration. The scope was intentionally fixture-driven, keeping the shipped set untouched.

This sprint did the actual split after the fragment policy and parity baseline were in place. The brief constrained the agent to a renaming and refiling change: move the per-sprint pipeline into sprint, keep planning and recovery in milestone, preserve behavior, and prove equivalence with the wrapper block inclusion introduces. It stayed green, which is the important signal for a mechanical-looking but high-blast-radius move. Compatibility proof and prose were left for later sprints rather than folded into this central edit.

This sprint handled recorded and resumable runs after the live registry had changed. Its task was to read the real replay, reconstruction, repair, and resume paths before adding tests, because some paths use frozen material while others hold only a historical name. The unit stayed green, showing the compatibility story could be pinned without adding a second alias path. It also copied a real pre-rename recording as evidence instead of fabricating one from the new tree.

This final sprint made the written tree match the built tree. The brief asked for the manual, specification, live docs, prompt references, code identifiers, generated artifacts, and the live plan queue to be swept under a clear historical-record boundary. It stayed green, so the only remaining run stress was outside the sprint, in merge conflict resolution after the broad rename crossed other work. The unit was last because it depended on the exact contracts and compatibility fixtures written by the earlier migration sprints.