# Day Shift 0.1.20 Release Notes This release completes agent guidance command contract / closeout and memory guidance / define implementation summary closeout, agent guidance command contract / closeout and memory guidance / define reconciliation readiness, agent guidance command contract / closeout and memory guidance / define repository memory checkpoint boundary, agent guidance command contract / closeout and memory guidance / define review and validation evidence boundaries, agent guidance command contract / command surface and output contract / define orientation data model, agent guidance command contract / command surface and output contract / register agent command family, agent guidance command contract / command surface and output contract / render default text orientation, agent guidance command contract / command surface and output contract / render reminder alias, agent guidance command contract / repository orientation context / agent verbose output mode, agent guidance command contract / repository orientation context / recommend health and runtime discovery, agent guidance command contract / repository orientation context / recommend planning and spec discovery, agent guidance command contract / repository orientation context / report agent entrypoint status, agent guidance command contract / repository orientation context / report effective root context, agent guidance command contract / validation docs and regression coverage / test command aliases and output modes, agent guidance command contract / validation docs and regression coverage / test no write regression contract, agent guidance command contract / validation docs and regression coverage / test root entrypoint and discovery context, agent guidance command contract / validation docs and regression coverage / test workflow boundaries and guardrails, agent guidance command contract / validation docs and regression coverage / update agent command documentation, agent guidance command contract / workflow rules and command boundaries / classify command surfaces, agent guidance command contract / workflow rules and command boundaries / encode finding and state guardrails, agent guidance command contract / workflow rules and command boundaries / encode migration and health blockers, agent guidance command contract / workflow rules and command boundaries / encode planning flow rules, canonical documentation application / application and content foundation / frontmatter and content collection, canonical documentation application / application and content foundation / initial information architecture, canonical documentation application / application and content foundation / starlight application scaffold, canonical documentation application / complete cli and automation reference / command and capability inventory, canonical documentation application / complete cli and automation reference / core workflow command reference, canonical documentation application / complete cli and automation reference / operational and administration reference, canonical documentation application / complete cli and automation reference / structured automation and extension contracts, canonical documentation application / documentation coverage and drift verification / continuous documentation drift gates, canonical documentation application / documentation coverage and drift verification / example link and troubleshooting verification, canonical documentation application / documentation coverage and drift verification / page disposition and substance closure, canonical documentation application / documentation coverage and drift verification / product surface coverage verification, canonical documentation application / end to end workflow and artifact lifecycle / evidence review and reconciliation lifecycle, canonical documentation application / end to end workflow and artifact lifecycle / intake to implementation workflow, canonical documentation application / end to end workflow and artifact lifecycle / operating model and artifact concepts, canonical documentation application / end to end workflow and artifact lifecycle / resume trace archive and release handoff, canonical documentation application / installation init and workspace onboarding / canonical page inventory and entry points, canonical documentation application / installation init and workspace onboarding / configuration shell and first health checks, canonical documentation application / installation init and workspace onboarding / init and workspace anatomy, canonical documentation application / installation init and workspace onboarding / installation and version management, canonical documentation application / integrated verification and deployment / cross application and domain verification, canonical documentation application / integrated verification and deployment / end to end publication verification, canonical documentation application / integrated verification and deployment / vercel readiness and release gate, canonical documentation application / marketing content migration / canonical content migration, canonical documentation application / marketing content migration / website content inventory, canonical documentation application / marketing content migration / website entry point transition, canonical documentation application / prompts templates and customization / discovery rendering and trust boundaries, canonical documentation application / prompts templates and customization / prompt and template catalogs, canonical documentation application / prompts templates and customization / upgrade merge and drift maintenance, canonical documentation application / prompts templates and customization / workspace customization workflows, canonical documentation application / publication and artifact pipeline / command and build lifecycle, canonical documentation application / publication and artifact pipeline / inference artifact generation, canonical documentation application / publication and artifact pipeline / publication eligibility contract, day shift version manager / command surface and shim runtime / command family contract, day shift version manager / command surface and shim runtime / runtime diagnostics, day shift version manager / command surface and shim runtime / shim dispatch runtime, day shift version manager / inspection network and cross platform diagnostics / approval gated network check, day shift version manager / inspection network and cross platform diagnostics / cross platform path diagnostics, day shift version manager / inspection network and cross platform diagnostics / list current and doctor output, day shift version manager / managed state and install validation / local source install validation, day shift version manager / managed state and install validation / managed version write path, day shift version manager / managed state and install validation / state root and layout, day shift version manager / regression coverage and release handoff / diagnostics and release handoff, day shift version manager / regression coverage and release handoff / install uninstall license regressions, day shift version manager / regression coverage and release handoff / runtime selection regressions, day shift version manager / selection aliases and pinning / aliases and partial selectors, day shift version manager / selection aliases and pinning / repository pins and config defaults, day shift version manager / selection aliases and pinning / resolution precedence, day shift version manager / uninstall and license preservation / license preservation and coverage, day shift version manager / uninstall and license preservation / selector impact and replacement, day shift version manager / uninstall and license preservation / targeted uninstall contract, eadl qualification analysis / classification and report synthesis / classification and qualification boundary, eadl qualification analysis / classification and report synthesis / ten section report, eadl qualification analysis / qualification and trace analysis / representative workflow trace, eadl qualification analysis / qualification and trace analysis / thirteen criterion evidence matrix, eadl qualification analysis / repository model and evidence baseline / implemented repository model, eadl qualification analysis / repository model and evidence baseline / revision and evidence inventory, lifecycle friction reduction / closeout build and status sync / explicit status metadata sync, lifecycle friction reduction / closeout build and status sync / implementation summary build closeout, lifecycle friction reduction / closeout build and status sync / reconciliation build closeout, lifecycle friction reduction / command surface adoption audit / adoption validation and gap report, lifecycle friction reduction / command surface adoption audit / command surface inventory, lifecycle friction reduction / command surface adoption audit / guidance command adoption map, lifecycle friction reduction / command surface adoption audit / machine readable command inventory export, lifecycle friction reduction / command surface adoption audit / prompt reference workflow alignment, lifecycle friction reduction / evidence aware review behavior / actionable review findings, lifecycle friction reduction / evidence aware review behavior / active evidence warning downgrade, lifecycle friction reduction / evidence aware review behavior / declared later work classification, lifecycle friction reduction / markdown link materialization / body reference source locations, lifecycle friction reduction / markdown link materialization / cli integration and guidance, lifecycle friction reduction / markdown link materialization / markdown link rewrite engine, lifecycle friction reduction / markdown link materialization / materialization command contract, lifecycle friction reduction / markdown link materialization / regression and validation coverage, lifecycle friction reduction / regression guidance and release handoff / command family regression update, lifecycle friction reduction / regression guidance and release handoff / release handoff evidence, lifecycle friction reduction / regression guidance and release handoff / workflow guidance alignment, lifecycle friction reduction / scaffold contract intelligence / milestone scaffold inheritance, lifecycle friction reduction / scaffold contract intelligence / task scaffold inheritance, lifecycle friction reduction / scaffold contract intelligence / upstream metadata preservation, lifecycle friction reduction / task scoped change evidence / path category classification, lifecycle friction reduction / task scoped change evidence / summary closeout evidence feed, lifecycle friction reduction / task scoped change evidence / task scope change report, onboarding experience redesign / audience and responsibility separation / audience marker inventory, onboarding experience redesign / audience and responsibility separation / human agent boundary mapping, onboarding experience redesign / audience and responsibility separation / prompt template reference boundaries, onboarding experience redesign / audience and responsibility separation / reference and marker materialization, onboarding experience redesign / doc hygiene validation and migration / compatibility and validation pass, onboarding experience redesign / doc hygiene validation and migration / duplication and canonical link cleanup, onboarding experience redesign / doc hygiene validation and migration / stale cli wording cleanup, onboarding experience redesign / evidence navigation and workflow handoffs / evidence source navigation, onboarding experience redesign / evidence navigation and workflow handoffs / read only discovery command guidance, onboarding experience redesign / evidence navigation and workflow handoffs / workflow input output handoffs, onboarding experience redesign / human onboarding entrypoints / existing repository onboarding, onboarding experience redesign / human onboarding entrypoints / first project guide refinement, onboarding experience redesign / human onboarding entrypoints / human workflow routing, onboarding experience redesign / reference and layer relationship docs / command registry and metadata reference, onboarding experience redesign / reference and layer relationship docs / planning layer relationship reference, onboarding experience redesign / reference and layer relationship docs / prompt template validation reference, programmatic workflow enforcement / artifact shape and family validation / artifact family parser and shape rules, programmatic workflow enforcement / artifact shape and family validation / prompt template manifest and scaffold lanes, programmatic workflow enforcement / artifact shape and family validation / trace link and file scoped validation, programmatic workflow enforcement / closeout and reconciliation evidence / implementation summary evidence review, programmatic workflow enforcement / closeout and reconciliation evidence / lifecycle status coherence, programmatic workflow enforcement / closeout and reconciliation evidence / reconciliation eligibility gates, programmatic workflow enforcement / command capability and no write boundaries / command capability registry, programmatic workflow enforcement / command capability and no write boundaries / command posture regression tests, programmatic workflow enforcement / command capability and no write boundaries / read only boundary reporting, programmatic workflow enforcement / heuristics and derived state gates / derived state sync eligibility, programmatic workflow enforcement / heuristics and derived state gates / lightweight promotion pressure, programmatic workflow enforcement / heuristics and derived state gates / planning language and decomposition warnings, programmatic workflow enforcement / layer specific overview filename migration / destination contract and compatibility policy, programmatic workflow enforcement / layer specific overview filename migration / docs templates and regression coverage, programmatic workflow enforcement / layer specific overview filename migration / scaffold navigation and link resolution, programmatic workflow enforcement / lifecycle and scaffold gates / create revise and selected artifact boundaries, programmatic workflow enforcement / lifecycle and scaffold gates / linked slice parent traceability and conflicts, programmatic workflow enforcement / lifecycle and scaffold gates / source spec and planning advancement gates, programmatic workflow enforcement / reporting guidance and regression coverage / cross family regression coverage, programmatic workflow enforcement / reporting guidance and regression coverage / finding taxonomy and output guidance, programmatic workflow enforcement / reporting guidance and regression coverage / workflow prompt reference alignment, runtime evidence gates / closeout review and validation gates / reconciliation runtime evidence, runtime evidence gates / closeout review and validation gates / summary closeout gates, runtime evidence gates / closeout review and validation gates / task readiness mode gates, runtime evidence gates / closeout review and validation gates / validation exception policy, runtime evidence gates / execution mode and runtime delta contracts / contract closeout boundary, runtime evidence gates / execution mode and runtime delta contracts / execution mode metadata, runtime evidence gates / execution mode and runtime delta contracts / runtime delta contract, runtime evidence gates / guidance template and policy pack alignment / command output guidance, runtime evidence gates / guidance template and policy pack alignment / portable policy pack, runtime evidence gates / guidance template and policy pack alignment / prompt and workflow guidance, runtime evidence gates / guidance template and policy pack alignment / template mode and delta content, runtime evidence gates / path classification and change evidence / changed path evidence, runtime evidence gates / path classification and change evidence / default doc path classifier, runtime evidence gates / path classification and change evidence / repository path policy, runtime evidence gates / path classification and change evidence / runtime target alignment, runtime evidence gates / regression and ci enforcement / ci policy enforcement, runtime evidence gates / regression and ci enforcement / classifier and evidence regressions, runtime evidence gates / regression and ci enforcement / mode and delta regressions, runtime evidence gates / regression and ci enforcement / review gate regressions, runtime evidence gates / workflow separation and loop detection / breakout task requirement, runtime evidence gates / workflow separation and loop detection / contract to runtime handoff, runtime evidence gates / workflow separation and loop detection / documentation loop detection, runtime evidence gates / workflow separation and loop detection / phase and milestone review alignment, small model agent efficiency / artifact scoped context and context packs / build relevance ranked context packs, small model agent efficiency / artifact scoped context and context packs / deliver artifact scoped agent context, small model agent efficiency / artifact scoped context and context packs / integrate budget freshness and exclusion reporting, small model agent efficiency / atomic mutations and crash recovery / add locking rollback and crash recovery, small model agent efficiency / atomic mutations and crash recovery / deliver multi file plans preconditions and receipts, small model agent efficiency / atomic mutations and crash recovery / establish atomic single file write primitive, small model agent efficiency / authoritative command descriptors and tool discovery / add structured input and drift validation, small model agent efficiency / authoritative command descriptors and tool discovery / deliver focused discovery and tool manifests, small model agent efficiency / authoritative command descriptors and tool discovery / establish authoritative command descriptor registry, small model agent efficiency / bound and page output contracts / add deterministic pagination and completeness, small model agent efficiency / bound and page output contracts / enforce output budgets and bounded failures, small model agent efficiency / bound and page output contracts / implement detail grouping and filter contracts, small model agent efficiency / canonical policy composition and trust boundaries / enforce trust lanes and prompt injection boundaries, small model agent efficiency / canonical policy composition and trust boundaries / establish canonical policy rules and composition, small model agent efficiency / canonical policy composition and trust boundaries / unify authorization redaction and sanitization, small model agent efficiency / consolidate and close related specifications / build related spec coverage matrix, small model agent efficiency / consolidate and close related specifications / recertify linkage and lifecycle evidence, small model agent efficiency / consolidate and close related specifications / record closeout and archive eligible specs, small model agent efficiency / constrained execution profiles and task sizing / add advisory task sizing and decomposition, small model agent efficiency / constrained execution profiles and task sizing / define constrained profile and readiness gates, small model agent efficiency / constrained execution profiles and task sizing / integrate profile decisions and calibration hooks, small model agent efficiency / evidence freshness observability and performance / add cache lifecycle and bounded decision traces, small model agent efficiency / evidence freshness observability and performance / establish performance benchmarks and regression gates, small model agent efficiency / evidence freshness observability and performance / implement incremental state and freshness indexing, small model agent efficiency / executable workflow actions and recovery / add evidence backed resume capsules, small model agent efficiency / executable workflow actions and recovery / model executable workflow state and actions, small model agent efficiency / executable workflow actions and recovery / standardize typed failures and recovery actions, small model agent efficiency / explicit work selection and concurrency / deliver actionable candidate discovery, small model agent efficiency / explicit work selection and concurrency / implement local selection lifecycle and precedence, small model agent efficiency / explicit work selection and concurrency / protect selection state with concurrency evidence, small model agent efficiency / scoped health and relevant blockers / classify action relevant blockers, small model agent efficiency / scoped health and relevant blockers / integrate scoped health with context and validation, small model agent efficiency / scoped health and relevant blockers / separate health domains and command surfaces, small model agent efficiency / shared artifact parsing and architecture decomposition / characterize and build shared artifact parser, small model agent efficiency / shared artifact parsing and architecture decomposition / decompose command adapters and priority hotspots, small model agent efficiency / shared artifact parsing and architecture decomposition / migrate planning and validation callers, small model agent efficiency / small model evaluation and calibration / add adversarial corpus and payload budgets, small model agent efficiency / small model evaluation and calibration / build deterministic trajectory harness, small model agent efficiency / small model evaluation and calibration / calibrate real model baselines and promotion gates, small model agent efficiency / version automation protocol and schemas / define protocol version and feature negotiation, small model agent efficiency / version automation protocol and schemas / establish canonical schema catalog, small model agent efficiency / version automation protocol and schemas / integrate runtime validation and generated types, test infrastructure / final v1 disposal and v2 default validation / final retained v1 disposition, test infrastructure / final v1 disposal and v2 default validation / final v2 default closeout evidence, test infrastructure / final v1 disposal and v2 default validation / fixture helper and tests tree cleanup, test infrastructure / final v1 disposal and v2 default validation / retained cli runtime v2 migration, test infrastructure / final v1 disposal and v2 default validation / retained lib and script v2 migration, test infrastructure / final v1 disposal and v2 default validation / v2 default runner repoint, test infrastructure / legacy retirement and runner alignment / equivalent coverage review, test infrastructure / legacy retirement and runner alignment / legacy retirement decisions, test infrastructure / legacy retirement and runner alignment / runner alignment and follow up, test infrastructure / paired artifact template and completion migrations / implementation summary command migration, test infrastructure / paired artifact template and completion migrations / reconciliation command migration, test infrastructure / paired artifact template and completion migrations / template completion and runtime validation migration, test infrastructure / post migration lifecycle and validation polish / active reference audit surface, test infrastructure / post migration lifecycle and validation polish / planning command option aliases, test infrastructure / post migration lifecycle and validation polish / reconciliation build evidence quality, test infrastructure / post migration lifecycle and validation polish / retained workspace root blocker, test infrastructure / post migration lifecycle and validation polish / retired file validation classification, test infrastructure / post migration lifecycle and validation polish / reviewer accepted residual semantics, test infrastructure / spec and planning command migrations / planning creation command migration, test infrastructure / spec and planning command migrations / planning update command migration, test infrastructure / spec and planning command migrations / spec registry command migration, test infrastructure / v2 build test reference alignment / active guidance reference alignment, test infrastructure / v2 build test reference alignment / final v1 retirement evidence, test infrastructure / v2 build test reference alignment / final v2 closeout evidence, test infrastructure / v2 build test reference alignment / init and lib v2 migration, test infrastructure / v2 build test reference alignment / package script and runner reference check, test infrastructure / v2 build test reference alignment / retained cli family inventory and sequencing, test infrastructure / v2 build test reference alignment / retained cli subprocess migration, test infrastructure / v2 build test reference alignment / v1 helper fixture and runner cleanup, test infrastructure / v2 harness baseline / representative smoke migration, test infrastructure / v2 harness baseline / subprocess helper contract, test infrastructure / v2 harness baseline / tests v2 structure and scripts, trace link lifecycle management / discovery and preview surfaces / affected artifact discovery, trace link lifecycle management / discovery and preview surfaces / migration preview output, trace link lifecycle management / discovery and preview surfaces / read only posture regressions, trace link lifecycle management / disposition crud cli / add update delete behavior, trace link lifecycle management / disposition crud cli / command family routing and help, trace link lifecycle management / disposition crud cli / list show and error output, trace link lifecycle management / disposition model and storage contract / apply evidence and safety boundaries, trace link lifecycle management / disposition model and storage contract / disposition schema and identity, trace link lifecycle management / disposition model and storage contract / storage location and file contract, trace link lifecycle management / forward link apply workflow / apply reporting and rollback guidance, trace link lifecycle management / forward link apply workflow / apply selection and dry run parity, trace link lifecycle management / forward link apply workflow / safe forward link mutation, trace link lifecycle management / guidance regression and release handoff / guidance and help text alignment, trace link lifecycle management / guidance regression and release handoff / regression coverage matrix, trace link lifecycle management / guidance regression and release handoff / release handoff and deferred scope, trace link lifecycle management / validation integration / links check disposition findings, trace link lifecycle management / validation integration / smoke and rollup lifecycle evidence, trace link lifecycle management / validation integration / validation no write regressions, website / automated upgrade discount checkout / license submission and verification, website / automated upgrade discount checkout / server created stripe upgrade checkout, website / automated upgrade discount checkout / upgrade flow validation and handoff, website / commerce and license delivery / checkout and upgrade entrypoints, website / commerce and license delivery / license delivery and recovery flow, website / commerce and license delivery / webhook and license issuance boundary, website / commercial journey and trust / authoritative plan and pricing contract, website / commercial journey and trust / checkout delivery upgrade and recovery, website / commercial journey and trust / public copy and documentation reconciliation, website / commercial journey and trust / publisher support privacy and security trust, website / discovery accessibility and performance / accessible semantics and interactions, website / discovery accessibility and performance / crawl surfaces and structured data, website / discovery accessibility and performance / responsive and performance budgets, website / discovery accessibility and performance / route metadata canonical and social contracts, website / downloads and release publication / download url contract, website / downloads and release publication / publication consistency validation, website / downloads and release publication / release asset consumption, website / integrated validation and release evidence / critical marketing and commerce journeys, website / integrated validation and release evidence / deterministic website and cross app gates, website / integrated validation and release evidence / manual quality and external review, website / measurement and baseline / analytics runtime and privacy contract, website / measurement and baseline / field performance and baseline window, website / measurement and baseline / funnel and commercial confirmation, website / nextjs site foundation / route and rendering model, website / nextjs site foundation / shared content and server boundary policy, website / nextjs site foundation / workspace and build contract, website / positioning navigation and product proof / compatibility and proof boundaries, website / positioning navigation and product proof / first contact positioning and actions, website / positioning navigation and product proof / homepage narrative and navigation, website / positioning navigation and product proof / reproducible product demonstration, website / public content and positioning / install license and troubleshooting docs, website / public content and positioning / marketing and product positioning, website / public content and positioning / support privacy and limitation pages, website / publication validation and launch readiness / launch readiness and handoff, website / publication validation and launch readiness / release commerce and secret boundary validation, website / publication validation and launch readiness / route content and build validation, website / visual system and route experience / commerce and content route polish, website / visual system and route experience / design tokens and shell components, and website / visual system and route experience / download install and license surfaces. ## Completed Work - Register Agent Command Family Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. - Implement the public `day-shift agent` command family entrypoints so the primary command and aliases resolve consistently to a read-only orientation command surface. - Define Orientation Data Model Reconciliation - Completed. All declared task summaries are completed and non-placeholder, and the milestone acceptance criteria are satisfied by the recorded implementation and validation evidence. - Define the shared `AgentOrientationData` contract that all agent command entrypoints and renderers use for stable text and JSON output. - Render Default Text Orientation Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone closure. - Implement the default text renderer for the full agent orientation payload as a compact, prompt-ready instruction block. - Render Reminder Alias Reconciliation - Completed. All four declared task summaries are completed and reviewed with sufficient closeout evidence. - Implement the `day-shift agent remind` correction-focused output path as a shorter orientation reminder that still uses the shared command surface and read-only contract. - Report Effective Root Context Reconciliation - Completed. All declared task implementation summaries are completed, reviewed, and sufficient for milestone closure. - Define how `day-shift agent` reports the effective repository or workspace root and the evidence used to resolve it, without reimplementing or mutating shared root-detection behavior. - Report Agent Entrypoint Status Reconciliation - Completed. All declared task implementation summaries are completed, reviewed, and non-placeholder. Milestone acceptance criteria are satisfied by the combined task evidence. - Define how `day-shift agent` reports the repository-level `.day-shift/agents.md` entrypoint path, presence, absence, and first-read guidance without creating or repairing the file. - Recommend Health And Runtime Discovery Reconciliation - Completed. All declared task summaries are completed, non-placeholder, and reviewed with no blocking findings. - Define the no-write health, configuration, runtime, and version discovery recommendations that `day-shift agent` emits before agents perform workspace mutation or rely on uncertain setup state. - Recommend Planning And Spec Discovery Reconciliation - Completed. The three declared task summaries are completed and reviewed, and milestone acceptance is satisfied by the recorded implementation and validation evidence. - Define the read-only planning, metadata, and specification discovery recommendations that help agents choose current source or planning artifacts from repository evidence instead of guessing state. - Agent Verbose Output Mode Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, and the milestone acceptance criteria are satisfied by task evidence and validation. - Add an explicit `--verbose` mode to the agent orientation command so agents can request a fuller text orientation picture without weakening the compact default output contract or relying only on JSON. - Encode Planning Flow Rules Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Define the agent-facing planning flow rules that keep orientation output aligned with the standard Day Shift hierarchy, layer-local advancement, selected-artifact evidence, lightweight planning exception, and emergent specification intake. - Classify Command Surfaces Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Define the read, write, validate, review, and mixed command-surface taxonomy that the agent orientation command exposes so agents can distinguish evidence-gathering surfaces from mutation-capable operations. - Encode Finding And State Guardrails Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and review-ready. Milestone acceptance criteria have been reviewed against task summary evidence and focused validation output. - Define severity, no-invented-state, selected-work evidence, and validation or review boundary guidance so agents treat findings and repository evidence as constraints rather than optional context. - Encode Migration And Health Blockers Reconciliation - Completed. All declared task implementation summaries are completed, reviewed, and non-placeholder; milestone acceptance criteria are satisfied by the recorded implementation and validation evidence. - Define the health-check, workspace-compatibility, and migration-blocker guidance that tells agents when to stop normal work and route through explicit diagnostics, preview, or apply flows instead of manually moving `.day-shift/` assets. - Define Implementation Summary Closeout Reconciliation - Completed. The three declared task implementation summaries are completed, reviewed, and sufficient for milestone closeout. - Define the closeout guidance that tells agents what implementation evidence must be recorded before work is claimed complete or handed into reconciliation. - Define Reconciliation Readiness Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, and milestone acceptance has been reviewed against task evidence. - Define the milestone reconciliation readiness gate so agents only roll up a milestone after all relevant task implementation summaries are completed and non-placeholder. - Define Review And Validation Evidence Boundaries Reconciliation - Completed. All three declared task implementation summaries are completed and non-placeholder, implementation-summary review reported sufficient closeout evidence for each task, and milestone reconciliation found no remaining blocking concerns. - Define closeout guidance that treats review and validation outputs as evidence only until a separate write-capable command or user request explicitly authorizes mutation. - Define Repository Memory Checkpoint Boundary Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, acceptance criteria are satisfied, and focused validation evidence is recorded. - Define bounded repository-memory checkpoint guidance for durable facts while making clear that orientation output does not write private model memory or repository-memory state. - Test Command Aliases And Output Modes Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. - Add regression coverage proving the agent orientation command entrypoints, default text mode, JSON mode, and alias outputs stay aligned with the source command contract. - Test Root Entrypoint And Discovery Context Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. - Add regression coverage proving the agent command reports effective root context, repository-entrypoint status, and discovery recommendations without inventing workspace state. - Test Workflow Boundaries And Guardrails Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, focused validation passed, and the milestone acceptance criteria are satisfied by the combined task evidence. - Add regression coverage proving the agent command preserves workflow-rule codes, command-boundary taxonomy, finding severity guidance, planning exceptions, emergent-work guidance, and migration-blocker routing. - Test No Write Regression Contract Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, focused validation passed, planning links-check passed, and the milestone acceptance criteria are satisfied by the combined task evidence. - Prove the agent orientation command remains a read-only orientation surface and does not create, repair, validate, migrate, checkpoint, release, or mutate repository artifacts as a side effect. - Update Agent Command Documentation Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and review-clean. - Update user-facing help and documentation surfaces so humans and automation agents can discover `day-shift agent` and `day-shift agent --format json` as the repository-orientation entrypoint. - 01 Starlight Application Scaffold Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-starlight-application-scaffold` milestone: create the `apps/docs` workspace with `pnpm create astro apps/docs --template starlight`, then establish core Starlight configuration, package scripts, and static deployment configuration. - 02 Frontmatter And Content Collection Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-frontmatter-and-content-collection` milestone: specify the shared page metadata contract and connect Starlight directly to the canonical Markdown collection. - 03 Initial Information Architecture Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-initial-information-architecture` milestone: establish the required home, getting-started, section-index, and contribution pages with valid explicit metadata. - 01 Publication Eligibility Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-publication-eligibility-contract` milestone: centralize metadata validation and the fail-closed eligibility decision for every public consumer. - 02 Inference Artifact Generation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-inference-artifact-generation` milestone: generate deterministic language-model indexes, clean Markdown exports, and approved public contracts from eligible canonical pages. - 03 Command And Build Lifecycle Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-command-and-build-lifecycle` milestone: integrate generation, checks, safe cleanup, static build, and output-leakage verification into supported scripts. - 01 Website Content Inventory Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-website-content-inventory` milestone: audit documentation-relevant website routes and modules and assign explicit ownership and migration dispositions. - 02 Canonical Content Migration Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-canonical-content-migration` milestone: rewrite move-scoped material as eligible canonical Markdown with appropriate information-architecture placement. - 03 Website Entry Point Transition Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-website-entry-point-transition` milestone: remove duplication, retain website-owned responsibilities, and implement summaries, redirects, navigation, and canonical docs links. - 01 End To End Publication Verification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-end-to-end-publication-verification` milestone: validate canonical-source propagation, eligibility consistency, deterministic generation, cleanup safety, and static output isolation. - 02 Cross Application And Domain Verification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Verify the cross-application publication boundary after canonical documentation migration: every intentional website entry point must resolve to its exact `https://docs.tnsds.tech` destination, documentation must link back only to website-owned operational surfaces, and retained commerce, release-delivery, support-policy, and legal routes must remain owned by the marketing application. - 03 Vercel Readiness And Release Gate Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-vercel-readiness-and-release-gate` milestone: confirm reproducible static builds, preview behavior, deployment configuration, canonical URLs, and production acceptance evidence. - 01 Canonical Page Inventory And Entry Points Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Inventory every currently authored canonical documentation page, assign a closed disposition that phase 09 can reconcile, and replace structural entry-point placeholders with useful orientation and onward navigation. - 02 Installation And Version Management Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish one canonical installation and version-management journey that is grounded in shipped release assets and the authoritative CLI command surface. Readers must be able to choose an exact release, verify it, install or upgrade without losing the previous working installation, understand the separate managed-version workflow, and recover safely from prerequisite, PATH, selection, or compatibility failures. - 03 Init And Workspace Anatomy Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish one canonical, runtime-grounded workspace initialization guide. A reader must be able to choose the effective target root, preview or run each supported init mode, understand every generated directory and file family, preserve user-owned customization on repeat runs, and recover safely from stale or partial workspace state. - 04 Configuration Shell And First Health Checks Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish one canonical, runtime-grounded guide that takes a reader from an initialized repository through configuration inspection, optional shell completion, read-only health diagnosis, and the first safe planning action. The guide must distinguish repository-shared and local-only configuration, expose effective-value provenance, and label every workspace or host mutation before asking the reader to authorize it. - 01 Operating Model And Artifact Concepts Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-operating-model-and-artifact-concepts` milestone: explain hierarchy, planning depth, roles, metadata, evidence, and ownership concepts. - 02 Intake To Implementation Workflow Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-intake-to-implementation-workflow` milestone: document the verified path from specification intake through planning decomposition, readiness, selection, and task execution. - 03 Evidence Review And Reconciliation Lifecycle Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish and protect the canonical journey from task implementation evidence through review, milestone reconciliation, structural-pressure decisions, and explicit follow-up classification. - 04 Resume Trace Archive And Release Handoff Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-resume-trace-archive-and-release-handoff` milestone: document resumability, trace-link lifecycle, archival, recovery, and release handoff through role-based scenarios. - 01 Prompt And Template Catalogs Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish a canonical public reference catalog for every shipped prompt and template, grounded in the workspace manifests and linked to the lifecycle stages and command families that consume each asset. - 02 Discovery Rendering And Trust Boundaries Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish the operational companion to the completed prompt/template catalog: explain prompt lookup and fallback, rendering lanes, template routing, agent-entrypoint trust, degraded modes, and the evidence-versus-write boundary without expanding into the detailed customization and upgrade procedures owned by later milestones. - 03 Workspace Customization Workflows Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-workspace-customization-workflows` milestone: document seeding, listing, editing, updating, materialization, review, validation, and ownership boundaries. - 04 Upgrade Merge And Drift Maintenance Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish and regression-protect a canonical guide for upgrading prompt and template customizations: establish release/workspace/base evidence, classify drift, preserve user intent through an explicit three-way merge, and recover safely from force, manifest, stale-copy, and partially upgraded workspace failures. - 01 Command And Capability Inventory Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish a mechanically derived command-and-capability inventory that gives the remaining phase a complete, authoritative coverage baseline for every callable Day Shift surface. - 02 Core Workflow Command Reference Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish the detailed reference for Day Shift's core lifecycle commands, grounded in the completed 140-command inventory and organized around the work users perform. - 03 Operational And Administration Reference Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish the detailed operational and administration command reference for configuring, diagnosing, maintaining, migrating, resuming, and releasing Day Shift workspaces. - 04 Structured Automation And Extension Contracts Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Publish the structured automation protocol and extension contract, including machine-readable output, bounded retrieval, failures, registration architecture, design rationale, and safe command contribution. - 01 Page Disposition And Substance Closure Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-page-disposition-and-substance-closure` milestone: implement every page disposition and eliminate empty, placeholder-only, unresolved, or misleading public surfaces. - 02 Product Surface Coverage Verification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-product-surface-coverage-verification` milestone: reconcile onboarding, lifecycle, command, prompt, template, architecture, decision, and contribution coverage with authoritative inventories. - 03 Example Link And Troubleshooting Verification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-example-link-and-troubleshooting-verification` milestone: execute examples and verify cross-links, role journeys, scenario paths, and recovery guidance. - 04 Continuous Documentation Drift Gates Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-continuous-documentation-drift-gates` milestone: add reproducible, actionable checks for canonical pages, shipped assets, runtime descriptors, examples, and generated public artifacts. - 01 Command Family Contract Reconciliation - Completed. All declared task implementation summaries are complete, implementation-summary review found sufficient closeout evidence for each task, and milestone acceptance criteria are satisfied for the first-pass command-family contract. - Introduce the first-pass `day-shift version ...` command family under the existing `day-shift` executable. This milestone establishes command ownership, argument shape, output envelopes, and offline fail-closed behavior for command surfaces whose deeper install, selection, uninstall, and network semantics are implemented in later phases. - 02 Shim Dispatch Runtime Reconciliation - Completed. All declared tasks are complete, implementation-summary review found sufficient closeout evidence, and dispatch runtime acceptance criteria are satisfied. - Implement the runtime boundary that lets the stable `day-shift` shim distinguish manager-owned commands from managed CLI invocations and dispatch normal CLI execution to a selected installed package without recursive self-dispatch. - 03 Runtime Diagnostics Reconciliation - Completed. All declared tasks are complete, implementation-summary review found sufficient evidence, and runtime diagnostic acceptance criteria are satisfied. - Provide clear, actionable diagnostics for the first-pass version-manager runtime, covering missing selected versions, malformed metadata, unsupported managed package roots, PATH conflicts, recursion hazards, and invocation context. - 01 State Root And Layout Reconciliation - Completed. All declared task implementation summaries are complete, implementation-summary review found sufficient closeout evidence for each task, and the milestone acceptance criteria are satisfied. - Implement the durable version-manager state-root contract that later install and selection work can share. This milestone defines the platform-specific state root, creates the inspectable `version-manager/` directory layout, and records enough layout evidence for doctor and install code to use without mutating package versions yet. - 02 Local Source Install Validation Reconciliation - Completed. All declared task implementation summaries are complete, implementation-summary review found sufficient closeout evidence for each task, and local install-source validation acceptance criteria are satisfied. - Implement local install-source validation for Day Shift package payloads before any managed version state is mutated. - 03 Managed Version Write Path Reconciliation - Completed. All declared task implementation summaries are complete, implementation-summary review found sufficient closeout evidence for each task, and managed version write-path acceptance criteria are satisfied. - Implement the target-scoped managed version write path that installs or replaces one validated exact Day Shift version and records durable metadata/receipt evidence. - 01 Resolution Precedence Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, and the combined evidence satisfies this milestone's resolver and `version current` diagnostics scope. - Implement the core installed-version selection resolver and diagnostics for the required precedence chain. This milestone establishes the shared resolution model that later repository-pin and alias milestones extend. - 02 Repository Pins And Config Defaults Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, including the added pin-write task discovered from phase acceptance criteria. - Implement repository-scoped version selectors for `.day-shift-version`, `.day-shift/local.toml`, and `.day-shift/config.toml` so project-specific selection participates in the resolver before global aliases or fallback. - 03 Aliases And Partial Selectors Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, and the combined evidence satisfies alias mutation, alias selection, partial selector, and `latest-installed` scope. - Implement local alias selection and deterministic local selector expansion for the version manager. This milestone completes the configured selector chain after repository sources and adds explicit alias mutation. - 01 Targeted Uninstall Contract Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, and the milestone evidence satisfies the targeted uninstall validation, target-only removal, and focused coverage scope. - Implement the first concrete uninstall surface for the version manager: reject targetless uninstall requests, accept one explicit exact installed-version target, and remove only that target's managed package state and target-specific version-manager records. - 02 Selector Impact And Replacement Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, and the milestone evidence satisfies affected-selector reporting, replacement, confirmation, and preservation behavior. - Prevent targeted uninstall from silently leaving the active shim selection unusable by detecting selectors that point at the uninstall target and requiring either explicit confirmation or a safe exact-version replacement. - 03 License Preservation And Coverage Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, and the milestone evidence satisfies license preservation and per-installed-version coverage reporting. - Preserve authoritative license and purchase state during version uninstall, and expose non-secret per-installed-version license coverage summaries using existing offline release-line license resolution. - 01 List Current And Doctor Output Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for all tasks, and validation evidence satisfies the milestone's list/current/doctor inspection scope. - Expose local version-manager inspection output that explains installed versions, the active selection decision, state paths, license coverage, and first-pass PATH/runtime diagnostics without using the network. - 02 Approval Gated Network Check Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for all tasks, and validation evidence satisfies the approval-gated network-check scope. - Implement `day-shift version check --network` as an explicit approval-gated availability lookup against Day Shift-owned release metadata while preserving offline local workflows and user-managed aliases. - 03 Cross Platform Path Diagnostics Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for all tasks, and validation evidence satisfies the cross-platform path diagnostics scope. - Validate macOS, Linux, Windows, and WSL version-manager paths and install-source normalization so cross-platform failures are explicit, local, and safe. - 01 Runtime Selection Regressions Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for each task, and the combined evidence satisfies the runtime selection regression scope. - Prove the already implemented runtime selection behavior with focused regression coverage for side-by-side installed versions, shim dispatch, exact-version execution, selector precedence, aliases, partial selectors, and repository pins. - 02 Install Uninstall License Regressions Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for each task, and the combined evidence satisfies install, uninstall, selector-impact, and license regression scope. - Prove install, replacement, uninstall, selector-impact, and license-preservation behavior with regression coverage that reflects the release-line license contract and local offline workflows. - 03 Diagnostics And Release Handoff Reconciliation - Completed. Every declared task has a completed non-placeholder implementation summary, implementation-summary review passed for each task, and the combined evidence satisfies diagnostic, network/path, and release-handoff regression scope. - Prove diagnostics, offline/network boundaries, cross-platform path behavior, and release-handoff assumptions before treating the version manager as releasable. - 01 Revision And Evidence Inventory Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Freeze the repository state inspected by the EADL qualification analysis and produce a coverage-controlled evidence inventory that later phases can cite without confusing discovery matches, implementation evidence, and unavailable evidence. - 02 Implemented Repository Model Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Produce an implementation-grounded model of Day Shift's domain, artifacts, execution, lifecycles, persistence, and human/agent roles using the frozen revision and evidence inventory from milestone 1. - 01 Thirteen Criterion Evidence Matrix Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Evaluate all thirteen EADL criteria against the frozen repository evidence, using the specification's controlled status taxonomy and citation discipline to produce one qualification matrix without over-crediting terminology, documentation, prompts, or configuration. - 02 Representative Workflow Trace Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Trace the implemented `link materialize --write` planning workflow from operator trigger through validation and filesystem outcome, mapping every proposed EADL stage to concrete persisted evidence or an explicit gap and evaluating reconstruction, repetition, and reproduction boundaries. - 01 Classification And Qualification Boundary Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-classification-and-qualification-boundary` milestone: select and justify the classification, confidence, alternative category, qualification gaps, and minimum coherent boundary from the completed evidence. - 02 Ten Section Report Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-ten-section-report` milestone: assemble and quality-check the required report, evidence matrix, trace analysis, conditional canonical model, and exact final-verdict fields. - 01 Milestone Scaffold Inheritance Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and review-clean; the milestone acceptance criteria are satisfied with the validation evidence recorded below. - Make `milestone new` generate parent-derived milestone contracts for well-declared phase milestones, replacing generic placeholder bodies with conservative scaffold intelligence while preserving exact parent upstream metadata. - 02 Task Scaffold Inheritance Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and review-clean; the milestone acceptance criteria are satisfied with the validation evidence recorded below. - Make `task new` generate implementation-ready task drafts from well-declared milestone contracts, using milestone acceptance criteria, dependencies, validation focus, and task declarations as bounded evidence. - 03 Upstream Metadata Preservation Reconciliation - Completed. The declared task implementation summary is completed, non-placeholder, and review-clean; the milestone acceptance criteria are satisfied with the validation evidence recorded below. - Verify and harden exact upstream metadata and parent-link preservation across generated milestone and task artifacts. - 01 Active Evidence Warning Downgrade Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and sufficient for this milestone. - Implement the `01-active-evidence-warning-downgrade` milestone: use current parent, task, and reconciliation evidence to downgrade repeated stale-source or message-source warnings. - 02 Declared Later Work Classification Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and sufficient for this milestone. - Implement the `02-declared-later-work-classification` milestone: classify later declared milestone or phase work separately from unresolved residual concerns in reconciliation review. - 03 Actionable Review Findings Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and sufficient for this milestone. - Implement the `03-actionable-review-findings` milestone: tighten review finding wording so warnings and errors point to the exact artifact or explicit follow-up command. - 01 Implementation Summary Build Closeout Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone acceptance criteria are satisfied by the recorded implementation and validation evidence. - Improve `implementation-summary build` so completed task evidence can produce a closeout-ready paired `implementation-summary.md` instead of a heading-only refresh that still requires predictable boilerplate replacement. - 02 Reconciliation Build Closeout Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Improve `reconciliation build` so it can produce completed, review-clean milestone reconciliation language when every declared task summary is completed, non-placeholder, and evidence-sufficient. - 03 Explicit Status Metadata Sync Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Extend the explicit `metadata sync-status-from-review` write command so deterministic milestone and phase status metadata recommendations can be applied with active-artifact guard support. - 01 Task Scope Change Report Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-task-scope-change-report` milestone: produce a focused changed-path report for declared task target paths, including tracked and untracked files. - 02 Path Category Classification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-path-category-classification` milestone: classify source, generated, planning, and unrelated paths in task-scope evidence. - 03 Summary Closeout Evidence Feed Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-summary-closeout-evidence-feed` milestone: integrate task-scoped changed-path evidence into implementation-summary build or closeout guidance. - 01 Command Family Regression Update Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-command-family-regression-update` milestone: revise help and command-family tests toward durable presence, posture, and boundary assertions. - 02 Workflow Guidance Alignment Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-workflow-guidance-alignment` milestone: update workflow, prompt, template, and reference guidance for the new lifecycle-friction behavior. - 03 Release Handoff Evidence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-release-handoff-evidence` milestone: prepare validation, changed-path, and release-note evidence for the completed slice. - 01 Command Surface Inventory Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-command-surface-inventory` milestone: generate and review a complete inventory of available CLI commands, command families, options, write posture, and intended lifecycle use. - 02 Guidance Command Adoption Map Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-guidance-command-adoption-map` milestone: map inventoried commands to prompts, references, workflows, templates, and lifecycle guides where command use should replace inference-heavy or manual steps. - 03 Prompt Reference Workflow Alignment Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-prompt-reference-workflow-alignment` milestone: update prompts, references, workflows, and lifecycle guides to prefer available command surfaces, preserve read-only/write boundaries, and record command gaps explicitly. - 04 Adoption Validation And Gap Report Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-adoption-validation-and-gap-report` milestone: validate the updated guidance, document remaining unsupported command gaps, and produce release-ready evidence for the command-adoption audit. - 05 Machine Readable Command Inventory Export Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `05-machine-readable-command-inventory-export` milestone: build a machine-readable command inventory export that combines callable Commander-tree evidence with command capability registry metadata, exposes it through an explicit `commands inventory` command, and verifies coverage gaps. - 01 Materialization Command Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Define the Markdown link materialization command contract before implementation work adds source locations, rewrite mechanics, and CLI execution. This milestone establishes the command family, options, posture metadata, output fields, dry-run semantics, write boundary, rollback language, and relationship to the read-only `validation links-check` surface. - 02 Body Reference Source Locations Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Extend the existing validation link discovery evidence for body-section references with occurrence-level source locations while preserving the current read-only `validation links-check` behavior and existing `traceFields[].values` compatibility. - 03 Markdown Link Rewrite Engine Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement a reusable Markdown body rewrite engine that converts validated plain local references into Markdown links using source-location evidence, while skipping existing links, front matter, fenced code, inline code, duplicate/overlapping candidates, and unsafe source mismatches. - 04 Cli Integration And Guidance Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Wire the `link materialize` command to the source-location and rewrite-engine helpers for real dry-run preview and selected-artifact write execution, then update command guidance so agents use `validation links-check` evidence before materialization. - 05 Regression And Validation Coverage Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `05-regression-and-validation-coverage` milestone: add focused unit and CLI tests for preview, writes, skipped candidates, no-write validation behavior, and rollback evidence. - Audience Marker Inventory Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. The milestone acceptance criteria are satisfied by the inventory, classification, and traceability evidence in the completed task summaries. - Inventory the repository-local onboarding, workflow, agent, prompt, template, and reference surfaces that need clearer audience or responsibility markers before any human-workflow cleanup removes or shortens existing guidance. - Human Agent Boundary Mapping Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. The milestone acceptance criteria are satisfied by the completed boundary map and the task evidence. - Map agent-focused guidance that currently appears in human workflow surfaces to its verified agent, prompt, template, or reference destination before any cleanup removes it from the human documentation path. - Prompt Template Reference Boundaries Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Clarify the responsibilities of prompt, template, and reference surfaces so downstream workflow cleanup can point to durable homes for prompt instructions, artifact shapes, command references, metadata references, validation guidance, and planning-layer relationships. - Reference And Marker Materialization Reconciliation - Completed. All declared task implementation summaries are present, completed, non-placeholder, and reviewed with sufficient closeout evidence. - Create the reference destinations and visible audience or responsibility markers needed to close the remaining phase-level gaps before the audience and responsibility separation phase can be marked complete. - Command Registry And Metadata Reference Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Create or revise canonical command, spec registry, and metadata reference material so later workflow cleanup can replace repeated command and metadata explanations with durable links. - Prompt Template Validation Reference Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed. The combined evidence satisfies the milestone intent and acceptance criteria. - Create or revise canonical prompt, template, validation, review, and structural-pressure reference material so workflow docs can shorten repeated policy detail without losing ownership or mutation boundaries. - Planning Layer Relationship Reference Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed. The combined evidence satisfies the milestone intent and acceptance criteria. - Document the planning-layer relationships from specification through reconciliation so procedural workflow docs can link to a canonical model for producers, consumers, dependencies, expected outputs, and evidence handoffs. - Human Workflow Routing Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and populated with task evidence; milestone acceptance was reviewed against those task summaries and the focused validation evidence. - Clarify the main human workflow routing entrypoints so new-project, existing-repository, and ongoing planning readers can choose the correct next document without parsing agent-facing execution instructions. - First Project Guide Refinement Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, non-placeholder, and sufficient for milestone reconciliation. - Refine the existing first-project walkthrough so a fresh-repository user understands the expected outputs, command sequence, and handoff into the normal planning workflow without treating the guide as missing or newly invented documentation. - Existing Repository Onboarding Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Define the human onboarding path for adopting or resuming Day Shift in an existing repository, with clear read-only discovery, workspace detection, source-spec intake, validation, and migration preview boundaries. - Workflow Input Output Handoffs Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking issues, warnings, or metadata-hygiene follow-ups. - Document the expected inputs, actions, outputs, and downstream consumers for Day Shift planning, implementation, and reconciliation workflows so handoff cleanup can happen without losing operational context. - Evidence Source Navigation Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking issues, warnings, or metadata-hygiene follow-ups. - Route workflow readers to concrete source specs, planning artifacts, implementation summaries, reconciliation artifacts, review findings, and validation output so evidence stays inspectable instead of being replaced by status-only summaries. - Read Only Discovery Command Guidance Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. - Clarify how read-only discovery and validation commands help readers navigate planning evidence without authorizing writes, replacing evidence artifacts, or implying automatic repair. - Stale CLI Wording Cleanup Reconciliation - Completed. Both declared task summaries are completed, non-placeholder, and reviewed; milestone acceptance is satisfied by the audit and correction evidence recorded below. - Audit and correct documentation that still describes implemented Day Shift CLI surfaces as unavailable, future-only, manual-only, or unsupported, while preserving any useful operational guidance in the right workflow or reference home. - Duplication And Canonical Link Cleanup Reconciliation - Completed. Both declared tasks have completed, non-placeholder implementation summaries, the audit-to-rewrite sequence was preserved, and milestone-level validation passed after one prompt-lane wording repair. - Reduce duplicated documentation explanations by replacing repeated prose with concise links to canonical workflow or reference homes after those homes exist and contain the guidance readers still need. - Compatibility And Validation Pass Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed; milestone acceptance is satisfied by the compatibility repair and focused validation evidence recorded below. - Preserve compatibility links, prompt and template references, and planning traceability after documentation cleanup, then run focused validation on changed artifacts without broad unrelated repository rewrites. - Command Capability Registry Reconciliation - Completed. All three declared task implementation summaries are completed, reviewed, non-placeholder, and sufficient for milestone closure. - Define one inspectable command capability registry that classifies Day Shift command surfaces by read, validation, review, navigation, scaffold, update, build, sync, migration, install, materialize, and related write-capable posture so runtime output, help/reference surfaces, and regression tests consume the same source of command metadata. - Read Only Boundary Reporting Reconciliation - Completed. All declared task summaries are completed and non-placeholder, implementation-summary reviews reported sufficient evidence with no findings, and milestone acceptance criteria are satisfied with the recorded residual follow-up noted below. - Standardize no-write boundary reporting for read-only command families so review, validation, inventory, next-action, explain, list, and inspection surfaces report evidence-only behavior and recommend explicit write commands without mutating artifacts in the same pass. - Command Posture Regression Tests Reconciliation - Completed. The three declared task implementation summaries are completed, reviewed, and sufficient for milestone closure. - Add regression coverage that compares command capability metadata, runtime side effects, and documented command behavior so read-only surfaces remain measurably non-mutating and write-capable surfaces cannot silently broaden their mutation authority. - Source Spec And Planning Advancement Gates Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking implementation-summary findings. - Implement deterministic gates that keep source-spec authoring, source-spec review, hardening, and second-pass requests at the specification and registry layer unless the selected command or user request explicitly advances into planning. - Create Revise And Selected Artifact Boundaries Reconciliation - Completed. The declared task implementation summaries are complete, reviewed, and sufficient for milestone closure. - Enforce canonical create behavior, selected-artifact revise behavior, artifact-scoped validation boundaries, and no same-pass downstream creation across planning scaffold and update command families. - Linked Slice Parent Traceability And Conflicts Reconciliation - Completed. All declared task summaries are completed, reviewed, and non-placeholder; milestone acceptance has been reconciled against task evidence. - Validate linked-slice registry targets, explicit parent overview traceability, required scaffold companion artifacts, manual-exception metadata, and active-artifact conflicts before write-capable planning commands mutate repository state. - Artifact Family Parser And Shape Rules Reconciliation - Completed. All declared task implementation summaries are present, completed, non-placeholder, and review-clean. Milestone reconciliation accepts the implemented artifact-family parser, shape validator, and selected-artifact validation smoke reporting as satisfying the milestone scope. - Centralize artifact-family identification and mechanically knowable shape validation so planning, prompt, template, workflow, reference, summary, reconciliation, manifest, and scaffold surfaces can be parsed and checked through one deterministic contract. - Prompt Template Manifest And Scaffold Lanes Reconciliation - Completed. All three declared task summaries are present, non-placeholder, and marked completed. Milestone acceptance was reviewed against the completed task evidence and targeted validation results. - Enforce prompt, template, manifest, and scaffold validation lanes as separate family-aware surfaces so cross-family references, destination routing, and update attempts are checked without lossy normalization. - Trace Link And File Scoped Validation Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Validate explicit upstream spec links, parent planning links, local reference resolution, and selected-artifact validation scope while preserving validation as read-only evidence rather than a repair or recursive cleanup mechanism. - Implementation Summary Evidence Review Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient closeout evidence. - Review implementation summaries as completed closeout evidence by checking changed paths, task-summary traceability, deviations, validation evidence, and acceptance-result specificity against the originating task definitions. - Lifecycle Status Coherence Reconciliation - Completed. The three declared task implementation summaries are complete, non-placeholder, and reviewed; milestone acceptance criteria are satisfied with the residual caveats recorded below. - Validate status and lifecycle coherence across task definitions, implementation summaries, reconciliation artifacts, parent child declarations, and metadata update surfaces without normalizing wrong-family fields. - Reconciliation Eligibility Gates Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and sufficient for milestone rollup. - Gate milestone reconciliation on declared tasks with completed, non-placeholder, current implementation summaries and sufficient validation evidence, while preserving task-level reconciliation as an explicit exception path. - Planning Language And Decomposition Warnings Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with sufficient closeout evidence. - Implement shared warning-level planning language and decomposition checks that catch ambiguous deliverables, weak task shape, stale planning context, and shallow dependency or target-path evidence without blocking valid contract-setting work. - Lightweight Promotion Pressure Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed with no blocking findings. Remaining validation smoke output is advisory and recorded below. - Detect warning-level pressure that a lightweight planning path has outgrown its boundary, while preserving explicit promotion, scope-split, or documented-remain-lightweight decisions as separate operator choices. - Derived State Sync Eligibility Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for milestone rollup. - Gate structural-pressure and other derived-state sync writers on completed canonical Markdown evidence so JSON state mirrors reconciled planning facts instead of becoming a parallel source of truth. - Finding Taxonomy And Output Guidance Reconciliation - Completed. All declared task implementation summaries are completed and non-placeholder, acceptance criteria were reviewed against task evidence, and milestone reconciliation is ready for read-only review. - Define one shared finding taxonomy and output contract so validation, review, navigation, metadata, reconciliation, prompt, template, manifest, planning, and structural-pressure commands report equivalent evidence, no-write boundaries, affected paths, and recommended next commands. - Workflow Prompt Reference Alignment Reconciliation - Completed. The milestone has been reviewed against all three completed, non-placeholder task implementation summaries and the recorded validation evidence. - Align workflow, prompt, reference, template, manifest, and command-help guidance with the implemented enforcement surfaces so prose points to executable command contracts without creating contradictory same-pass repair or cross-family write instructions. - Cross Family Regression Coverage Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, reviewed, and sufficient for milestone closure. - Add regression coverage across command families and artifact families so command posture, lifecycle gates, validation findings, closeout review, reconciliation eligibility, heuristic warnings, derived-state sync, documentation guidance, and no-write side effects do not drift after enforcement behavior is implemented. - Destination Contract And Compatibility Policy Reconciliation - Completed. The milestone has completed task implementation summaries, sufficient task-summary review evidence, and targeted validation for the overview filename destination contract, compatibility behavior, shared inference, and no-write conflict reporting. - Settle the planning overview filename policy before implementation changes fan out across scaffold, navigation, validation, documentation, and compatibility surfaces. - Scaffold Navigation And Link Resolution Reconciliation - Completed. All four declared task implementation summaries are completed, non-placeholder, and reviewed or validated with no blocking findings. - Apply the selected overview filename policy to write-capable scaffolds and read-only planning traversal surfaces so generated artifacts, parent links, validation, review, and navigation resolve paths consistently. - Docs Templates And Regression Coverage Reconciliation - Completed. All declared task summaries are completed, non-placeholder, reviewed, and reconciled. - Align operator guidance, template identity, manifest metadata, command help, packaging behavior, and regression coverage with the selected layer-specific overview filename contract. - 01 Execution Mode Metadata Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-execution-mode-metadata` milestone: add required mode metadata to task and summary artifacts with strict allowed values. - 02 Runtime Delta Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-runtime-delta-contract` milestone: add Runtime Delta requirements for runtime and hybrid tasks while documenting contract-mode non-applicability. - 03 Contract Closeout Boundary Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-contract-closeout-boundary` milestone: specify how contract tasks close without satisfying pending runtime acceptance criteria. - 01 Default Doc Path Classifier Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the default documentation-only path classifier used by runtime evidence gates. This milestone establishes conservative, repository-relative classification primitives only; repository-specific overrides, changed-path collection, and Runtime Delta target comparison remain owned by later milestones in this phase. - 02 Repository Path Policy Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the repository path policy layer that lets a repository add documentation-only path prefixes and declare explicit runtime-eligible exceptions without weakening the default classifier shipped by milestone 01. - 03 Changed Path Evidence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement changed-path evidence for runtime gate consumers by classifying task-scoped and summary-authored changed paths as documentation-only or runtime-eligible. - 04 Runtime Target Alignment Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Compare runtime/hybrid implementation-summary changed paths with declared Runtime Delta targets, and require explicit deviation evidence when changed paths replace or differ from declared targets. - 01 Task Readiness Mode Gates Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-task-readiness-mode-gates` milestone: reject invalid execution modes and incomplete Runtime Delta before implementation handoff. - 02 Summary Closeout Gates Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-summary-closeout-gates` milestone: enforce changed-path, runtime-target, validation-evidence, and summary-language blockers. - 03 Reconciliation Runtime Evidence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-reconciliation-runtime-evidence` milestone: require runtime evidence in reconciliation for runtime and hybrid tasks. - 04 Validation Exception Policy Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-validation-exception-policy` milestone: implement structured validation exceptions without allowing them to replace runtime code changes. - 01 Contract To Runtime Handoff Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Milestone verdict: accepted for phase progression. The milestone satisfies its declared contract-to-runtime handoff scope, with no blocking residual work. - Add read-only planning review evidence that prevents the first runtime or hybrid task after contract work from advancing without a visible frozen-contract evidence reference. - 02 Documentation Loop Detection Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary, implementation-summary review reported sufficient closeout evidence, and the milestone evidence is ready for reconciliation review. - Milestone verdict: accepted for phase progression. Documentation-loop detection is implemented as read-only milestone and phase review evidence, with no automatic task creation or planning mutation. - Add read-only milestone and phase review detection for repeated documentation-only completed task summaries when runtime acceptance criteria remain pending. - 03 Breakout Task Requirement Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary, implementation-summary review reported sufficient closeout evidence, and the milestone evidence is ready for reconciliation review. - Milestone verdict: accepted for phase progression. Breakout task requirements after documentation-only loops are implemented as read-only review evidence. - Require the task immediately following a detected documentation-only loop to be an explicitly ready runtime or hybrid breakout task with Runtime Delta evidence and a frozen-contract evidence link. - 04 Phase And Milestone Review Alignment Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary, implementation-summary review reported sufficient closeout evidence, and the milestone evidence is ready for reconciliation review. - Milestone verdict: accepted for phase progression. Phase and milestone review evidence is aligned through shared read-only planning-review issue collectors and focused phase-review regression coverage. - Align phase and milestone review evidence for handoff, documentation-loop, and breakout blockers while preserving read-only/no-write boundaries. - 01 Template Mode And Delta Content Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Milestone verdict: accepted for phase progression. Template and generated-summary contracts now expose validation exceptions and runtime-evidence boundaries, and focused regression coverage proves the updated contract surface. - Implement the `01-template-mode-and-delta-content` milestone: update task and summary templates with mode and Runtime Delta requirements. - 02 Prompt And Workflow Guidance Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary. Milestone verdict: accepted for phase progression because workflow and prompt guidance now preserve execution-mode evidence, Runtime Delta expectations, structured validation exceptions, and evidence-only review boundaries. - Implement the `02-prompt-and-workflow-guidance` milestone: align prompts and workflows with mode-aware runtime evidence gates. - 03 Command Output Guidance Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-command-output-guidance` milestone: surface blockers, exceptions, and no-write boundaries in command output. - 04 Portable Policy Pack Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-portable-policy-pack` milestone: package reusable policy, template content, validator behavior, and CI examples. - 01 Mode And Delta Regressions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Prove execution-mode and Runtime Delta regression behavior across task readiness and implementation-summary closeout reviews. - 02 Classifier And Evidence Regressions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Prove path classification, repository runtime exceptions, changed-path evidence, and Runtime Delta target alignment with focused regression tests. - 03 Review Gate Regressions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Prove review-gate blockers and valid contract success paths with focused regression tests for runtime closeout evidence, validation exceptions, reconciliation review, documentation-loop detection, and mode-aware verb policy. - 04 Ci Policy Enforcement Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Prove provider-neutral CI enforcement examples call reusable Day Shift validation and review behavior without coupling the policy pack to one hosted CI provider. - 01 Build Related Spec Coverage Matrix Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-build-related-spec-coverage-matrix` milestone: map every related-spec requirement to evidence, an explicit disposition, and any replacement spec 22 requirement identifier. - 02 Recertify Linkage And Lifecycle Evidence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-recertify-linkage-and-lifecycle-evidence` milestone: repair spec 15 linkage, synchronize spec 20 lifecycle evidence, and rerun focused reviews for all archival candidates. - 03 Record Closeout And Archive Eligible Specs Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-record-closeout-and-archive-eligible-specs` milestone: record independent closeout verdicts and use supported archival commands only for specifications whose gates pass. - 01 Define Protocol Version And Feature Negotiation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-define-protocol-version-and-feature-negotiation` milestone: establish protocol identity, capability discovery, compatibility windows, and deprecation rules. - 02 Establish Canonical Schema Catalog Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-establish-canonical-schema-catalog` milestone: specify authoritative schemas and representative positive, negative, recursive, and union fixtures. - 03 Integrate Runtime Validation And Generated Types Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-integrate-runtime-validation-and-generated-types` milestone: connect Ajv validation and generated TypeScript to command output without creating dual authorities. - 01 Implement Detail Grouping And Filter Contracts Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-implement-detail-grouping-and-filter-contracts` milestone: add explicit detail modes, stable grouping, filters, and per-lane limits. - 02 Add Deterministic Pagination And Completeness Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-add-deterministic-pagination-and-completeness` milestone: specify stable cursors, continuation metadata, stale-cursor rejection, and snapshot consistency. - 03 Enforce Output Budgets And Bounded Failures Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-enforce-output-budgets-and-bounded-failures` milestone: apply representative byte budgets and preserve valid, actionable envelopes under limits and errors. - 01 Establish Authoritative Command Descriptor Registry Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish one typed command-descriptor registry as the source of truth for command identity, invocation metadata, effects, authorization, selection requirements, transitions, and examples. - 02 Deliver Focused Discovery And Tool Manifests Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Deliver bounded command discovery and descriptor-derived tool manifests without requiring consumers to load or scrape the full command inventory. - 03 Add Structured Input And Drift Validation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Add shell-equivalent structured requests for migrated discovery commands and enforce descriptor-to-Commander drift checks before additional command families migrate. - 01 Deliver Actionable Candidate Discovery Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Expose bounded, deterministic planning-work candidates with enough evidence for an operator or agent to choose deliberately, while keeping candidate discovery read-only and advisory. - 02 Implement Local Selection Lifecycle And Precedence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement a user-local, named-session work-selection lifecycle that persists until explicitly cleared, reports stale artifact evidence, and resolves direct artifact input without allowing hidden stored state to silently redirect an invocation. - 03 Protect Selection State With Concurrency Evidence Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Protect user-local selection mutations with opaque revision preconditions and lock-serialized compare-and-write behavior so concurrent or stale callers cannot silently overwrite a named session. - 01 Deliver Artifact Scoped Agent Context Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Deliver a bounded `agent context` surface that resolves one explicit or stored planning-artifact selection into trustworthy lifecycle state, action-relevant blockers, descriptor-backed permitted actions, and one exact recommended action. - 02 Build Relevance Ranked Context Packs Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Build an optional artifact-context pack that converts explicit planning traceability, declared implementation paths, dependency and validation references, and recent implementation evidence into deterministic, trust-labeled, bounded excerpts. - 03 Integrate Budget Freshness And Exclusion Reporting Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Complete context-pack safety with caller-selected byte budgets, per-entry freshness, deterministic budget trimming, labeled heuristic evidence, and explicit missing, stale, or budget-excluded candidate reports. - 01 Separate Health Domains And Command Surfaces Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish explicit runtime/setup, selected-artifact, planning-scope, and repository-audit health domains, then expose them through bounded read-only doctor command surfaces without changing the authoritative repository-wide default. - 02 Classify Action Relevant Blockers Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Bind health and validation findings to one descriptor-backed selected action through conservative, explicit relevance evidence so artifact-local work stops for applicable safety failures without inheriting unrelated repository history. - 03 Integrate Scoped Health With Context And Validation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Integrate scoped health and descriptor-backed relevance evidence into artifact context and focused planning validation so agents receive complete current-action blockers without weakening explicit repository-wide release, migration, or audit gates. - 01 Model Executable Workflow State And Actions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement one executable workflow-action model that combines authoritative command descriptors with current artifact evidence so automation consumers can distinguish legal, blocked, and non-callable transitions without reconstructing commands or inferring completion. - 02 Standardize Typed Failures And Recovery Actions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Standardize every terminal automation failure around a typed category, exit classification, retryability decision, write outcome, and bounded executable recovery actions that preserve the milestone 01 authorization and transition contract. - 03 Add Evidence Backed Resume Capsules Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement user-local, inspectable resume capsules that preserve bounded workflow progress and permit resumption only while selection, evidence hashes, and recorded postconditions still match current repository state. - 01 Establish Atomic Single File Write Primitive Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish one reusable synchronous primitive for replacing a single file without exposing partially written destination content, with durable best-effort flush behavior and deterministic temporary-file cleanup. - 02 Deliver Multi File Plans Preconditions And Receipts Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Build a shared synchronous coordinator for deterministic multi-file mutation plans on top of `atomicWriteFileSync`, rejecting stale evidence before the first write whenever the complete plan can be prevalidated and returning truthful path-level hash evidence for every outcome. - 03 Add Locking Rollback And Crash Recovery Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Protect shared filesystem state with portable renewable leases, identity-safe rollback, and atomic journal evidence so interrupted coordinated mutations can be classified and recovered deterministically without overwriting newer work. - 01 Establish Canonical Policy Rules And Composition Reconciliation - Accepted. Every declared runtime task has a completed, non-placeholder implementation summary, executable evidence is sufficient, and manual acceptance review found no blocker or unresolved concern. - Establish one runtime contract for stable canonical policy rule identifiers, task-specific policy deltas, fail-closed rule resolution, and compact prompt-policy assembly without pulling later trust-lane, adversarial-injection, or cross-surface redaction work into this milestone. - 02 Enforce Trust Lanes And Prompt Injection Boundaries Reconciliation - Accepted. Every declared runtime task has a completed, non-placeholder implementation summary, executable evidence is sufficient, and manual acceptance review found no blocker or unresolved concern. - Introduce a shared structural trust-lane vocabulary and expose it on prompt rendering, artifact context packs, workflow explanation, and resume evidence so repository-authored or external prose remains data and cannot become policy, user intent, command authorization, or confirmation evidence. - 03 Unify Authorization Redaction And Sanitization Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Complete the Phase 10 trust boundary with one fail-closed action-posture contract and one safe-by-default output policy. Every callable action must expose filesystem, network, host-state, destructive, interactive, authorization, and confirmation posture from authoritative command descriptors, while sensitive or host-specific values and terminal control sequences are handled consistently wherever automation evidence is rendered or persisted. - 01 Define Constrained Profile And Readiness Gates Reconciliation - Accepted. Every declared runtime task has a completed, non-placeholder implementation summary and executable evidence satisfies the milestone contract. - Implement a vendor-neutral constrained execution profile and deterministic readiness evidence that fails closed on missing prerequisites while keeping heuristic sizing separate. - 02 Add Advisory Task Sizing And Decomposition Reconciliation - Accepted. Every declared runtime task has complete executable evidence and the advisory/no-write boundaries are verified. - Add explainable complexity signals and safe advisory recommendations for decomposition or explicit profile escalation. - 03 Integrate Profile Decisions And Calibration Hooks Reconciliation - Accepted. Every declared runtime task has complete executable evidence and later evaluation ownership remains explicit. - Preserve explicit profile, decomposition, escalation, and rollback decisions as versioned evidence suitable for later evaluation and threshold calibration. - 01 Characterize And Build Shared Artifact Parser Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Preserve the observable behavior of existing planning Markdown parsers, then introduce one typed, lossless artifact-document seam that later milestones can adopt incrementally. - 02 Migrate Planning And Validation Callers Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Migrate the highest-value planning and validation consumers to the shared artifact-document seam while preserving their public diagnostics, source locations, path text, and Markdown fidelity. - 03 Decompose Command Adapters And Priority Hotspots Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Consolidate command-descriptor projection adapters and extract cohesive seams from the agent-orientation and doctor orchestration hotspots without changing their CLI contracts. - 01 Implement Incremental State And Freshness Indexing Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-implement-incremental-state-and-freshness-indexing` milestone: track source identity, generated evidence hashes, supersession, and stale or incomplete state. - 02 Add Cache Lifecycle And Bounded Decision Traces Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-add-cache-lifecycle-and-bounded-decision-traces` milestone: provide deterministic invalidation, inspection, cleanup, and privacy-safe trace evidence. - 03 Establish Performance Benchmarks And Regression Gates Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-establish-performance-benchmarks-and-regression-gates` milestone: measure cold and warm work, output, memory, scans, and latency across representative workflows. - 01 Build Deterministic Trajectory Harness Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-build-deterministic-trajectory-harness` milestone: create fixture-driven mock-agent workflows and hard safety invariant checks. - 02 Add Adversarial Corpus And Payload Budgets Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-add-adversarial-corpus-and-payload-budgets` milestone: exercise trust, authorization, stale evidence, failures, output limits, and recovery under measured context budgets. - 03 Calibrate Real Model Baselines And Promotion Gates Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Add a provider-neutral, explicit opt-in calibration layer that evaluates versioned held-out trajectory evidence from independently implemented models and produces an auditable promotion decision without making networked model execution part of ordinary CI. - 01 Tests V2 Structure And Scripts Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and sufficient for this milestone's structure-and-script baseline. - Create the initial `tests_v2/` placement boundaries and package-script entrypoints required before helper behavior or migrated CLI smoke coverage can be added. - 02 Subprocess Helper Contract Reconciliation - Completed. Both declared helper tasks are completed, reviewed, and sufficient for the V2 subprocess helper baseline. - Implement the reusable V2 helper contract for subprocess CLI execution, workspace isolation, fixture setup, and assertions without mutating process-global output streams or the test process working directory. - 03 Representative Smoke Migration Reconciliation - Completed. The representative V2 license status smoke task is completed, reviewed, and sufficient for this baseline migration proof. - Migrate one representative CLI smoke file into `tests_v2/` to prove the V2 helper contract, focused `node --test` execution, and V2 package-script validation before larger command-family migrations begin. - 01 Spec Registry Command Migration Reconciliation - Completed. Task implementation summary evidence, focused validation, and closeout search evidence satisfy the milestone acceptance criteria. - Migrate spec registry command tests for add, list, search, update, and archive from legacy in-process CLI execution into the V2 subprocess suite. - 02 Planning Creation Command Migration Reconciliation - Completed. Task implementation summary evidence and validation satisfy the milestone acceptance criteria. - Migrate planning creation command tests for slice, phase, milestone, task creation, and task promotion into the V2 subprocess suite. - 03 Planning Update Command Migration Reconciliation - Completed. Task implementation summary evidence and validation satisfy the milestone acceptance criteria. - Migrate planning metadata update command tests for slice, phase, milestone, and task update commands into the V2 subprocess suite. - 01 Implementation Summary Command Migration Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient; milestone acceptance criteria are satisfied by the recorded validation evidence. - Migrate implementation-summary build, review, and update command tests from legacy in-process CLI execution into V2 subprocess coverage while preserving paired-artifact behavior and read/write boundaries. - 02 Reconciliation Command Migration Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient; milestone acceptance criteria are satisfied by the recorded validation evidence. - Migrate reconciliation build, review, and update command tests from legacy in-process CLI execution into V2 subprocess coverage while preserving milestone and task-level reconciliation behavior. - 03 Template Completion And Runtime Validation Migration Reconciliation - Completed. All declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient; milestone acceptance criteria are satisfied by the recorded validation evidence. - Migrate template update, completion, and runtime validation command tests into V2 subprocess coverage while preserving command output, read/write boundaries, and validation finding contracts. - 01 Equivalent Coverage Review Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for the equivalent coverage review milestone. - Recertify the legacy CLI command-family inventory against the migrated `tests_v2/` suite and record which legacy files have equivalent V2 evidence, which remain intentionally pending, and which are outside this CLI migration lane. - 02 Legacy Retirement Decisions Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for the legacy retirement decision milestone. - Retire only legacy CLI test files whose equivalent V2 coverage was validated in milestone `01-equivalent-coverage-review`, while preserving retained legacy files and shared helpers that are still needed outside the source migration inventory. - 03 Runner Alignment And Follow Up Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for the runner alignment and follow-up milestone. - Assess whether the validated V2 runner and package-script behavior requires any final alignment after legacy retirement, then record follow-up work for retained helper limitations and out-of-scope legacy validation findings. - 01 Active Guidance Reference Alignment Reconciliation - Completed. Both declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for active guidance reference alignment. - Align active implementation guidance so future CLI migration and test-infrastructure tasks use the V2 validation lane by default while retained legacy validation remains explicitly scoped. - 02 Package Script And Runner Reference Check Reconciliation - Completed. The declared task implementation summary is completed, non-placeholder, and reviewed as sufficient for package-script and runner-reference closeout. - Verify package scripts and runner references after active guidance alignment, preserving the V2 validation lane and retaining legacy runner ownership only where it remains intentionally scoped. - 03 Final V2 Closeout Evidence Reconciliation - Completed. The declared task implementation summary is completed, non-placeholder, and reviewed as sufficient for final V2 closeout. - Run and record final V2 closeout evidence for the CLI test-runner migration, separating migrated V2 validation from retained legacy-suite follow-up. - 04 Retained Cli Family Inventory And Sequencing Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for retained CLI family inventory and sequencing. - Inventory retained legacy CLI test families, classify their migration and cleanup ownership, and establish the execution order for continuing V2 migration beyond the completed source-inventory families. - 05 Retained Cli Subprocess Migration Reconciliation - Completed. All six declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for retained CLI subprocess migration and retirement decisions. - Migrate retained CLI command-family coverage from legacy `tests/cli` into subprocess-first `tests_v2/cli` coverage using the sequencing evidence from milestone `04`. - 06 Init And Lib V2 Migration Reconciliation - Completed. All four declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for init and direct library V2 migration. - Migrate retained init and direct library coverage into `tests_v2/init` and `tests_v2/lib` while preserving the correct test boundary for non-CLI behavior. - 07 V1 Helper Fixture And Runner Cleanup Reconciliation - Completed. All three declared task implementation summaries are completed, non-placeholder, and reviewed as sufficient for helper, fixture, and retained-runner decision evidence. - Clean up legacy-only helper, fixture, and runner dependencies after retained CLI, init, and lib coverage has equivalent V2 evidence. - 08 Final V1 Retirement Evidence Reconciliation - Completed. The milestone recorded final V2 validation, classified every remaining legacy `tests/` path, and retained the legacy runner as an explicit blocker-bound compatibility surface. - Record final evidence for retiring, replacing, or explicitly retaining the legacy `tests/` runner after the remaining V1-to-V2 migration work is complete. - 01 Reviewer Accepted Residual Semantics Reconciliation - Completed. Accepted residual reviewer semantics were inventoried, defined, implemented, and validated with focused reconciliation review coverage. - Plan reviewer behavior that keeps accepted residual work visible without presenting explicitly accepted follow-up evidence as unresolved blocker-like concern. - 02 Planning Command Option Aliases Reconciliation - Completed. The planning gap-report command surface now supports an artifact-focused alias while preserving existing scope behavior. - Plan command-surface improvements for planning validation ergonomics, especially the `planning gap-report --scope` and validation `--artifact` option split. - 03 Reconciliation Build Evidence Quality Reconciliation - Completed. Reconciliation build output now gives cleaner draft rollups without auto-completing reconciliation metadata. - Plan improvements to reconciliation build output so generated rollups better guide final acceptance review without pretending to complete human or agent review automatically. - 04 Retired File Validation Classification Reconciliation - Completed. Retired missing-input classification is implemented and validated. - Plan validation-smoke behavior for intentionally deleted migrated files referenced as deletion evidence, so they are not reported as unqualified missing-input warnings. - 05 Active Reference Audit Surface Reconciliation - Completed. The active-reference audit surface is implemented as a script/report surface. - Plan a narrower audit surface for active code, script, and package references so migration reviews do not have to manually filter historical planning references. - 06 Retained Workspace Root Blocker Reconciliation - Completed. The retained workspace-root blocker has a final disposition, targeted and runner validation pass, and runner retirement remains a separate explicit decision. - Plan the final disposition of the retained workspace-root regression that blocks legacy runner retirement after V2 migration closeout. - 01 Final Retained V1 Disposition Reconciliation - Completed. All declared milestone tasks have completed non-placeholder implementation summaries, and the milestone evidence documents satisfy the disposition and sequencing checkpoint. - Recertify the remaining V1 surfaces after phase 06 resolved the workspace-root blocker, then record the exact migration, retirement, fixture, or compatibility disposition required before future work can default to V2. - 02 Retained Cli Runtime V2 Migration Reconciliation - Completed. All declared milestone tasks have completed non-placeholder implementation summaries, focused V2 validation passed, and the CLI-focused V2 lane passed. - Migrate or retire the remaining retained CLI/runtime legacy tests so command-level coverage is owned by subprocess-first V2 files instead of the legacy in-process runtime helper. - 03 Retained Lib And Script V2 Migration Reconciliation - Completed. All declared task summaries are completed and reviewed, mapped V2 validations passed, and no legacy `tests/cli/*.test.js` files remain. - Move retained direct-library and script-specific legacy tests into V2-owned placement without forcing them through CLI subprocess helpers when the tested contract is not command execution. - 04 Fixture Helper And Tests Tree Cleanup Reconciliation - Completed. Fixtures moved to tests_v2/fixtures, legacy helpers and tests tree were removed, and focused V2 fixture-consumer validation passed. - Clean up legacy helper and fixture ownership after retained tests are migrated, so any remaining shared test data no longer implies that the V1 test suite is active. - 05 V2 Default Runner Repoint Reconciliation - Completed. Declared milestone tasks have completed summaries, required validation evidence is present, and the milestone is accepted for phase closeout sequencing. - Repoint active runner and guidance surfaces so future work defaults to the V2 validation lane instead of the legacy `tests/` runner. - 06 Final V2 Default Closeout Evidence Reconciliation - Completed. Declared milestone tasks have completed summaries, final validation passed, and phase closeout evidence is ready for phase-level read-only review. - Record final evidence that V1 disposal is complete or intentionally bounded, and that future CLI/test-infrastructure work should use V2 as the default validation suite. - 01 Disposition Schema And Identity Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Define the durable trace-link disposition record shape, stable identity rules, supported lifecycle status tokens, and repository-local target path normalization that later storage, CRUD, preview, apply, and validation work will share. - 02 Storage Location And File Contract Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Choose and implement the repository-local trace-link disposition storage contract so later CRUD, preview, apply, and validation work share one inspectable file shape and one fail-closed parser. - 03 Apply Evidence And Safety Boundaries Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Define how trace-link disposition apply evidence is represented and updated without turning validation into a write surface, rewriting historical context for retired/deleted targets, or mutating unrelated disposition fields. - 01 Affected Artifact Discovery Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Implement the shared read-only discovery behavior that locates supported planning artifacts whose trace fields reference a recorded disposition target, while preserving repository-relative source evidence and explicit unsupported or malformed artifact evidence. - 02 Migration Preview Output Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Implement preview output for trace-link dispositions so users and agents can inspect affected planning artifacts, migrated-target proposals, skipped paths, and unresolved cases before any write-capable apply command exists. - 03 Read Only Posture Regressions Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Harden read-only posture coverage for trace-link disposition discovery and preview surfaces so storage, planning artifacts, validation state, and timestamps are not mutated by read-only commands or helpers. - 01 Command Family Routing And Help Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Add the `day-shift link disposition` CRUD command family shell around the existing read-only `preview` command, including help text, accepted argument names, output-format plumbing, and visible read-only/write-capable posture metadata. - 02 Add Update Delete Behavior Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Implement durable write behavior for creating, updating, and deleting trace-link disposition records with schema validation, duplicate protection, missing-record handling, and no partial writes on invalid input. - 03 List Show And Error Output Reconciliation - Completed. All declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Implement read-only list/show behavior and deterministic text/JSON output for successful CRUD operations and failure cases across the disposition command family. - Apply Selection And Dry Run Parity Reconciliation - Completed. The declared task implementation summary is complete, reviewed, and sufficient for milestone acceptance. - Add the explicit `link disposition apply` command selection and dry-run contract, reusing the existing preview proposal model so apply dry-run evidence stays aligned with read-only preview output before write mutation is introduced. - Safe Forward Link Mutation Reconciliation - Completed. The declared task implementation summary is complete, reviewed, and sufficient for milestone acceptance. - Implement write execution for migrated trace-link apply when each proposed update is mechanically safe, limited to supported repository-local front-matter trace fields, and guarded against partial rewrites. - Apply Reporting And Rollback Guidance Reconciliation - Completed. The declared task implementation summary is complete, reviewed, and sufficient for milestone acceptance. - Complete apply output so text and JSON clearly report changed, skipped, conflict, unresolved, storage-evidence, and rollback guidance for both dry-run and write execution. - 01 Links Check Disposition Findings Reconciliation - Completed. The declared task implementation summaries are complete, reviewed, and sufficient for milestone acceptance. - Integrate recorded trace-link disposition evidence into `validation links-check` so missing local targets are classified as retired, deleted, migration-available, malformed-disposition, or ordinary missing-target findings without writing files. - 02 Smoke And Rollup Lifecycle Evidence Reconciliation - Completed. The declared task implementation summary is complete, reviewed, and sufficient for milestone acceptance. - Surface links-check lifecycle findings through artifact-scoped `validation smoke` and `validation rollup` without changing validation scope semantics or writing files. - 03 Validation No Write Regressions Reconciliation - Completed. The declared task implementation summary is complete, reviewed, and sufficient for milestone acceptance. - Prove lifecycle-aware validation remains read-only across links-check, smoke, and rollup after disposition evidence integration. - Guidance And Help Text Alignment Reconciliation - Completed. Both declared task implementation summaries are completed, reviewed, and sufficient for milestone acceptance. - Align operator-facing command help, workflow guidance, prompt guidance, and agent entrypoint language with the completed trace-link disposition lifecycle. The milestone makes command posture explicit: discovery, preview, validation, inventory, and review remain read-only, while disposition CRUD and migrated-link apply are separate write-capable surfaces. - Regression Coverage Matrix Reconciliation - Completed. The declared task implementation summary is completed, reviewed, and sufficient for milestone acceptance. - Close the trace-link lifecycle V2 regression coverage matrix by verifying and extending focused tests across disposition storage, CRUD, discovery, preview, apply, validation integration, output formats, malformed inputs, unsupported targets, and no-write/write-capable boundaries. - Release Handoff And Deferred Scope Reconciliation - Completed. All declared task summary evidence is present, non-placeholder, and accepted for this milestone. - Prepare release handoff evidence for the trace-link lifecycle workflow, including changed command surfaces, storage behavior, validation integration, regression evidence, rollback notes, safety boundaries, and deferred scope. - 01 Analytics Runtime And Privacy Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-analytics-runtime-and-privacy-contract` milestone: verify the production analytics runtime and specify bounded event names, properties, consent behavior, and sensitive-data exclusions. - 02 Funnel And Commercial Confirmation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-funnel-and-commercial-confirmation` milestone: instrument the installation-intent and purchase funnels while keeping verified paid-license purchases as the commercial confirmation signal. - 03 Field Performance And Baseline Window Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-field-performance-and-baseline-window` milestone: establish Core Web Vitals field collection, deterministic budget inputs, traffic exclusions, and the documented baseline observation window. - 01 Workspace And Build Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Align the existing `apps/website` Next.js workspace with the repository build contract for the rebuilt public website. - 02 Route And Rendering Model Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Define the canonical website route inventory, static rendering defaults, and explicit server-capable route exceptions for later website phases. - 03 Shared Content And Server Boundary Policy Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish shared typed website content sources and a small server-boundary policy for commerce, signed license delivery, recovery, and future authenticated support. - 01 Download Url Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Define the website-owned download URL contract for immutable versioned releases, the mutable latest pointer, manifest/checksum/installer/release-note asset paths, and public copy that explains exact-version resolution before install guidance relies on artifacts. - 02 Release Asset Consumption Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Wire website content and route data to checked-in release-pipeline-produced release assets without regenerating archives, manifests, installers, checksums, release notes, or validation reports. - 03 Publication Consistency Validation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Validate website-visible release manifests, byte sizes, checksums, latest pointer resolution, release notes, installer assets, and download-route visibility before publication. - 01 First Contact Positioning And Actions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-first-contact-positioning-and-actions` milestone: establish plain-language positioning, audience framing, supportable claims, and one primary plus one subordinate evaluation action. - 02 Homepage Narrative And Navigation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-homepage-narrative-and-navigation` milestone: implement the focused homepage journey, grouped responsive navigation, compact footer, and intentional website-to-docs handoffs. - 03 Reproducible Product Demonstration Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-reproducible-product-demonstration` milestone: publish the canonical Tic-Tac-Toe lifecycle using real representative commands, output, artifacts, and documented starting and completed states. - 04 Compatibility And Proof Boundaries Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-compatibility-and-proof-boundaries` milestone: expose supportable platform, shell, coding-assistant, release, and first-party evidence without implying unverified certification or adoption. - 01 Authoritative Plan And Pricing Contract Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-authoritative-plan-and-pricing-contract` milestone: consolidate plan definitions, comparison content, entitlements, release coverage, and purchase actions into one buyer-facing commercial source. - 02 Checkout Delivery Upgrade And Recovery Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-checkout-delivery-upgrade-and-recovery` milestone: verify the hosted checkout handoff and the current verified-payment, signed-license delivery, upgrade, reminder, and recovery journeys. - 03 Publisher Support Privacy And Security Trust Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-publisher-support-privacy-and-security-trust` milestone: publish assessable maintainer identity, contact, maturity, support scope, local-first privacy, security boundaries, and policy handoffs. - 04 Public Copy And Documentation Reconciliation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-public-copy-and-documentation-reconciliation` milestone: remove stale implementation language and contradictions while preserving concise website summaries and canonical documentation ownership. - 01 Marketing And Product Positioning Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement primary product positioning, pricing, FAQ, and objection-handling content from the approved marketing source pool so public product pages describe Day Shift as a local, repository-native Human-Agent-Contract workflow layer. - 02 Install License And Troubleshooting Docs Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement install, downloads-adjacent, license-command, troubleshooting, PATH, and local-state documentation for the public website using the verified release URL and CLI license command contracts. - 03 Support Privacy And Limitation Pages Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement support, privacy, known-limitation, recovery-adjacent, and MVP-boundary content with clear local-first claims and explicit website/server responsibility boundaries. - 01 Checkout And Upgrade Entrypoints Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement purchase and upgrade entry points that route customers to hosted Stripe checkout surfaces while preserving one-time release-line licensing language and keeping payment-card collection, eligibility checks, and private purchase records out of static pages. - 02 Webhook And License Issuance Boundary Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement server-only Stripe webhook verification plus signed license issuance/retrieval boundary helpers so payment completion, entitlement mapping, and license signing stay behind explicit website server routes. - 03 License Delivery And Recovery Flow Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement customer-facing success, license-delivery, install-instruction, and recovery entry points that use verified private license records and purchaser proof without broadening release-line entitlement scope. - 01 Route Metadata Canonical And Social Contracts Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `01-route-metadata-canonical-and-social-contracts` milestone: implement unique indexable-route metadata, canonical URLs, and consistent social-sharing output. - 02 Crawl Surfaces And Structured Data Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `02-crawl-surfaces-and-structured-data` milestone: add website-owned robots and sitemap behavior plus truthful product, offer, organization, and eligible visible-FAQ structured data. - 03 Accessible Semantics And Interactions Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `03-accessible-semantics-and-interactions` milestone: establish WCAG 2.2 AA-oriented landmarks, headings, bypass behavior, controls, forms, feedback, contrast, reflow, and motion handling. - 04 Responsive And Performance Budgets Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Implement the `04-responsive-and-performance-budgets` milestone: enforce representative viewport behavior, reserved media dimensions, limited client JavaScript, deterministic asset budgets, and field-vitals review. - 01 Deterministic Website And Cross App Gates Reconciliation - Completed evidence review. Every declared task has a completed, non-placeholder implementation summary. Verdict: accepted; the deterministic validation sequence, both production builds, and built cross-application verification passed using environment-qualified execution. - Implement the `01-deterministic-website-and-cross-app-gates` milestone: complete type checking, linting, website validation, production build, route checks, and documentation-boundary verification. - 02 Critical Marketing And Commerce Journeys Reconciliation - Completed evidence review. Every declared task has a completed, non-placeholder implementation summary. Verdict: accepted; offline validation and all 12 intended real-browser cases pass across narrow and wide viewports. - Implement the `02-critical-marketing-and-commerce-journeys` milestone: automate and exercise representative homepage, navigation, demonstration, installation, pricing, checkout, delivery, upgrade, and recovery paths. - 03 Manual Quality And External Review Reconciliation - Completed evidence review. Verdict: blocked on unavailable named screen-reader and live external-validator evidence; local automated, browser, screenshot-inspection, crawl, social-metadata, and JSON-LD evidence is complete. - Implement the `03-manual-quality-and-external-review` milestone: record keyboard, screen-reader, contrast, reflow, responsive, social-preview, crawlability, and applicable structured-data review evidence. - 01 Design Tokens And Shell Components Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish the website-owned visual system primitives that make the public routes feel restrained, operational, durable, and inspectable without duplicating palette and shell markup on every page. - 02 Download Install And License Surfaces Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Apply the shared operational visual system to release, install, license, and troubleshooting surfaces so commands, checksums, version metadata, platform choices, and license steps are inspectable rather than decorative. - 03 Commerce And Content Route Polish Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Apply the completed visual system to commerce, recovery, pricing, FAQ, support, privacy, known-limitation, and remaining content route surfaces so purchase and support decisions stay practical, inspectable, and visually consistent. - Route Content And Build Validation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish launch-readiness validation for the public website route set, static route coverage, build/typecheck commands, and public content constraints that are required before publication. - Release Commerce And Secret Boundary Validation Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Establish launch-readiness validation for website-visible release publication inputs, commerce server boundaries, webhook and license secrecy, and recovery/upgrade claim boundaries. - Launch Readiness And Handoff Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Collect the website publication readiness evidence, production domain assumptions, known limitations, rollback notes, and launch handoff documentation after route/content, release, commerce, and secret-boundary validation are complete. - 01 License Submission And Verification Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Define and implement the server-side prior-license submission contract required before the website grants a 50% release-line upgrade checkout path. - 02 Server Created Stripe Upgrade Checkout Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Replace static upgrade checkout redirection with server-created Stripe upgrade checkout that applies the 50% discount only after prior-license eligibility has been verified. - 03 Upgrade Flow Validation And Handoff Reconciliation - Completed. Every declared task has a completed, non-placeholder implementation summary and the milestone evidence is ready for reconciliation review. - Update validation, documentation, environment examples, and launch handoff so the automated 50% upgrade checkout flow is reproducible and safe to operate. ## User-Visible Behavior - Added Ajv 8 as a direct dependency and an executable catalog gate backed by 18 ordered positive, negative, recursive, union, additional-property, and deterministic-serialization fixtures. - Added CLI regression coverage proving invalid writes fail before storage creation or mutation. - Added V2 workspace, fixture, and assertion helper modules. - Added `agent orient` and `agent remind` as thin subcommands on the registered `agent` command family. - Added `apps/website/content/docs-content.ts` with structured install, license, troubleshooting, PATH, release URL, and local-state documentation content. - Added `docs:verify-guidance`, a read-only gate that validates internal routes, reference/troubleshooting reachability for 18 task-oriented journeys, and a structured safe CLI example in isolated temporary state. - Added `initializeVersionManagerLayout` and the declared `VERSION_MANAGER_LAYOUT_DIRECTORIES` contract. - Added `installManagedVersion`, which validates a local source, initializes the version-manager layout, removes only the exact target version package directory when replacing, and copies the validated payload into. - Added `preview.ts` with shared preview result types and classification for migrated proposals, retired/deleted lifecycle-only evidence, skipped discovery evidence, conflicts, unresolved cases, read-only posture, and. - Added `tests_v2/cli/license/status-smoke.test.js`, a representative V2 CLI smoke test that uses the V2 subprocess runner, workspace helper, and assertion helper to execute `license status` with explicit `cwd` and. - Added `tests_v2/cli/version/release-handoff.test.js`, a read-only regression that compares the `0.1.8` local release bundle with website download metadata. - Added `tests_v2/cli/workspace/root-contract.test.js` and retired the retained V1 workspace-root regression and reporting files. - Added `tests_v2/helpers/cli-runner.js`, a V2-local subprocess helper that executes the compiled CLI with `execa`, preserves explicit `cwd` and environment options, removes `undefined` environment entries, returns. - Added `validateVersionInstallSource` source resolution for unpacked package roots, `.tar.gz` archives, and deterministic stored `.zip` archives. - Added a central read-only product-surface verifier and integrated it into the standard docs check. - Added a command posture regression test fixture that seeds an isolated Day Shift workspace, runs representative read-only command families, and compares pre/post workspace snapshots to prove the selected workspace is. - Added a concise prompt-family responsibility marker to `.day-shift/prompts/user/manifest.json`. - Added a concise template-family responsibility marker to `.day-shift/templates/manifest.json`. - Added a declined-network no-write alias assertion and reran the path diagnostics suite. - Added a dedicated `healthRuntimeGuidance` lane to the agent orientation data model and rendering. - Added a deterministic route-metadata validator and Node regression test covering all declared public routes. - Added a doctor diagnostic regression for unsupported selected package layouts and repaired the runtime diagnostics fixture so selected-runtime doctor coverage uses valid installed-version metadata. - Added a fail-closed inventory validator and integrated it into the website validation chain. - Added a focused commercial-journey contract validator covering hosted checkout, verified-payment delivery, upgrade eligibility and checkout rejection, and recovery proof handling without live Stripe credentials. - Added a focused commercial-plan contract test and updated foundation expectations so source uniqueness, required buyer-visible fields, checkout eligibility, endpoint preservation, and single-surface rendering regress. - Added a focused executable documentation contract for the operating-model page. - Added a focused regression test that exercises the three declared agent entrypoints through the CLI subprocess harness. - Added a focused runtime documentation regression that ties the public operational guidance to shipped prompt precedence, rendering evidence, template manifest routes, command posture, and later-milestone boundaries. - Added a focused, inventory-driven website entry-point validator and integrated it into the complete website validation chain. - Added a full selector precedence regression to `selection-resolution.test.js`. - Added a read-only version selection resolver for managed Day Shift installations. - Added a reusable default documentation path classifier under validation helpers. - Added a reusable descriptor/runtime/tool drift validator and exposed it through the read-only `commands validate` command. - Added a reusable state-aware workflow-action composer and integrated it into artifact-scoped agent context. - Added a server-only signed license issuance boundary helper for turning verified payment evidence into Day Shift signed JSON license envelopes, plus private record retrieval by license ID. - Added a shared implementation-summary closeout evidence model to the agent orientation data. - Added a standalone read-only website release publication validator that checks public 0.1.10 and latest download assets for manifest consistency, byte-size and SHA-256 integrity, checksum metadata drift, latest pointer. - Added a structured closeout evidence-boundary model to the agent orientation data. - Added a typed marketing content source for launch product positioning, homepage sections, audiences, pricing packages, FAQ objections, static purchase/upgrade entry copy, and anti-positioning boundaries. - Added a versioned adversarial trajectory corpus and focused provider-free regressions for trust boundaries, invalid context, redaction, payload budgets, recovery, and partial writes. - Added a versioned deterministic trajectory fixture corpus and focused Node regression suite covering ordinary completion, recovery and resume, stable metrics, failure attribution, and all hard harness safety gates. - Added an authoritative `resume` command family for create/replace, inspect, resume, clear, and cleanup, with typed stale/conflict/concurrency failures and explicit read/write boundaries. - Added an executable publication lifecycle that snapshots canonical Markdown, runs two clean generate/check/Astro-build/leakage-verification cycles, and rejects canonical mutation or byte-level drift in generated public. - Added an exported, typed, additive planning-artifact document parser retaining exact source text and exposing metadata, ordered sections, source ranges, diagnostics, and SHA-256 content hashes. - Added an optional exact descriptor-backed action lens to focused planning validation. - Added and ran focused CRUD regression coverage for list/show read-only snapshots, success output, JSON posture metadata, malformed storage, unsupported format, invalid migrated add, duplicate add, and missing-record. - Added application-level and focused Node regression coverage for the canonical installation/version-management contract. - Added application-level and focused-test enforcement for exact page/inventory parity, closed disposition semantics, and substantive link-bearing retained indexes. - Added assertions that evidence-aware review findings expose actionable recovery and parent declaration affected-path evidence. - Added bounded lightweight-planning and emergent-work guidance to the shared agent orientation planning model. - Added bounded versioned calibration observations that retain decision evidence, deterministically order signals, and prohibit automatic threshold changes. - Added build-time website consumption of the checked-in public 0.1.10 release manifest and artifact checksum metadata, then updated downloads and release-notes pages to render the current exact release version, command. - Added callable `work select`, `work current`, `work next`, and `work clear` commands with named-session lifecycle evidence, explicit-input precedence, structured conflict/stale/missing errors, next-action integration,. - Added category regression coverage for the task-scoped changed-path report. - Added cleanup readiness gates and per-item cleanup states to the boundary map. - Added command metadata drift coverage for agent orientation surfaces. - Added command-facing regression coverage that treats source-spec review/refinement phrases as no downstream planning writes and verifies selected spec registry writes or failures do not create `.day-shift/planning`. - Added compact source and adjacent-reference link coverage to `.day-shift/references/planning-layers.md`. - Added concise human-reader audience and responsibility markers to the workflow index, start-here workflow, and procedural workflow sequence. - Added dedicated missing-entrypoint no-write coverage for the agent command family. - Added deterministic coverage for publisher/contact visibility, trust-route reachability, tiered support boundaries, local/server privacy controls, release evidence, and prohibited unsupported assurance or. - Added deterministic offline regression coverage for ordered funnels, representative route signals, dual plan-selection and checkout dispatch, milestone 01 privacy enforcement, and the server-owned commercial. - Added deterministic public-copy/documentation-boundary coverage, wired it into aggregate website validation, and reconciled foundation assertions with the current `/demo`, marketing, analytics-contract, and public. - Added deterministic schema-to-TypeScript generation, a checked-in generated protocol-v1 schema bundle, build/check scripts, and an Ajv runtime validator that consumes only generated catalog output. - Added deterministic, offline regression coverage for the production runtime mount and the analytics event, privacy, consent, traffic, and evidence-boundary contracts. - Added exact follow-up recommendation posture to no-write evidence. - Added executable regression coverage for focused homepage closure, responsive buyer-facing navigation, compact footer semantics, required operational/policy destinations, and the canonical documentation handoff. - Added executable regression coverage tying public compatibility claims to release 0.1.19 manifest, release-layout tests, completion-shell tests, and explicit assistant proof boundaries. - Added explicit no-side-effect coverage for health and runtime discovery recommendations. - Added explicit promotion-pressure recovery guidance to lightweight advisory findings. - Added explicit route-model policy for static public rendering and bounded server-capable exceptions. - Added final regression coverage for the materialization command boundary. - Added focused CLI regression coverage for milestone scaffold inheritance. - Added focused CLI regression coverage for standard task scaffold inheritance. - Added focused CLI regression coverage for the agent orientation workflow-rule contract. - Added focused CLI regression coverage for the materialization command contract. - Added focused CRUD CLI regression coverage for family help, per-command posture help, migrated add output metadata, duplicate rejection, update/delete mutation, list/show read-only behavior, invalid-write. - Added focused JSON-mode regression coverage for the agent orientation command family. - Added focused Node regression coverage for the docs scaffold and exposed it through the `@day-shift/docs` package test script. - Added focused Node regression coverage for the incremental freshness index, including exact-match authorization, invalidation, source removal, incomplete generation, supersession, deterministic cleanup, and malformed. - Added focused Runtime Delta regression coverage. - Added focused V2 coverage for trace-link disposition affected-artifact discovery, including supported planning trace-field matches, no-match evidence, unsupported focused artifact evidence, malformed disposition input,. - Added focused V2 regression coverage for the trace-link disposition model, status contract, target normalization, migrated-target rules, retired/deleted safety boundary, and duplicate identity detection. - Added focused V2 regression tests for the trace-link disposition storage path, schema version, empty document, valid parsing, deterministic serialization, malformed input rejection, unsupported version rejection,. - Added focused V2 tests for apply-evidence path normalization, unsafe path rejection, decision-field preservation, migrated-only rewrite eligibility, and required timestamp/revision evidence. - Added focused agent command coverage for implementation-summary closeout guidance. - Added focused agent command coverage for reconciliation readiness guidance. - Added focused agent command coverage for verbose orientation mode. - Added focused agent command fixture coverage for root-context reporting across explicit root, config marker, agents marker, git marker, and current-directory fallback cases. - Added focused classifier regression assertions proving configured runtime-eligible paths override repository documentation-only rules and default Day Shift documentation classification. - Added focused closeout and reconciliation gate assertions for validation-exception policy, Runtime Delta target policy, read-only reconciliation review output, and task readiness review output. - Added focused command-surface taxonomy regression coverage for the agent orientation command. - Added focused compiled-runtime and CLI regressions that freeze the seven-lane registry and inject instruction-like repository content across prompt rendering, artifact context, context packing, workflow explanation,. - Added focused compiled-runtime regressions for canonical policy composition and prompt rendering integration. - Added focused core-family, contract, posture, workflow-link, canonical-page, and built-route regression coverage. - Added focused current-state and negative-case tests for the product-surface verifier, covering all declared families, a missing canonical owner, and an empty authoritative command inventory. - Added focused documentation coverage in the existing agent command test harness. - Added focused documentation-loop and verb-policy assertions for read-only breakout review output and mode-aware verb selection. - Added focused drift coverage that regenerates descriptor evidence in memory and checks the committed public inventory, command-family ownership, shared controls, posture vocabulary, canonical page set, and. - Added focused executable coverage for command ordering, immutable allowlisted cleanup, excluded route/content leakage, search-like output leakage, and unapproved static contracts. - Added focused executable coverage for the exact initial path manifest, every page's explicit metadata and structural body boundary, and all required built routes. - Added focused executable documentation coverage for the evidence-review and reconciliation workflow. - Added focused executable documentation coverage for the resume, trace-link lifecycle, archive, recovery, and release-handoff workflow. - Added focused executable guards for configuration layers/provenance, completion read/write boundaries, doctor scopes and recovery, the ordered first-use journey, navigation, inventory closure, and canonical path parity. - Added focused executable guards for init modes, root semantics, generated anatomy, ownership, repeat-run safety, force protection, migration-safe recovery, inventory closure, and getting-started navigation. - Added focused executable regression coverage for the canonical intake-to-implementation workflow, including lane routing, ordered decomposition, readiness and selection gates, mutation posture, evidence handoff,. - Added focused frontmatter-schema regression coverage and expanded the docs package test command to run all schema and scaffold suites. - Added focused full-orientation text assertions without introducing a full-output snapshot. - Added focused implementation-summary build regression coverage for completed none-state normalization and the incomplete-summary guard. - Added focused implementation-summary review coverage for Runtime Delta target alignment. - Added focused implementation-summary review coverage for contract closeout boundaries. - Added focused implementation-summary review regression assertions for mode consistency, contract-mode runtime-claim boundaries, Runtime Delta target policy exposure, and no-write review posture. - Added focused launch handoff validation and wired it into the website validation chain. - Added focused launch validation for public/static secret boundaries and commerce/license server-only posture. - Added focused local source validation regression tests covering accepted unpacked, tar, and zip inputs plus wrong identity, wrong command name, mismatched asserted version, mixed release directory, malformed metadata,. - Added focused migration coverage and expanded the information-architecture suite from the initial ten-page scaffold to the current 13-page canonical collection. - Added focused mutation coverage for the reusable cross-application contract, including missing public entry points, exact destination and origin drift, absent docs-to-website operational links, and protected. - Added focused offline regression coverage for the field-vitals mount/allowlist, metric and device scope, accepted thresholds, deterministic build inputs, traffic boundaries, and pending representative baseline. - Added focused offline regression tests and a real-browser Playwright suite for representative critical journeys at narrow and wide viewports. - Added focused operational-family, consequence, posture, recovery, canonical-page, and built-route tests. - Added focused phase-review regression coverage proving the aggregate review surface reports breakout requirement blockers and keeps recovery guidance read-only. - Added focused planning review regression coverage for contract-to-runtime handoff behavior. - Added focused planning review tests for repeated documentation-only summary detection and phase aggregation. - Added focused planning-review tests for breakout task requirements after documentation-only loops. - Added focused preview regression coverage for library preview classification, CLI JSON output, CLI text output, target selectors, missing storage empty previews, malformed storage failure, and no-write workspace. - Added focused protocol, bounded-output, failure, registration, effect, extension, canonical-page, and built-route regression coverage. - Added focused public-copy launch validation for prohibited public npm install positioning and required launch claims. - Added focused readiness-review regression assertions for runtime evidence gates. - Added focused real-filesystem and injected-operation regression coverage for deterministic evidence, ordered full prevalidation, unchanged suppression, atomic delegation, postcondition verification, partial-state. - Added focused real-filesystem and injected-operation regression coverage for the atomic single-file primitive. - Added focused real-filesystem and injected-operation regression coverage for the recoverable mutation coordinator. - Added focused reconciliation review regression coverage for runtime task summaries with documentation-only Changed Paths evidence. - Added focused regression assertions for changed-path evidence lane separation and Runtime Delta target-alignment review output. - Added focused regression coverage for body-reference source-location evidence. - Added focused regression coverage for closeout evidence-boundary behavior in the agent command surface. - Added focused regression coverage for every state in the publication eligibility contract and its fail-closed metadata errors. - Added focused regression coverage for execution-mode metadata scaffold and review behavior. - Added focused regression coverage for generic skipped-validation exceptions and complete structured validation exceptions. - Added focused regression coverage for planning exception boundaries, closeout sequencing, reconciliation readiness, and workspace migration blocker routing in the agent orientation command. - Added focused regression coverage for profile identity, complete and missing prerequisites, inapplicable constrained-only evidence, versioning, and authorization invariants. - Added focused regression coverage for repository path-policy behavior and config validation. - Added focused regression coverage for repository-memory checkpoint boundaries. - Added focused regression coverage for required review areas, complete evidence fields, blocked not-run disposition, and external-review overclaim rejection. - Added focused regression coverage for the command inventory export. - Added focused regression coverage for the default documentation path classifier. - Added focused regression coverage for the integrated release gate's declared order, all-success execution, stop-on-first-failure behavior, and child-process startup failures. - Added focused regression coverage for the new version command surface and updated root-help coverage for the new command. - Added focused regression coverage for the portable runtime evidence policy pack so the pack remains included in shared authoring assets and aligned with repository template and review policy text. - Added focused regression coverage for the task-scoped changed-path report helper. - Added focused regression coverage for the updated implementation-summary template contract and generated task artifacts. - Added focused regression coverage tying published lifecycle evidence to the canonical workflow, current CLI command sequence, homepage proof surface, documented states, and executable public fixture. - Added focused regression tests proving agent orientation output never claims prohibited command families ran as side effects. - Added focused release publication launch validation for checked-in website-visible downloads. - Added focused release-readiness regression coverage for Vercel framework/build/output drift, canonical-origin drift, failed preview responses, and explicit classification of hosted deployment constraints. - Added focused responsive/media/client-boundary regression coverage and revalidated deterministic budgets plus separately classified field evidence. - Added focused rewrite-engine tests covering safe rewrites, duplicate distinct occurrences, existing link destination skips, YAML front matter skips, fenced code skips, inline/backticked skips, overlapping candidates,. - Added focused route launch validation for the website and wired it into the website package validation surface. - Added focused runtime diagnostics regression coverage for JSON failure findings, malformed selected metadata, recursion-hazard recovery guidance, doctor JSON context, and PATH conflict reporting. - Added focused runtime regression coverage for deterministic cache lifecycle behavior, semantic value preservation, bounded decision metrics, and privacy-safe trace evidence. - Added focused runtime regression coverage for lightweight promotion-pressure warnings in `tests/cli/runtime-planning-navigation.test.js`. - Added focused runtime regression coverage for representative cold/warm workflow measurement, explicit baselines, deterministic work gates, and host-sensitive latency advisories. - Added focused runtime-grounded coverage for the public upgrade guide and disposable-workspace validation. - Added focused source-level regression coverage for the homepage first-contact contract and exposed it as a named website validation command. - Added focused state-layout regression coverage for override root resolution, platform default roots, idempotent directory creation, and preservation of existing selected metadata, aliases, and package files. - Added focused text-mode regression coverage for the default agent orientation and correction-focused reminder output. - Added implementation-summary build coverage for task-scoped changed-path evidence. - Added install validation regressions for unsupported local source directories and package metadata that does not expose the `day-shift` command. - Added isolated regression coverage for deterministic repeated publication, output drift, and cleanup mutation of canonical Markdown. - Added isolated regression coverage for deterministic, fail-closed inference artifact generation and explicit contract allowlisting. - Added isolated shim dispatch tests with fake version-manager roots and managed packages. - Added manifest-derived regression coverage for prompt identities, versions, layer/action coverage, template references, template identities/classes/destinations, semantic variables, ownership boundaries, navigation,. - Added metadata sync regression coverage for milestone overview sync, phase overview sync, active-artifact guard rejection, selector ambiguity rejection, and existing task sync behavior. - Added minimal cross-link coverage after task 01 and task 02 completed their canonical reference homes. - Added no-write regression coverage for the new agent command surfaces. - Added one registry-backed Next.js metadata contract and connected all 18 declared public pages to route-specific metadata without changing their rendering model. - Added package metadata validation for local install sources. - Added planning and metadata inventory recommendations to the shared `AgentOrientationData.discoveryRecommendations` model. - Added preview command posture assertions that verify help text exposes the read-only boundary, JSON output reports `readOnly: true` and `writeCapable: false`, and the phase does not expose apply or CRUD subcommands. - Added pure graph regression cases for a valid journey, an unresolved internal route, and missing troubleshooting reachability. - Added read-only version-manager runtime-state helpers for explicit shim mode, version-manager root resolution, selected-version metadata parsing, managed package executable resolution, and failure classification for. - Added reconciliation build regression coverage for the all-complete closeout path, including generated completed metadata, canonical none-state wording, and a clean read-only reconciliation review. - Added reconciliation review tests for declared-later-work classification and the unresolved-work control case. - Added registered source-spec discovery recommendations to the shared `AgentOrientationData.discoveryRecommendations` model. - Added registry-level write capability scope tests that require each write-capable command to use an allowed artifact-family, destination-posture, mutation-posture, and coordination-scope combination. - Added regression coverage for changed-path classification evidence and runtime-summary review behavior. - Added regression coverage for evidence-aware stale message-source review behavior. - Added regression coverage for stable workflow-rule and command-surface structured fields. - Added release-handoff regressions for explicit `stable` alias mutation and ambiguous alias target expansion. - Added repository-owned V2 validation scripts and a deterministic V2 test-file runner. - Added runtime-grounded regression coverage for the public customization workflow and its ownership, no-write, preservation, destination, force, and later-milestone boundaries. - Added selected-artifact no-write regression coverage for validation, links-check, planning inventory, gap-report, next-action, and milestone review commands. - Added selected-artifact update boundary regressions for slice, phase, milestone, task, implementation-summary, and reconciliation update commands. - Added server-only private license record lookup plus license download and recovery request route handlers. - Added shared bypass navigation, focusable content targeting, minimum target sizing, reduced-motion handling, and explicit upgrade help association with regression coverage. - Added shared entrypoint-status data to the agent orientation payload. - Added side-by-side shim dispatch regression coverage. - Added slice and phase closeout references to final phase 07 evidence without changing status metadata. - Added stale source-spec planning risk warnings to the shared planning heuristic helper and wired them into task readiness review, task review, and milestone review. - Added strict structured discovery requests while preserving shell behavior. - Added structured command-surface posture coverage to the runtime command posture regression suite. - Added structured finding-severity guidance to the shared agent orientation data model. - Added structured license delivery/recovery content, a `/success` license delivery page, and updated `/recovery` to describe MVP purchaser-proof recovery without expanding entitlement scope. - Added structured no-invented-state and selected-artifact evidence guardrails to the shared agent orientation data model. - Added structured reconciliation readiness guidance to the agent orientation data model. - Added structured workspace blocker and migration routing guidance to the agent orientation contract. - Added the `commands inventory` CLI surface. - Added the explicit verbose option contract and routing seam for the agent orientation command family. - Added the final focused assertion coverage for `agent remind`: text compactness, distinction from full orientation lanes, structured JSON reminder fields, and no-write behavior for reminder JSON. - Added the hosted checkout redirect boundary for the `stripe-checkout` server exception. - Added the named `docs:verify-drift` gate and placed guidance/example verification inside each deterministic clean publication cycle before static rendering. - Added the protocol-v1 runtime authority and compatibility reference. - Added the reminder-specific data-selection layer in `src/cli/commands/agent/index.ts`. - Added the server-only Stripe webhook verification boundary with raw-body signature verification and a fail-closed `/api/stripe/webhook` route. - Added the shared fail-closed publication eligibility decision and made the application checker apply it to every canonical Markdown page before downstream build work. - Added the shared health and runtime discovery recommendation data model to `AgentOrientationData`. - Added the shared trace-link disposition affected-artifact discovery module and exported it from the disposition library. - Added the shared trace-link disposition model surface with status tokens, normalized target shape, discovery context, apply evidence, audit metadata, and discriminated record types for retired, deleted, and migrated. - Added the structured repository-memory checkpoint boundary model to the agent orientation data. - Added the typed public boundary content source for support, privacy, recovery, and known limitations, including local-first CLI claims and Phase 04 server-only ownership wording. - Added the website download URL contract model and replaced the generic downloads and release-notes route shells with contract-aware static pages. - Added the website-owned foundation validation script and verified the workspace `validate` script executes it. - Added traceability verification to the inventory artifact. - Added tracked adversarial output-safety coverage and refreshed protocol fixtures for the additive action posture. - Added typed hosted-checkout commerce content and rewired the purchase and upgrade pages to render release-line license purchase/upgrade actions from that content. - Added typed server-boundary policy for the allowed future dynamic/server responsibilities and extended website validation to keep that policy synchronized with the route inventory. - Added typed shared content modules for site identity, route content conventions, home metrics, and install/release input ownership policy. - Added uninstall selector-impact regression assertions and preserved structured uninstall validation details in JSON error output. - Added versioned synthetic held-out calibration evidence and provider-free regressions for independent model/baseline sufficiency, confidence intervals, promotion thresholds, attribution, and deterministic verdicts. - Adopted the approved baseline agent-context library extraction consumed by the agent command adapter. - Adopted the shared visual-system primitives on the homepage, generic public route shell, and boundary page shell. - Aligned command help, command capability metadata, rendered validation/review guidance, planning navigation, reconciliation review output, structural-pressure reporting, and regression coverage with the shared finding. - Aligned lifecycle workflows, prompts, and template-facing guidance with the command adoption map. - Aligned reference, template, prompt-manifest, and template-spec guidance with artifact-family mutation boundaries, selected-artifact validation scope, active-artifact handoff guards, template reference semantics, and. - Aligned shared human-readable output with the structured no-write evidence contract. - Aligned source-spec lifecycle gate wording across the specification-to-slice prompt, specification review prompt, prompt manifest, and planning workflow guides. - Aligned template and reference guidance with the lifecycle-friction behavior. - Aligned template-family reporting and docs with the layer-specific overview filename policy. - Aligned the runtime evidence policy-pack CI examples with reusable Day Shift validation and review commands, including milestone reconciliation review and provider-neutral no-write guidance. - Aligned the shared human-readable finding renderer and structured validation output contracts with the taxonomy fields from task 01. - Aligned the website workspace foundation with the repository script contract and replaced generated starter app content with Day Shift foundation content. - Aligned trace-link disposition help surfaces and focused help regression coverage. - Aligned workflow and prompt guidance for command-family regression work. - Also tightened the text renderer by removing separator-only blank lines so the expanded recommendation list stays within the existing compact prompt-ready line budget. - Archived specs 15 and 20 independently through separate supported commands. - Assembled the complete EADL Qualification Analysis report with the exact ten-section structure, thirteen-criterion matrix, representative trace, language and alternative classification analysis, qualification gaps,. - Assessed V2 runner and package-script behavior after legacy retirement and recorded a no-change runner decision in `runner-alignment-follow-up.md`. - Audited V2 fixture and helper consumers before moving fixtures and deleting legacy helper paths. - Audited in-scope Day Shift documentation for stale CLI availability wording and verified the current built CLI command surfaces from `node dist/cli/index.js`. - Audited package scripts and runner references for migrated CLI validation. - Built a coverage-controlled repository evidence inventory spanning every required family and all 27 source-spec vocabulary terms, with representative discovery matches followed into implementation, storage, validation,. - Captured current option surfaces. - Captured current review output for the phase 05 final V1 retirement reconciliation. - Captured the live retained V1 surface in `current-v1-surface-inventory.md`, including remaining legacy test files, retained fixtures/helpers, V2 test coverage inventory, default runner references, and active guidance. - Characterized legacy front-matter and H2-section helper behavior before introducing the shared seam. - Clarified the agent entrypoint and lifecycle routing path. - Classified all remaining retained script/direct-library V1 files and recorded their V2 owner files in `lib-script-migration-evidence.md`. - Classified the inventory entries by audience lane, current marker mechanism, missing marker or ambiguity, and likely destination lane. - Completed a citation-ready assessment of EADL criteria 1 through 7. - Completed a documentation duplication audit for the milestone. - Completed a nine-step operational trace of `link materialize --write`, covering invocation, guards, resolution, discovery, validation, candidate projection, authorization, scoped mutation, structured result, and. - Completed apply reporting and rollback guidance for dry-run, successful write execution, and blocked unsafe execution. - Completed command boundary classification in `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/command-inventory.md`. - Completed command posture and no-write regression coverage. - Completed focused command-output regression coverage for the shared review-output contract and validation no-write boundary. - Completed guidance, heuristic, derived-state, and report/read-only boundary regression coverage. - Completed lifecycle, artifact-family, closeout-review, and reconciliation eligibility regression coverage. - Completed links-check disposition output and applied-migration suppression coverage. - Completed migration batch sequencing in the milestone-local retained CLI family inventory. - Completed regression hardening for layer-specific overview filenames. - Completed the controlled thirteen-criterion qualification matrix, including explicit support/limitation evidence, missing capabilities, status confidence, status distribution, and separate findings for event replay,. - Completed the cross-output rendering and coverage pass for health/runtime and workspace migration blockers. - Completed the discovered compact-context regression repair. - Completed the discovery-command handoff guidance pass. - Completed the final command-gap and release-ready evidence sections in `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/validation-and-gap-report.md`. - Completed the focused validation pass for the milestone and repaired one in-scope closeout metadata warning surfaced by artifact-scoped planning smoke. - Completed the legacy runner-retirement decision. - Completed the manual-exception boundary in `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/adoption-map.md`. - Completed the nine-stage EADL trace, adjacent-edge inventory, semantic-conflation review, and separate event replay, decision reconstruction, action repetition, and outcome reproduction findings. - Completed the portable runtime evidence gates policy pack and wired `.day-shift/policy-packs` into shared authoring asset discovery so the pack is bootstrap-copyable with other Day Shift authoring assets. - Completed the remaining V1 helper, fixture, runtime-helper, and runner audit and recorded decisions in `helper-fixture-runner-decision.md`. - Completed the retained init/lib/helper/fixture inventory and recorded migration decisions in `init-lib-fixture-inventory.md`. - Completed the shared review-output contract source changes for review-family commands. - Completed the trace-link lifecycle regression coverage matrix and added a focused CRUD read-output assertion. - Completed the validation evidence boundary guidance pass. - Completed with a no-deletion cleanup decision. - Completed. - Confirmed all retained legacy `tests/cli/*.test.js` files are retired; only `tests/cli/runtime-helpers.js` remains for milestone 04 cleanup. - Confirmed and strengthened the agent command JSON envelope contract. - Confirmed phase review uses the same shared planning-review issue collectors as milestone review for runtime handoff, documentation-loop, and breakout blockers. - Confirmed the CLI help discovery surfaces already satisfy the task contract. - Consolidated descriptor-to-capability, inventory, and discovery projections behind a typed adapter seam. - Consolidated the evaluation, Solo Commercial, Small Team, Company, and Enterprise paths into `commercialPlans` and changed `/pricing` to render that collection once with a directly comparable commercial contract. - Constrained structural-pressure sync writes to material derived-state source and entry changes by ignoring timestamp-only churn during state comparison. - Converted all six candidate routes and secondary navigation to canonical-documentation entry points, retained website-owned download/purchase/recovery/policy actions, removed the 143-line long-form docs module, and. - Corrected stale CLI availability wording identified by the audit. - Created `.day-shift/planning/16-onboarding-experience-redesign/phases/01-audience-and-responsibility-separation/milestones/03-prompt-template-reference-boundaries/prompt-template-reference-boundary-map.md` as the. - Created `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/adoption-map.md` from the completed command inventory. - Created `.day-shift/workflows/00-existing-repository-with-day-shift.md` as a dedicated human workflow for adopting or resuming Day Shift in an existing repository. - Created `active-guidance-reference-audit.md` for milestone `01-active-guidance-reference-alignment`. - Created `apps/website/LAUNCH_READINESS.md` as the operator-facing website launch handoff. - Created `disposal-sequence.md` with the declared order for remaining V1 disposal: CLI/runtime migration, direct-library/script migration, fixture/helper cleanup, runner repointing, and final closeout evidence. - Created `final-disposition-record.md` with final classifications for retained legacy CLI tests, helpers, fixtures, default runner surfaces, migrated/deleted V1 files, and historical planning references. - Created a durable closed inventory for all 13 authored canonical pages and replaced structural entry-point copy with honest, useful orientation and onward navigation. - Created and adapted the Astro Starlight starter as the self-contained `@day-shift/docs` workspace. - Created lifecycle-friction release handoff evidence and added concise lifecycle-friction reduction sections to current website, latest, and download-bundle release-note handoff copies. - Created the exact ten-page canonical information architecture with explicit schema-valid metadata, concise structural content, stable section navigation, and exact-path application checks. - Created the final nine-spec closeout ledger with required dispositions, evidence, replacement identifiers, blockers, archive authorization, sequencing, and reversal guidance. - Created the initial `tests_v2/` placement skeleton with placeholder-only `.gitkeep` files under the helper, CLI command-family, init, and lib boundaries declared by the phase and milestone. - Created the milestone-local `coverage-inventory.md` artifact. - Created the milestone-local audience marker inventory artifact and recorded the repository-local surfaces in scope for later audience and responsibility clarification. - Created the milestone-local human/agent boundary map and mapped 20 human-workflow guidance items from `.day-shift/workflows/README.md`, `.day-shift/workflows/01-start-here.md`,. - Created the milestone-local retained CLI family inventory at `.day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/04-retained-cli-family-inventory-and-sequencing/retained-cl. - Created the phase-local command inventory artifact at `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/command-inventory.md`. - Created the planned `.day-shift/references/` homes for prompt/template, command, spec registry, metadata, validation/review, planning-layer, and structural-pressure responsibilities. - Created the requirement-level legacy-spec coverage record. - Created the typed public route inventory, shared static route-shell component, and individual route pages for every required public website entry point. - Created the website documentation-migration inventory with 25 route and content-module entries, explicit ownership, one supported disposition per item, rationale, and canonical destinations for every move or. - Defined options, selector validation, output-format validation, and command posture payloads for add, list, show, update, and delete. - Defined the accepted residual warning contract for milestone 01. - Defined the active reference audit scope: `package.json`, `scripts/`, `src/`, `tests/`, and `tests_v2/`, excluding `.day-shift/planning` history by default. - Defined the canonical trace-link disposition storage contract at `.day-shift/state/trace-link-dispositions.json` with schema version `1`, an inspectable JSON envelope, empty-document construction, and workspace-root. - Defined the prior-license upgrade submission contract in website content, replaced the direct upgrade checkout call-to-action with a prior-license evidence form, documented safe response fields and fail-closed error. - Defined the reconciliation build rollup contract for draft status, review-clean empty sections, and fuller validation evidence. - Defined the retired input classification contract. - Defined the shared apply-evidence contract with `lastAppliedAt`, `dispositionRevision`, changed paths, skipped paths, conflict paths, and unresolved paths as evidence separate from disposition decision fields. - Deleted legacy runtime and output helper files after all legacy tests were retired. - Derived shared envelope aliases from generated `AutomationEnvelope`, wired both JSON emitters through generated-schema Ajv validation, normalized implementation-only finding reason inputs, and expanded drift,. - Each reference is a compact routing document with linkable sections and canonical source links. - Encoded the standard planning-flow rules in the shared agent orientation data. - Enforced additional no-write rejection behavior for lossy manifest update requests and added regression coverage for scaffold/support update rejection. - Enforced explicit task-level reconciliation exception rationale at the build and review command boundary. - Expanded `.day-shift/references/planning-layers.md` from a terse layer list into a planning-layer relationship model. - Expanded `.day-shift/references/prompts-and-templates.md` into a canonical prompt/template responsibility reference. - Expanded `.day-shift/references/validation-and-review.md` into a canonical validation, review, evidence-only, no-write, implementation-summary gate, milestone-reconciliation gate, and structural-pressure policy. - Expanded the agent command no-write fixture in `tests/cli/agent-command-surface.test.js` with deterministic representative files for planning overviews, task definitions, implementation summaries, reconciliation,. - Expanded the canonical installation page from a short installer pointer into the complete verified release, managed-version, upgrade, compatibility, and recovery journey. - Expanded the shared `day-shift agent` command-surface taxonomy with explicit read-only entries for agent orientation, doctor, config, about, planning inventory, metadata inventory, spec discovery, spec search, and spec. - Expanded the shared `day-shift agent` command-surface taxonomy with validation, review, write, and mixed command-family entries. - Expanded the shared planning heuristic helper with warning-level checks for documentation-only decomposition, weak target-path evidence, and weak dependency evidence. - Exposed `day-shift agent context` as a read-only selected-artifact command, registered its structured authoritative descriptor and compact budget eligibility, and added focused selection, detail-parity, trust-boundary,. - Exposed explicit `doctor` selectors for runtime-only, one planning artifact, one planning directory, and repository audit. - Exposed selection preconditions through `--if-match` on select/clear, added `work cleanup`, surfaced current tokens and stable precondition/lock errors, updated authoritative descriptors, and added real child-process. - Exposed the task-01 candidate model through a new read-only `work candidates` command family, added bounded text/JSON rendering, registered authoritative descriptor metadata, and approved the command for shared output. - Exposed validated context-pack byte budgets through `agent context` and added executable budget, trimming, freshness, exclusion, heuristic, invalid-input, and core-context parity regressions. - Extended CLI coverage for dry-run preview, selected-artifact write execution, skipped rewrite reasons, no-write validation posture, and command guidance. - Extended `metadata sync-status-from-review` to accept exactly one task, milestone, or phase selector and apply deterministic completed status updates from completed review evidence. - Extended discovery and preview no-write regressions so unsupported and malformed discovery cases, text preview, missing storage preview, and malformed storage failure all compare full workspace snapshots before and. - Extended lifecycle regression coverage to pin the continuous drift alias and the generation/check/guidance/build/leakage stage order. - Extended the deterministic evaluation harness with typed adversarial signals and versioned UTF-8 payload-budget baseline metrics while preserving milestone 01 result compatibility. - Extended the focused information-architecture regression suite so it mirrors the runtime disposition and substance contract across every canonical inventory entry and retained public page. - Extended the shared pack builder with full-payload UTF-8 budgets, rank-preserving trimming, freshness evidence, low-confidence heuristic candidates, and compact missing/entry-limit/budget exclusion reports. - Extended the task-scoped changed-path report with path category classifications. - Extended validation link discovery so body-section trace fields continue to expose the existing unique `values` list while also reporting `bodyReferenceOccurrences` for each matched body reference. - Extended website validation coverage for the automated upgrade flow. - Extended website validation for license delivery content, success/recovery pages, private license records, license downloads, recovery proof intake, and the expanded commerce route-handler allowlist. - Extended website validation so the phase-02 download URL contract is checked as part of `pnpm --filter @day-shift/website validate`. - Extended website validation to enforce the webhook route, webhook helper, license issuance helper, and route-handler boundary for milestone 02. - Extracted ordered doctor check-plan execution into a typed module and routed core checks through it. - Final V2 validation evidence was captured after the migration and cleanup milestones. - Fixed metadata update parent-link evidence checks so selected planning artifacts with supported legacy parent overview links can receive status-only updates. - Generated a fresh synthetic Tic-Tac-Toe lifecycle with the current CLI, published sanitized command/state evidence and an executable public fixture, and added inspectable proof to the homepage without changing. - Hardened lifecycle validation no-write regression coverage. - Identified phase 05 milestone 06 as the retired-file evidence source. - Implemented Runtime Delta target-alignment review for runtime and hybrid implementation summaries. - Implemented `/install` and `/license` as static documentation pages backed by `apps/website/content/docs-content.ts`. - Implemented `/troubleshooting` as a static guidance page backed by `apps/website/content/docs-content.ts` and extended validation to verify install, license, and troubleshooting docs wiring. - Implemented `day-shift version pin ` as a repository-scoped `.day-shift-version` write. - Implemented `discoverTraceLinkDispositionAffectedArtifacts`, a pure read-only helper that reuses planning validation links discovery, normalizes trace-field values, matches them to disposition target paths, groups. - Implemented `link disposition add` through the CRUD command module. - Implemented `link disposition delete` through the CRUD command module. - Implemented `link disposition list` and `link disposition show` as read-only commands over the disposition storage document. - Implemented `link disposition update` through the CRUD command module. - Implemented `planning gap-report --artifact ` as a backward-compatible alias for artifact-focused gap reports. - Implemented `scripts/audit-active-references.js` and exposed it as `pnpm audit:active-references`. - Implemented `src/lib/validation/artifact-shape.ts`, a shared read-only parser and shape validator that consumes artifact-family detection, separates Markdown front matter from body text, parses JSON manifests with. - Implemented a canonical `buildAgentOrientationData()` payload used by the agent command emission path. - Implemented a centralized website analytics runtime and privacy contract. - Implemented a deterministic source-spec lifecycle intent helper in the shared command-capability output module. - Implemented a durable eight-area quality-review record, validator, and Playwright inspection/screenshot suite with explicit evidence-method and claim boundaries. - Implemented a model-independent deterministic trajectory runner with versioned scenario and policy contracts, stable metrics, explicit failure attribution, and hard lifecycle safety gates. - Implemented a protocol-backed output projection boundary. - Implemented a pure Markdown link materialization helper. - Implemented a pure provider-neutral calibration evaluator with versioned evidence identities, deterministic Wilson intervals, explicit failure attribution, sufficiency rules, and all source-spec promotion gates. - Implemented a repository-local planning candidate model that identifies incomplete frontier artifacts, preserves canonical hierarchy order, classifies actionable and blocked work, reports bounded completeness counts,. - Implemented a repository-owned release-readiness gate that composes deterministic docs publication, the website production build, cross-application output verification, the static Vercel contract, canonical output. - Implemented a reusable performance benchmark contract for deterministic cold/warm workflow measurement and explicit blocking versus advisory regression gates. - Implemented a shared artifact-family detector in `src/lib/validation/artifact-family.ts` and exported it from `src/lib/validation/index.ts`. - Implemented a shared context-pack builder that discovers section-aware artifact evidence, deduplicates by strongest relevance, ranks deterministically, and emits trust-labeled hashed excerpts with stable locators. - Implemented a shared immutable seven-lane trust registry and added derived, source-specific trust evidence to prompt rendering, artifact context, context packs, workflow explanation, and resume inspection/resumption. - Implemented a shared, read-only artifact-context resolver that composes existing work-selection freshness and precedence, planning next-action evidence, front-matter lifecycle state, and authoritative command. - Implemented a typed command descriptor contract and made the existing command registration list descriptor-authoritative. - Implemented a typed incremental freshness index for canonical source snapshots and generated evidence. - Implemented a typed, ordered action-relevance policy registry and descriptor-backed classifier. - Implemented a versioned vendor-neutral execution-profile contract and integrated explicit profile evidence into the read-only task readiness result. - Implemented a versioned, bounded, workspace-keyed user-local resume-capsule store. - Implemented accepted-residual-specific reconciliation review wording and tests. - Implemented an authoritative canonical policy registry and compact composition seam. - Implemented an exported task-scoped changed-path report helper for validation code. - Implemented an inventory-derived cross-application verifier for website summary routes, exact documentation destinations, retained website ownership, and authored plus built application output. - Implemented an isolated derived-cache lifecycle and opt-in bounded decision-trace projection on top of milestone 01's strict source hash/revision evidence contract. - Implemented an isolated synchronous recovery coordinator over the milestone 01 and 02 primitives. - Implemented an offline critical-journey matrix validator plus a Playwright Chromium harness configured to reuse that matrix across narrow and wide browser projects. - Implemented blocking no-write active-artifact conflict detection in the shared planning update path. - Implemented bounded deterministic descriptor search and exact single-command description as read-only protocol commands. - Implemented canonical full-set declaration enforcement for phase, milestone, and task scaffolding. - Implemented changed-path evidence classification for runtime gate consumers. - Implemented changed-path evidence review for `implementation-summary review`. - Implemented compatibility reporting boundaries for duplicate canonical and legacy overview candidates. - Implemented coverage-preserving decomposition recommendations with fail-safe escalation for incomplete or ambiguous splits. - Implemented declared-later-work classification in reconciliation review. - Implemented declared-task-driven milestone reconciliation evidence collection. - Implemented descriptor-derived native tool manifests for one command or the full registry. - Implemented deterministic advisory task sizing across ten independently visible complexity signals. - Implemented deterministic first-pass command contracts for the declared `day-shift version ...` subcommands. - Implemented deterministic inference artifact generation from the canonical documentation collection using the shared fail-closed publication eligibility contract. - Implemented deterministic pagination primitives and protocol metadata. - Implemented disposition-aware `validation links-check` classification for missing local trace-link targets. - Implemented disposition-specific target normalization, deterministic id derivation, status validation, migrated replacement-target enforcement, retired/deleted replacement rejection, and duplicate disposition id. - Implemented evidence-aware stale message-source downgrade support for planning heuristics and review callers. - Implemented exact byte-aware protocol envelope serialization with compact/pretty modes, stabilized rendered-byte metadata, deterministic bounded/minimal fallback, stable error-blocker grouping, actionable recovery, and. - Implemented expanded verbose text rendering from the shared agent orientation data. - Implemented explicit, versioned profile decision evidence with validated rationale, source evidence, sizing score, disposition, and rollback expectations. - Implemented fail-closed parsing, runtime record validation, unsupported-version rejection, duplicate identity rejection, and deterministic two-space JSON serialization for trace-link disposition storage documents. - Implemented family-aware lifecycle status evidence for metadata update rejection and planning review hygiene. - Implemented local selector expansion for partial selectors and `latest-installed`. - Implemented nearest `.day-shift-version` discovery in the shared version selection resolver. - Implemented non-dry-run `link disposition apply` execution for migrated dispositions. - Implemented one deterministic, fail-fast release-gate orchestrator that runs the existing website and documentation checks in dependency-safe order and identifies the first failing gate. - Implemented opaque selection precondition tokens, workspace lock serialization, compare-and-write validation, token replay rejection, bounded lock recovery, and explicit stale-only cleanup in the selection library. - Implemented ordered installation-intent and purchase funnel contracts and wired representative landing, installation, documentation, pricing, plan-selection, and checkout-handoff signals through milestone 01's. - Implemented parent-child drift checks for planning review surfaces. - Implemented pre-write linked-slice integrity checks for `spec update` when a command touches `linked_slice.*`. - Implemented production-browser LCP, INP, and CLS collection through milestone 01's validated analytics seam, plus deterministic raw build-input budgets and an explicit pending representative-traffic baseline contract. - Implemented prompt-family front matter validation in the artifact-shape validator and added a template-family guard that rejects prompt-only front matter fields on template Markdown. - Implemented pure apply-evidence helpers that normalize evidence paths, attach evidence without mutating lifecycle decision fields, derive a disposition revision identifier, and classify rewrite eligibility only for. - Implemented read-only breakout task requirement checks in planning review. - Implemented read-only contract-to-runtime handoff detection in planning review. - Implemented read-only derived-state drift evidence for `structural-pressure report`. - Implemented read-only documentation-loop detection in planning review. - Implemented read-only duplicate closeout artifact detection in `implementation-summary review`. - Implemented read-only prompt-manifest and template-manifest validation in the artifact-shape JSON path and added template inventory reporting for destination routing gaps. - Implemented read-only version selection from `.day-shift/local.toml` and `.day-shift/config.toml`, with local config overriding shared config after `.day-shift-version` precedence. - Implemented reconciliation build output improvements: empty remaining-work sections now render as `None.`, completed-task rollups use clearer draft-ready wording without metadata completion, and validation review. - Implemented reconciliation review runtime evidence checks for runtime and hybrid completed task summaries. - Implemented retired missing-input classification. - Implemented selected-artifact planning metadata consistency checks for write-capable planning update commands. - Implemented server-created Stripe upgrade checkout. - Implemented server-only prior-license verification and the `/api/upgrade/eligibility` POST route. - Implemented shared planning-language warning support for review surfaces. - Implemented shared structured no-write evidence primitives in the command capability output layer. - Implemented shared validation finding taxonomy fields on the `ValidationFinding` envelope and centralized default mapping in `createValidationFinding`. - Implemented static pricing, FAQ, purchase, and upgrade pages from the shared marketing content source. - Implemented static robots/sitemap surfaces, truthful global and FAQ JSON-LD, and focused discovery regression coverage. - Implemented structured validation-exception enforcement for runtime and hybrid implementation-summary review. - Implemented sync eligibility regression coverage for completed-looking reconciliation artifacts whose declared task summaries remain incomplete. - Implemented text rendering and registered the read-only `link disposition preview` command under a new `link disposition` command family. - Implemented the Runtime Delta task-definition contract. - Implemented the `/known-limitations` page and extended foundation validation to enforce public boundary page content, wiring, local-first claims, and server-only exclusions. - Implemented the `/support`, `/privacy`, and `/recovery` public pages from the shared boundary content source and added a reusable static boundary page renderer. - Implemented the additive full action-posture contract and a shared output-safety seam. - Implemented the contract closeout boundary in implementation-summary review. - Implemented the execution-mode metadata contract across task and implementation-summary artifact generation and review gates. - Implemented the first `link disposition apply` command surface with explicit selector validation and dry-run-only execution. - Implemented the full-orientation text renderer for the agent command family. - Implemented the lightweight promotion-pressure detector family in the existing planning heuristic pipeline. - Implemented the repository path-policy contract for documentation path classification. - Implemented the retained blocker disposition. - Implemented the reusable command inventory model in `src/lib/output/command-inventory.ts` and exported it through `src/lib/output/index.ts`. - Implemented the shared agent orientation TypeScript model in the existing agent command module. - Implemented the shared command capability model in `src/lib/output/command-capabilities.ts`, exported it through `src/lib/output/index.ts`, and added focused unit coverage in `tests/lib/command-capabilities.test.js`. - Implemented the shared documentation frontmatter JSON Schema and composed its required enum semantics into Starlight's directly loaded documentation collection. - Implemented the shared planning overview path policy in `src/lib/paths/planning-overview-policy.ts` and exported it through `src/lib/paths/index.ts`. - Implemented the shared root-context evidence model for `day-shift agent`. - Implemented the shared synchronous atomic single-file replacement primitive. - Implemented the shared synchronous multi-file mutation coordinator. - Implemented the shared typed terminal-failure contract. - Implemented the shared website visual token layer and foundational component module for operational route shells. - Implemented the short correction-focused text renderer for `day-shift agent remind`. - Implemented the typed scoped-health domain contract and bounded report composition. - Implemented the versioned executable-workflow action contract and extended authoritative command descriptors with explicit preconditions, stable transition identity, and expected postconditions. - Implemented unsupported and wrong-family status-field rejection evidence. - Implemented validation-evidence and acceptance-result specificity checks in `implementation-summary review`. - Implemented version-manager alias resolution and mutation. - Implemented workspace-keyed user-local work selection storage with validated named sessions, bounded provenance, artifact content hashes, monotonic revisions, freshness inspection, targeted clear behavior, and. - Integrated authoritative descriptor metadata into command inventory and agent guidance. - Integrated byte budgets into JSON emission, registered compact/pretty serialization controls, restricted explicit budgets to approved read-only commands, applied an automatic 8 KB compact-output ceiling to those. - Integrated descriptor-backed action selection into scoped doctor. - Integrated generation, metadata checking, static rendering, and fail-closed post-build leakage verification into the documentation build. - Integrated optional default-capped context packs into `agent context`, registered the boolean descriptor input, and added executable pack discovery, ranking, excerpt, trust, and milestone-01 parity coverage. - Integrated protocol v1 into the shared JSON output boundary and runtime discovery. - Integrated safe global pagination for approved read-only JSON commands. - Integrated selected-artifact scoped health and shared descriptor-backed relevance classifications into agent context. - Integrated shared output controls at the root CLI and JSON emit boundary. - Integrated task-01 terminal failure metadata at the shared CLI boundary. - Integrated task-scoped changed-path evidence into implementation-summary build. - Integrated the release publication consistency validator into the website validation entry point. - Integrated the shared artifact-shape validator into validation smoke as a dedicated `artifact-shape` cross-artifact alignment lane. - Integrated the shared taxonomy fields into the representative template/manifest reporting surface. - Inventoried generated reconciliation draft gaps: review-clean empty sections were not produced by default, generated status/final notes were generic, and validation rollups kept only the first validation line from each. - Inventoried noisy reference searches. - JSON output already exposes the shared `implementationSummaryCloseoutGuidance` model from task 01 for both `agent`/`agent orient` and `agent remind`; this task preserved that data path while adding the text renderers. - Mapped Day Shift's principal implemented domain concepts, artifact lineage and pairing, parser/generator boundaries, and repository, generated, release, user-local, Git, and external persistence boundaries. - Mapped the retained CLI/runtime V1 files to V2 homes: workspace-root coverage needed a new V2 workspace test file, while validation-runtime and metadata-update coverage already lived in V2 command-family files. - Migrated completion command coverage into V2 subprocess tests. - Migrated implementation-summary build and review command coverage into V2 subprocess tests. - Migrated implementation-summary update command coverage into V2 subprocess tests. - Migrated planning navigation, planning review, and task readiness document reads to `parsePlanningArtifactDocument` while preserving their error adapters and section-map behavior. - Migrated reconciliation build and review coverage into V2 subprocess tests by mechanically copying the legacy suite and replacing the in-process runner with `tests_v2/helpers/cli-runner.js` plus compatible isolated. - Migrated reconciliation update coverage into V2 subprocess tests by mechanically copying the legacy suite and replacing the in-process runner with subprocess execution and compatible isolated workspace setup. - Migrated representative planning creation command coverage into the V2 subprocess suite. - Migrated representative planning update command coverage into the V2 subprocess suite. - Migrated retained agent orientation and config runtime CLI coverage into subprocess-first V2 tests. - Migrated retained direct library coverage into `tests_v2/lib` while preserving direct `dist/lib/**` imports and avoiding CLI subprocess wrappers. - Migrated retained init workflow coverage into `tests_v2/init` while preserving workspace/config/state isolation and direct init helper contracts. - Migrated retained manifest update, metadata sync/inventory, and metadata update command-family coverage into subprocess-first V2 tests. - Migrated retained prompt edit/init/update and template materialize/list command-family coverage into subprocess-first V2 tests. - Migrated runtime validation command coverage into V2 subprocess tests by copying `validation-runtime.test.js` and its runtime helper, then replacing in-process CLI execution with subprocess helper calls. - Migrated spec registry command coverage into the V2 subprocess suite. - Migrated template update command coverage into V2 subprocess tests by copying the legacy suite and replacing the in-process runner with `tests_v2/helpers/cli-runner.js`. - Migrated validation artifact-shape and link discovery/source-location parsing to the shared document seam. - Moved fixture data from `tests/fixtures` to `tests_v2/fixtures` and updated V2 license imports plus runtime smoke fixture seeding. - No prompt Markdown bodies, prompt entries, front matter fields, template references, prompt resolution behavior, or CLI behavior were changed. - No template Markdown bodies, template entries, placeholder structures, required artifact headings, scaffold destinations, or CLI behavior were changed. - Normalized CRUD command output through shared read and mutation emit helpers. - Normalized shim runtime failures into stable diagnostics with distinct reason codes, recovery guidance, and JSON error findings through the existing output envelope. - Polished download and release metadata routes with milestone 01 visual primitives. - Polished install, license, and troubleshooting routes with the shared visual primitives. - Polished pricing, purchase, upgrade, success/license-delivery, and recovery routes with shared visual primitives. - Polished the FAQ route with shared visual primitives and verified that support, privacy, and known-limitation pages continue through the shared `BoundaryPageView` shell adopted earlier in the phase. - Populated the shared command capability registry in `src/lib/output/command-capabilities.ts` with existing Day Shift top-level and nested command surfaces. - Preserved milestone 01's first-contact hero while completing the homepage journey with a focused closing conversion, simplifying grouped navigation around buyer intent, and adding a compact shared footer with canonical. - Preserved the default text output behavior for the agent command family through focused regression coverage. - Produced the integrated phase repository model covering domain, artifact relationships, execution, lifecycles, persistence, and human/agent/CLI actor boundaries from inspected implementation and data flow. - Propagated artifact-scoped links-check lifecycle findings into `validation smoke` and `validation rollup`. - Proved command, agent, and doctor compatibility and recorded structural/dependency evidence. - Proved the shared parser's lossless behavior across all supported planning artifact families and representative malformed documents. - Published a descriptor-derived inventory for all 140 callable commands, a public command-family ownership index, and an approved static contract generated through the existing documentation publication pipeline. - Published and registered a manifest-grounded public reference catalog for all 28 prompt entries and 14 template entries, including version evidence, lifecycle consumers, variables or placeholders, supported prompt. - Published and registered automation reference, command-registration architecture, structured-contract decision, and command-contribution guidance. - Published and registered the canonical evidence-review and reconciliation workflow. - Published and registered the canonical intake-to-implementation workflow. - Published and registered the canonical operating-model concept page. - Published and registered the canonical resume, trace-link lifecycle, archive, recovery, and release-handoff workflow. - Published and registered the core lifecycle command reference with exact family roots, descriptor discovery, shared contracts, safe examples, workflow links, and recovery guidance. - Published and registered the operations reference covering configuration, diagnostics, licensing, versions, migration, customization, resume, archive, and release consequences. - Published evidence-scoped platform, runtime, shell, release, and coding-assistant boundaries from first-party manifest and test sources, and rendered them on the homepage. - Published one buyer-facing trust contract across shared chrome and focused support/privacy content. - Published the canonical configuration-and-health guide, connected it to the settled getting-started and initialization journey, registered it in the closed page inventory and docs path guard, and grounded its. - Published the canonical upgrade guide and registered its public route. - Published the canonical workspace customization guide with command-by-command seeding, listing, editing, updating, materialization, review, validation, preservation, failure, and ownership boundaries. - Published the canonical workspace-initialization guide, linked it into getting started, and extended the closed page inventory. - Published the existing 0.1.10 release-pipeline download bundle into website-visible public download paths. - Published the operational companion to the completed catalog, grounded in the shipped resolver, rendering evidence model, manifests, command descriptors, initialization guide, and milestone 01 reconciliation. - Published the protocol-v1 JSON Schema 2020-12 catalog with seven stable schema documents covering envelopes, findings, actions, artifact documents, cursors, recovery actions, and feature manifests. - Ran final V2 closeout validation and created `final-v2-closeout-evidence.md`. - Ran final build, default V2 test, explicit V2 suites, and closeout searches. - Ran final targeted validation for command-surface adoption and recorded the evidence in `.day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/validation-and-gap-report.md`. - Ran focused retained legacy checks for `tests/cli/cross-command-workspace-root-regression.test.js` and recorded the blocker evidence in the milestone-local inventory. - Ran the focused final validation evidence for the Markdown link materialization phase after the command boundary regression was in place. - Reconciled `.day-shift/references/planning-layers.md` against current artifact terminology, lifecycle workflows, prompt handoffs, and adjacent references. - Reconciled website-owned buyer copy with the accepted commercial, recovery, and trust behavior; added `/demo` to the documentation migration inventory; preserved the deleted `docs-content.ts` entry as retired and. - Recorded `pnpm test` as the default full V2 suite and retained `test:v2` plus `test:v2:cli` as explicit V2 validation lanes. - Recorded an immutable commit anchor, local version context, dirty-working-tree boundary, evidence provenance classes, six-state evidence taxonomy, and reusable citation record for the EADL qualification analysis. - Recorded current, independent archival recertification evidence for specs 15, 16, 17, 20, and 21. - Recorded final V1 disposal classifications and intentional non-V1 retained output-capture behavior. - Recorded final runner follow-up classifications and validation evidence. - Recorded trace-link lifecycle release handoff evidence and updated the current 0.1.10 release-note handoff copies. - Refined the guide's command-map and reference-handoff section so reusable command, registry, planning-layer, validation/review, metadata, and prompt/template detail routes to canonical reference pages after the. - Reframed the homepage first contact around a familiar coding-agent continuity problem, a durable repository outcome, and a concise explanation of Day Shift's relationship to existing assistants. - Registered the `link disposition` CRUD command module under the existing disposition family and preserved the preview subcommand as a sibling route. - Registered the first-pass `day-shift version` command family through the existing command registry. - Registered the initial `link materialize` command contract under the existing `link` command family. - Registered the primary `day-shift agent` command family through the existing command registry and added a minimal read-only orientation response using the standard Day Shift success envelope. - Removed superseded scanner bodies from the five migrated callers and proved the combined planning/validation regression set. - Removed the legacy `tests/` tree after fixtures moved to `tests_v2/fixtures` and helpers were deleted. - Removed the static upgrade checkout action from commerce metadata, kept ordinary purchase checkout redirects intact, and added server-only Stripe upgrade checkout configuration examples for the follow-on session. - Rendered entrypoint first-read guidance from the shared `rootContext.agentEntrypoint` status data. - Rendered implementation-summary closeout expectations from the shared orientation model across the agent command output surfaces. - Rendered reconciliation readiness guidance from the shared structured model into compact text, verbose text, reminder text, and closeout guidance. - Rendered repository-memory checkpoint boundary guidance across the agent orientation surfaces. - Rendered the closeout evidence-boundary model in compact orientation text, verbose orientation text, and correction-focused reminder text. - Rendered the command-surface taxonomy in compact text output using the same shared `data.commandSurfaces` entries already used by verbose text and JSON output. - Rendered the expanded planning-flow guidance in compact and verbose `day-shift agent` text output and added focused coverage proving the same shared guidance is present in JSON. - Rendered the full planning and spec discovery recommendation set through the shared orientation data by renaming the text lane to `Discovery recommendations:` and keeping text output sourced from. - Rendered the guardrail data model in agent orientation output and added focused coverage for finding severity, no-invented-state, and selected-artifact evidence boundaries. - Rendered the shared `discoveryRecommendations` data in text orientation output under a compact health and runtime discovery section. - Rendered the shared root-context evidence in `day-shift agent` text output and aligned reminder text with the actual detection source from `rootContext`. - Repaired spec 15's registry linkage through the supported `spec update` command. - Replaced selected duplicated reference-level explanations with concise local context and repository-relative links to verified canonical homes. - Replaced structural placeholders and added canonical installation, license-management, troubleshooting, Human-Agent-Contract concepts, and technical limitations content. - Replaced the foundation homepage shell with launch-ready Day Shift product positioning rendered from `apps/website/content/marketing-content.ts`. - Replaced the generic deferred `version doctor` response with a read-only runtime context report for version-manager root, selected metadata, selected version, managed package path, shim mode, manager entrypoint, PATH. - Repointed package test scripts to the V2 runner, deleted the stale legacy runner, repaired V2 fixture paths, and hardened V2 sandbox cleanup retries. - Reproduced the retained blocker and localized it to a retired overview filename expectation in the init-derived planning fixture. - Retired 21 eligible legacy CLI test files whose equivalent V2 coverage was validated in milestone `01-equivalent-coverage-review`. - Retired V1 version install source and version state layout files after validating V2 version owner files. - Retired `tests/cli/metadata-update.test.js` after confirming V2 metadata update command coverage passes. - Retired `tests/cli/validation-runtime.test.js` after confirming `tests_v2/cli/runtime/validation-runtime.test.js` passes and remains in the CLI V2 validation lane. - Retired planning overview, release notes, and release version parser V1 files after validating their mapped V2 owner files. - Revised `.day-shift/references/commands.md` into a fuller command-family reference for onboarding and planning workflows. - Revised `.day-shift/references/metadata.md` into a fuller metadata reference. - Revised `.day-shift/references/spec-registry.md` into a fuller spec-registry reference. - Revised `.day-shift/workflows/01-start-here.md` so human startup guidance begins with a concrete procedure for CLI resolution, workspace-root discovery, read-only navigation, active artifact selection, workflow. - Revised `.day-shift/workflows/README.md` from a mixed workflow list into a human-facing routing index. - Revised the release command-family help regression so `release check --help` asserts its read-only validation posture instead of asserting the absence of the adjacent `--dry-run` option. - Revisited the legacy runner decision after resolving the retained blocker. - Routed `day-shift agent remind --format json` to the structured `AgentReminderData` payload while preserving the standard success envelope. - Selected a backward-compatible `planning gap-report --artifact ` alias for artifact-focused gap reports, with conflict handling when both selectors disagree. - Selected a retained-coverage fixture update, not retirement. - Shared version-manager root resolution now lives in `src/lib/version-manager/state-layout.ts`, with the existing shim runtime delegating through that helper. - Sharpened license preservation and mixed-status regression assertions. - Strengthened focused planning creation coverage with parent-link assertions for generated milestone and task artifacts. - Strengthened milestone reconciliation task-summary eligibility so completed metadata is not enough for rollup. - Strengthened the canonical documentation check from presence-based inventory validation to a closed page-disposition and public-page substance contract. - Strengthened the existing agent command no-write tests so each present-entrypoint command loop captures both the full fixture tree and the representative artifact contents before and after execution. - Strengthened the policy-pack contract test so CI examples must remain provider-neutral, name reusable Day Shift validation/review commands, and preserve explicit write-capable repair guidance. - Synchronized spec 20 lifecycle metadata bottom-up from completed reconciliation evidence: 17 stale milestone overviews, five stale phase overviews, and the slice overview now report completed status through supported. - Synthesized the evidence-backed `EADL-adjacent architecture` classification at 0.94 confidence, the repository-scoped human-agent planning and evidence-orchestration alternative, eleven complete qualification gaps, and. - The existing compact `closeout` list remains compatible with current callers and now includes the stronger before-completion boundary plus the explicit statement that `day-shift agent` reports guidance only and does. - The final V1 retirement inventory was recorded. - The final runner decision was recorded: retain `pnpm test` and `scripts/run-node-test-files.js` until the remaining workspace-root blocker is fixed, migrated, or explicitly retired by a dedicated owner. - The install writer now records `versions//metadata.json` and timestamped receipts under `installs/receipts/` after successful package copy. - The map assigns command, registry, metadata, prompt/template, validation/review, planning-layer, and structural-pressure responsibilities to existing canonical homes, existing partial homes, or clearly labeled planned. - The markers identify each workflow file's human-facing responsibility near the top, route agent lifecycle execution to `.day-shift/agents.md` and the relevant `.agent-lifecycle-guide.md` files, and route broad reusable. - Tightened evidence-aware review findings so downgraded stale-source findings provide lifecycle-continuation recovery and declared-later-work findings include structured affected-path evidence for the parent declaration. - Tightened the prompt-ready boundaries for the full-orientation text renderer. - Updated `.day-shift/workflows/02-plan-from-spec.md` with explicit planning evidence-navigation guidance. - Updated `.day-shift/workflows/03-implement-from-task.md` and `.day-shift/workflows/04-summarize-and-reconcile.md` with explicit evidence-navigation guidance for implementation, task-summary closeout, milestone. - Updated `README.md` so repository users and automation agents can discover the agent orientation command before broader discovery commands. - Updated active task execution guidance so migrated CLI/test-infrastructure validation points at the V2 lane. - Updated active task prompt and implementation workflow guidance so default validation now targets the V2 lane. - Updated agent orientation command-surface output to derive representative command posture from the shared command capability registry. - Updated agent, workflow, and prompt guidance so trace-link lifecycle disposition findings are consistently treated as read-only validation evidence unless a separate write-capable disposition command is explicitly. - Updated broader Day Shift guidance so agents have a reusable command-surface evidence rule: consult `commands inventory --format json` before inferring command availability, lifecycle role, write posture,. - Updated implementation and reconciliation workflow handoffs. - Updated lifecycle workflow guidance so task, milestone, phase, summary/reconciliation, and shared prompt-routing workflows preserve execution-mode evidence through closeout. - Updated milestone scaffold generation to parse parent phase body sections, carry declared milestone descriptions through full-set expansion, render concrete milestone overview sections, and preserve incoming upstream. - Updated operator-facing environment, Stripe setup, launch readiness, and README handoff material so automated 50% upgrade checkout is documented as a server-created flow after prior-license verification, separate from. - Updated public purchase, upgrade, verified-delivery, and recovery content to match the implemented server-owned commerce journey. - Updated read-only planning review traversal to use the shared planning overview path policy for phase and milestone overview inputs and milestone children beneath a phase. - Updated reconciliation build so all-complete milestone task evidence produces completed reconciliation metadata and completed review-clean section language. - Updated reusable command references from the adoption map. - Updated root and agent command help surfaces so the new command family is discoverable as an agent orientation guardrail. - Updated scaffold-facing command help for phase and milestone creation so parent overview examples use the canonical layer-specific filenames selected by the shared planning overview path policy. - Updated standard task scaffold generation to inherit declared task descriptions and parent milestone evidence into generated task definitions. - Updated the boundary map with destination verification evidence for all 20 mapped human-workflow guidance items. - Updated the first-project guide flow so it explicitly frames the guide as a fresh-repository walkthrough, adds concrete expected-output checkpoints after the major first-run steps, and clarifies that normal planning. - Updated the human workflow entrypoints so existing-repository users can discover `.day-shift/workflows/00-existing-repository-with-day-shift.md` from the workflow index and start-here guide. - Updated the implementation-summary build section resolver so completed summaries normalize optional none-state closeout sections while preserving pending behavior for incomplete evidence. - Updated the planning workflow handoff map in `.day-shift/workflows/02-plan-from-spec.md`. - Updated the standard and lightweight implementation-summary templates with durable validation-exception and runtime-evidence-boundary sections. - Updated user-facing task, implementation, reconciliation, milestone, and phase prompts so prompt handoffs preserve execution mode, Runtime Delta expectations, structured validation exception evidence, and evidence-only. - Updated website validation to enforce the completed commerce entrypoint contract. - Updated workflow and user-prompt guidance so lifecycle, scaffold, validation, review, implementation-summary, reconciliation, active-artifact, and command-placeholder language points to executable command contracts. - Updated workflow, prompt, reference, and tutorial guidance so newly generated slice, phase, and milestone overview artifacts are described with canonical layer-specific filenames: `slice-overview.md`,. - Validated and closed read-only trace-validation enforcement. - Validated and closed selected-artifact scope preservation across links-check, smoke, and rollup validation output. - Validated and closed the parent/upstream trace-link implementation for links-check. - Validated migrated init/lib V2 coverage, deleted legacy `tests/init` and `tests/lib` files with equivalent V2 evidence, and retained shared helpers/fixtures for later cleanup. - Validated that focused V2 fixture consumers pass, legacy helper/fixture imports are gone, and `tests/` is removed. - Validated that milestone-owned retained CLI/runtime V1 files are retired, no remaining legacy CLI test imports `tests/cli/runtime-helpers.js`, and the CLI-focused V2 lane passes. - Validated the implementation-summary V2 command family after build/review and update migrations. - Validated the legacy retirement diff. - Validated the lifecycle-friction release handoff artifact, release-note copy, changed-path scope, and phase planning state. - Validated the migrated V2 CLI family set recorded in `coverage-inventory.md`. - Validated the migrated template, completion, and runtime validation V2 files as a coherent milestone family. - Validated the reconciliation V2 command family after build/review and update migration. - Validated the repointed default runner, explicit V2 lanes, and active-reference cleanup. - Verified compatibility routing after the stale-wording and canonical-link cleanup milestones and corrected remaining prompt/template compatibility notes that still described the workspace as pre-CLI or manual-only. - Verified discovery-guidance regression coverage in `tests/cli/agent-command-surface.test.js`. - Verified entrypoint-status regression coverage in `tests/cli/agent-command-surface.test.js`. - Verified focused regression coverage for implementation-summary closeout blockers and sufficient-evidence acceptance cases. - Verified focused regression coverage for task-readiness mode gates, including missing execution mode, unsupported execution mode, missing Runtime Delta, incomplete Runtime Delta, and complete runtime handoff cases. - Verified implementation-summary review closeout gates for runtime and hybrid changed-path evidence, Runtime Delta target alignment, executable validation evidence, and mode-aware runtime-claim language. - Verified task generation, reconciliation build/review, metadata update, and metadata inventory paths already resolve canonical and supported legacy overview inputs through the shared policy. - Verified the existing fixture-backed root-context regression coverage in `tests/cli/agent-command-surface.test.js`. - Verified the task-readiness review gate that blocks implementation handoff when `execution_mode` metadata is missing or invalid, and when runtime or hybrid tasks do not provide complete Runtime Delta evidence. - Wired `day-shift version current` to the shared version selection resolver and added command-level coverage for environment precedence, missing configured selector failure, single-installed fallback, and. - Wired `day-shift version install --from --version ` to the managed install writer, added command output for text/JSON envelopes, enabled positional option parsing so install-level `--version` is treated. - Wired `link materialize` dry-run and selected-artifact write execution to `validation links-check` evidence and the Markdown rewrite helper. - Wired explicit shim-mode dispatch into CLI startup. - Wired scaffold destination construction, parent input resolution, declared-child gap inference, metadata parent-link inference, and write-summary classification to the shared planning overview path policy. - `.day-shift/agents.md` now reflects the current repo-local CLI posture: some command surfaces are available through `node dist/cli/index.js`, while the installed `day-shift` command still must be verified before use. ## Known Follow-Up Work - A dedicated follow-up should fix, migrate, or explicitly remove the retained workspace-root blocker before `pnpm test` is repointed or removed. - A dedicated follow-up should fix, migrate, or explicitly retire the retained workspace-root regression before `pnpm test` is repointed or removed. - A future machine-readable command inventory export would reduce manual help/source review. - A machine-readable command inventory export remains discovered follow-up work. - Accepted by declared phase ordering: later milestones integrate this decision into routes, navigation, Pagefind, sitemap, inference generation, contract export, and final static leakage verification. - Accepted by declared phase ordering: route, navigation, Pagefind, sitemap, and final static-output filtering are later milestone responsibilities. - Accepted disposition: task implementation-summary reviews carry advisory warnings for task-local `task-definition.md` and `implementation-summary.md` closeout edits being outside implementation target paths. - Accepted operational residual: live provider receipt and provider-side internal-production filtering remain unverified in-repository, carried forward from milestones 01 and 02. - Accepted residual release-fixture drift: `0.1.8` is sufficient for this phase's read-only handoff regression because it exercises archive payload package metadata, website metadata, immutable download paths, and. - Accepted residual: Phase 04 still owns actual Stripe checkout, webhook verification, signed license delivery, upgrade eligibility checks, and recovery logic. - Accepted residual: Phase 04 still owns checkout, recovery, and signed license delivery behavior. - Accepted residual: Phase 04 still owns commerce, recovery, and signed license delivery behavior. - Accepted residual: The docs intentionally describe current PATH troubleshooting generically because exact shell mutation behavior is owned by release-pipeline installer assets. - Accepted residual: the readiness review warning about source-spec message evidence is carried forward as non-blocking lifecycle evidence because the selected phase and milestone contracts narrow the active work. - Accepted validation limitation: a production Astro build requires Node `>=22.12.0`; this environment provides Node `20.19.0`. - Accepted warning: readiness review flagged broad `tests/cli/` target evidence. - Accepted warning: readiness review flagged broad target paths (`tests/cli/`, `tests_v2/cli/`) as weak evidence. - Accepted warning: readiness review initially flagged planning-language/decomposition concerns; the objective was tightened to name the concrete inventory artifact update. - Accepted. - Accepted: the unrelated aggregate-suite blocker does not prevent milestone acceptance because every milestone-owned validator ran directly and passed, lint/typecheck/build passed, and the failing inventory surfaces. - Accepted: the unrelated aggregate-suite blocker does not prevent milestone acceptance because every milestone-required validator ran directly and passed, lint/typecheck/build passed, and the failing inventory surfaces. - Accepted: the unrelated aggregate-suite blocker does not prevent this milestone's acceptance because every milestone-required validator ran directly and passed, lint/typecheck/build passed, and the failing inventory. - Accepted: the unrelated stale config-test assertion remains outside this documentation milestone. - Active package-script behavior still points `pnpm test` at `scripts/run-node-test-files.js` until milestone 05. - Actual private persistence and operator record management remain deployment concerns outside repository-visible public assets. - Actual user-local store contents and complete external/environment snapshots remain `Not verifiable`. - Actual user-local store contents and external/environment snapshots remain `Not verifiable`; task 02 must preserve that limitation while integrating execution and actor models. - Add `execution_mode` to the selected spec 13 fixture through its owning planning workflow, then rerun the command-posture gate and recertify spec 17. - Add bounded lightweight and emergent guidance to the shared planning model. - Add broader conflict-reporting regression coverage for later command families as downstream milestones wire more validation, review, completion, and documentation surfaces to the shared overview path policy. - Add fixture-based mutation checks for classified read-only commands in milestone `03-command-posture-regression-tests`. - Add spec-index and parent-planning traceability verification. - Additional prompt-manifest list/diff surfaces could later expose the same prompt-manifest findings outside artifact-scoped validation. - Additional scaffold-family update surfaces may need explicit command contracts if future scaffold assets gain front matter and become writable through a dedicated scaffold update lane. - Administrative: unrelated dirty workspace changes were observed outside this milestone's owned paths and were not reverted. - Adopting the primitive in existing writers is intentionally deferred; this task changes no callers. - Adversarial prompt injection, truncation, cursor drift, sensitive-value redaction, and payload baseline expansion remain explicitly assigned to milestone 02; provider-backed calibration remains milestone 03. - Advisory readiness warnings about message-sourced upstream evidence were reviewed and accepted because current phase scope plus milestone 01 reconciliation provide active implementation evidence. - Advisory readiness warnings about message-sourced upstream evidence were reviewed and accepted for this task because current phase scope and prior completed milestone reconciliations provide the active implementation. - Alias routing and no-write snapshot proof are intentionally handled by later tasks in this milestone. - Alias, partial selector, and `latest-installed` behavior are intentionally deferred to milestone 03. - Alias, partial selector, and `latest-installed` behavior remain deferred to milestone 03. - Alias, partial selector, and `latest-installed` behavior remain intentionally deferred to milestone 03. - Alias, partial selector, and `latest-installed` sources remain deferred to milestone 03. - Align `tests_v2/cli/config/runtime.test.js` with the current canonical relative-path provenance contract in the owning runtime workstream; no new milestone task is required for this documentation outcome. - An actual NVDA/VoiceOver session remains valuable release-level evidence and is recorded as discovered validation work, not claimed here. - Any public package rebuild, checksum refresh, archive payload update, or generated release manifest update should run through a separate release workflow. - Any release archive, checksum, manifest, or archive payload update remains a separate release workflow. - Apply command mutation remains deferred to phase `04-forward-link-apply-workflow`. - Archive payload release-note copies under `release/0.1.10/archive-payloads/` were not regenerated. - Broad `tests/cli/metadata-update.test.js` compatibility fixture failures should be resolved separately so full-file metadata validation can serve as a clean release gate. - Broad guidance adoption is wording-based, so future prompts/templates may still need opportunistic tightening when they introduce new command-family examples. - Broader command families beyond the targeted scaffold, task generation, gap-report, and reconciliation checks may need additional conflict-reporting coverage in later milestones. - Broader pre-existing documentation edits in `.day-shift/workflows/01-start-here.md` are outside this task's ownership and were not reviewed as part of this task beyond confirming this task's navigation. - Broader pre-existing documentation edits in `.day-shift/workflows/01-start-here.md`, `.day-shift/workflows/03-implement-from-task.md`, and `.day-shift/workflows/04-summarize-and-reconcile.md` are outside. - Broader recursive artifact-shape rollup can be planned separately if the project wants repository-wide shape enforcement. - Broader recursive artifact-shape rollup is intentionally out of scope. - Broader repository-wide selector scans remain out of scope; current-workspace selector handling is covered. - Browser-level narrow/wide viewport, keyboard, and assistive-technology review remains with the navigation and accessibility milestones that own those runtime surfaces. - Byte-budget enforcement and bounded fallback remain milestone 03 scope; pagination currently requires callers to select an appropriate lane/page size explicitly. - CI consumers now receive the V2 suite through `pnpm test`; milestone 06 will provide final phase evidence. - CLI task scaffolding initialized task artifact `source_type` as `markdown` even though the registered spec source type is `message`; this milestone corrected the selected task artifacts to preserve index-derived. - Caller adoption and equivalence remain intentionally deferred to milestone 02. - Caller-selected byte budgets, stale/missing source reporting, and visible excluded-candidate evidence remain intentionally sequenced to milestone 03. - Carry the discovered boundary-mapping items into the already-declared later milestones in this phase rather than creating follow-up task artifacts here. - Carry the two discovered-work items into the qualification-and-trace phase contract when that phase becomes active. - Changed-path evidence collection remains planned for milestone `03-changed-path-evidence`. - Checkout creation and discount material constraints remain intentionally deferred to milestone `02-server-created-stripe-upgrade-checkout`. - Classification remains intentionally incomplete until task `02-classify-command-boundaries`. - Classify every inventory entry by audience, current marker, missing marker, and destination lane. - Command-facing reporting remains deferred to task 03. - Command-gap and release-ready sections remain pending for task `02-document-command-gaps-and-release-evidence`. - Command-specific finding producers can gradually adopt `createNoWriteFindingEvidenceDetails` so more existing read-only outputs carry the new rich evidence fields automatically. - Command-specific finding producers can gradually adopt `createNoWriteFindingEvidenceDetails` so more existing read-only outputs carry the rich no-write evidence fields automatically. - Compact text remains near the existing line-count ceiling; task 03 should preserve the concise rendering boundary while adding final equivalence coverage. - Concurrent if-match enforcement is intentionally deferred to milestone 03. - Confidence values express confidence in status assignment, not capability maturity. - Conflict/no-write reporting for duplicate canonical-plus-legacy candidates remains for Task 03. - Consider a future command registry inventory/export command so later guidance audits can avoid manual help/source classification. - Consider a later planning item for repository-wide artifact-shape traversal, baseline policy, and noise controls if broad enforcement becomes desired. - Consider a later task to clean up `tests/cli/metadata-update.test.js` workspace compatibility fixtures so full-file metadata update validation is no longer noisy. - Consider adding a structured command inventory/export command for future guidance audits. - Consider command-specific adoption tasks for read-only producers that bypass shared finding rendering. - Consider exposing any future validation command surfaces through user-callable help before documenting them as supported. - Continue to milestone `02-retained-cli-runtime-v2-migration`. - Continue to milestone `03-retained-lib-and-script-v2-migration`. - Continue to milestone `04-fixture-helper-and-tests-tree-cleanup`. - Continue to milestone `05-v2-default-runner-repoint`. - Continue with `.day-shift/planning/17-programmatic-workflow-enforcement/phases/01-command-capability-and-no-write-boundaries/milestones/03-command-posture-regression-tests/overview.md` when ready to add read-only. - Create `.day-shift/references/prompts-and-templates.md`, `.day-shift/references/commands.md`, `.day-shift/references/spec-registry.md`, `.day-shift/references/metadata.md`,. - Create a compact prompt/template responsibility reference at planned path `.day-shift/references/prompts-and-templates.md` before removing prompt-layer matrices or template cleanup detail from workflow files. - Create planned references for commands, spec registry behavior, metadata, validation/review, and planning-layer relationships before aggressive workflow shortening. - Cross-link coverage is intentionally deferred to task 03 after the validation/review reference task is complete. - Cross-link coverage is intentionally deferred to task 03 after this task and task 01 are complete. - Current coverage validates the shared helper and command-output export surface; task 2 and task 3 still need to bind this helper into no-write regression coverage and prompt/workflow vocabulary alignment. - Decide whether structural-pressure policy belongs in a dedicated `.day-shift/references/structural-pressure.md` document or inside validation/review reference material. - Declared next milestone `02-package-script-and-runner-reference-check` still owns package-script and runner-reference review. - Declared task 02 must close the aggregate foundation expectation drift and add durable stale-copy/documentation-boundary regression coverage. - Dedicated missing-entrypoint no-write coverage remains intentionally deferred to sibling task 03. - Define cleanup readiness gates and classify each mapped item as cleanup eligible, cleanup blocked, or retained in the human workflow. - Define cleanup readiness gates and replace cleanup readiness placeholders with per-item states. - Delete `tests/cli/runtime-helpers.js` in milestone 04. - Detailed option tables remain descriptor-owned through the generated contract to prevent duplicate drift. - Detailed workspace editing/merge flows and upgrade drift recovery remain intentionally owned by milestones 03 and 04; this task does not claim those procedures are complete. - Direct-copy ports for runtime/privacy/cross-layer families exposed fixture drift; the milestone resolved this by replacing them with focused V2 subprocess coverage rather than retaining failing V2 files. - Discovered follow-up: the config runtime suite has one stale absolute-path expectation. - Discovered out-of-scope work: the accidental full-suite run exposed an unrelated release-notes assertion failure in `tests/cli/release-output-lifecycle.test.js`; it was not investigated or repaired under this task. - Discovered repair work is explicit but outside this phase's closeout scope: restore the exact runtime-evidence workflow wording and add `execution_mode` to the selected spec 13 fixture through their owning workflows,. - Discovered unrelated work: documentation migration inventory routes must be reconciled with the public route registry before the aggregate website validation command can pass. - Discovered unrelated work: the license cross-layer init fixture is missing a runtime-evidence policy-pack asset after initialization. - Discovered work for later milestones: the inventory identifies likely boundary-mapping needs in procedural workflow files and manifest reference notes, but no cleanup, relocation, or follow-up task artifacts were. - Discovered work for later milestones: workflow files `02-plan-from-spec.md`, `03-implement-from-task.md`, and `04-summarize-and-reconcile.md` likely need later boundary mapping between human procedure, agent operating. - Do not parallelize `next build` with website typecheck in future validation runs because `.next/types` can be transient while build regenerates it. - Documentation examples and runtime tests remain temporarily out of sync until task 03 completes. - Downstream migration tasks must validate each batch before deleting retained legacy files. - Exact leaf options remain machine-inventory and descriptor owned. - Existing dirty changes in the same workflow and prompt files predated this task closeout; they were preserved and validated rather than reverted. - Existing metadata-update fixture compatibility failures should be handled separately if broad metadata-update validation is required for a later milestone or release gate. - Existing planning artifacts remain legacy `overview.md` files until an explicit migration command or separate migration workflow is introduced. - Existing uncommitted changes outside this milestone remain in the worktree and were preserved. - Existing uncommitted documentation changes are present outside this task. - Existing unrelated dirty workspace state was observed by implementation-summary build. - Existing writer adoption and all coordination semantics remain intentionally deferred beyond this milestone. - Extend these tests in later milestones when schema and information-architecture behavior lands. - External deployment constraints remain: authenticated Vercel project/root linkage, `docs.tnsds.tech` DNS/domain assignment, a hosted preview URL with inspection, and promoted production deployment with post-deploy. - Final V2 build/test execution remains declared for milestone `03-final-v2-closeout-evidence`. - Final alias equivalence should be revisited after the full orientation data model lands in the next milestone. - Final consistency review against templates, workflows, prompts, and adjacent references is intentionally deferred to task 03. - Final marketing, install, pricing, support, and license copy remains owned by later content phases. - Final runner retirement is deferred to milestone 08. - Final terminology and consistency alignment is intentionally deferred to task 03. - First-contact comprehension review with coding-agent users unfamiliar with Day Shift remains carried from milestone 01 at phase scope. - First-contact comprehension review with coding-agent users unfamiliar with Day Shift remains phase-level validation evidence; source assertions do not substitute for that human review. - Five legacy phase-filename advisories remain visible for spec 15; they are non-blocking because the recorded legacy `overview.md` files exist and the completed slice is the linked target. - Fix, migrate, or explicitly retire `tests/cli/cross-command-workspace-root-regression.test.js` before removing or repointing `pnpm test`. - Focused assertions for the readiness wording and no-write fixture behavior remain in sibling task 03 as planned. - Focused behavioral regressions are completed by task 02 before milestone reconciliation. - Focused behavioral tests are intentionally handled by the next declared task, `02-cover-task-scoped-change-report`. - Focused build-output regression coverage is handled by `02-cover-summary-build-change-report-feed`. - Focused cache and trace regression coverage is completed by task 02 before milestone reconciliation. - Focused entry-point transition validation and production build remain assigned to task 02. - Focused fixture coverage for all detection sources remains for task 03. - Focused mutation-style negative cases are added by task 02. - Focused negative graph cases are delivered by task 02. - Focused negative-case coverage is delivered by task 02. - Focused prohibited-claim regression coverage is intentionally owned by the next declared task. - Focused regression assertions remain in sibling task 03 as planned. - Focused regression coverage and the production build remain sequenced in task 02. - Focused rejection-path coverage is intentionally delivered by declared task 02. - Focused runtime fixtures are the declared responsibility of task 02. - Focused runtime tests for valid and invalid signed envelopes remain deferred because the website package does not currently have a test script. - Focused semantic, generated-output, and production-route regression coverage remains assigned to task 02. - Focused source-uniqueness and checkout-alignment regression coverage is intentionally owned by the next declared task. - Focused tests for category behavior are handled by `02-cover-path-category-classification`. - Follow-up for `02-implement-stale-cli-wording-corrections`: apply the four actionable wording corrections above and rerun focused stale-term searches on the changed files. - Follow-up for a later milestone: compare registry completeness directly against Commander registration to catch newly added command surfaces automatically. - Follow-up for later command-posture regression work: compare registry entries to the actual Commander tree and reserved surface contracts so future command additions cannot drift silently. - Follow-up for milestone `02-legacy-retirement-decisions`: confirm retained legacy helper dependencies before deleting `tests/cli/runtime-helpers.js`. - Follow-up for milestone `02-legacy-retirement-decisions`: delete only source-inventory legacy files whose removal does not break retained out-of-scope legacy files. - Follow-up for milestone `03-runner-alignment-and-follow-up`: retain runner behavior unless V2 execution evidence shows a concrete script gap. - Follow-up for task 02: render the structured `implementationSummaryCloseoutGuidance` entries in compact text, verbose text, reminder text, and JSON at the appropriate detail level. - Follow-up for task 02: route `.day-shift/workflows/README.md` and `.day-shift/workflows/01-start-here.md` to the new guide. - Follow-up for task 03: add focused assertions for structured closeout JSON categories, compact/verbose/reminder rendering, and no-write behavior so this rendering cannot regress silently. - Follow-up for task 03: add focused regression tests that assert the structured closeout categories and no-write boundary across output modes. - Follow-up for task 03: render the structured severity guidance in text output and add focused regression coverage. - Follow-up for task 03: render the structured state and selected-evidence guardrails in text output and add focused regression coverage. - Follow-up for task `02-audit-active-guidance-references`: classify remaining `pnpm test` and legacy runner references across active workflows, prompts, and test-infrastructure planning evidence. - Follow-up for task `02-record-follow-up-and-final-validation`: record final V2 validation and closeout-search evidence. - Follow-up for task `02-register-existing-command-surfaces`: populate the registry with existing command surfaces now that the producer helper exists. - Follow-up for task `02-validate-legacy-retirement`: run V2, CLI-focused V2, and retained legacy validation after deletion. - Follow-up for task `02-validate-migrated-v2-equivalence`: run current V2 validation and update the inventory's validation evidence section. - Follow-up for task `03-expose-command-capability-metadata`: expose registry-derived metadata through agent orientation after the registry is populated. - Follow-up for task `03-expose-command-capability-metadata`: use the populated registry as the source for agent command-surface output. - Follow-up handoff: milestone reconciliation is eligible after task 03 metadata sync and final task-summary review confirm all three summaries are completed and non-placeholder. - Follow-up in task `02-align-human-readable-boundary-text`: render the structured no-write evidence in shared human-readable output. - Follow-up in task `03-add-read-only-recommendation-guidance`: make deterministic recommendation guidance more explicit and command-specific. - Follow-up in task `03-add-read-only-recommendation-guidance`: refine deterministic recommendation guidance and exact next-command text. - Follow-up is owned by later declared tasks in this milestone: task 02 renders the shared recommendation data in text output, and task 03 broadens no-side-effect coverage around the recommendations. - Follow-up is owned by task 03, which adds explicit no-side-effect coverage around the rendered recommendations. - Follow-up outside this phase: retained legacy `tests/cli/cross-command-workspace-root-regression.test.js` still needs separate ownership if full legacy `pnpm test` must pass. - Follow-up phases must replace deferred diagnostics with real behavior while preserving non-silent failure, JSON contract stability, and explicit network approval. - Follow-up remains for later milestones: implement mechanically safe artifact mutation, atomic writes, persisted apply evidence, richer changed/skipped/conflict reporting, and rollback guidance. - Follow-up remains for milestone 03: refine changed/skipped/conflict reporting and operator rollback guidance in text and JSON. - Follow-up remains in the declared milestone sequence: task 02 adds source-spec discovery recommendations, and task 03 broadens rendering/no-side-effect coverage across the completed recommendation set. - Follow-up remains in the declared milestone sequence: task 03 broadens rendering/no-side-effect coverage over the full discovery recommendation set. - Follow-up resolution: `--active-artifact ` now supplies a narrow explicit handoff input for direct comparison against the selected command artifact. - Follow-up within this milestone: task 02 should render `/install` and `/license` from `docs-content.ts`. - Follow-up within this milestone: task 02 should render homepage sections from `apps/website/content/marketing-content.ts`. - Follow-up within this milestone: task 03 should render `/troubleshooting` and complete docs validation coverage. - Follow-up within this milestone: task 03 should render `/troubleshooting` and extend route-level docs validation. - Follow-up within this milestone: task 03 should render pricing, FAQ, purchase, and upgrade pages from the same content source. - Follow-up within this milestone: task 03 should render pricing, FAQ, purchase, and upgrade pages from the structured content source. - Follow-up work may add an explicit `--active-artifact` or context handoff input if the CLI should compare conversation-selected artifacts directly. - Follow-up work remains to decide whether to retire or repoint `pnpm test`; that should happen in an explicitly scoped runner-retirement phase. - Follow-up work: create or sharpen reference destinations before aggressive human workflow cleanup for HAG-06, HAG-11, HAG-12, HAG-15, HAG-19, and HAG-20. - Follow-up work: later cleanup tasks may evaluate HAG-02, HAG-05, HAG-07, HAG-08, HAG-09, HAG-10, HAG-13, HAG-14, HAG-16, HAG-17, and HAG-18, but only by applying the gates recorded in the boundary map. - Full installer-shim behavior still needs non-sandboxed platform verification after install and release packaging phases add real shim producers. - Full release asset existence, checksum, byte-size, manifest, and latest pointer consistency checks remain intentionally deferred to milestone 03. - Full-suite validation remains useful after later milestones because this task only ran build, typecheck, and the focused command-surface test file during milestone 01. - Full-suite validation still has the previously observed unrelated non-root workspace regression failure from milestone 01. - Future phase or milestone reviews can decide whether similar concise entrypoint markers are needed in the phase and slice lifecycle guides; this milestone sharpened the task and milestone lifecycle routes used by the. - Future phases should preserve the reason-code taxonomy when adding selector precedence and install-produced metadata. - Future release artifact sync may need to create or restore local `release/0.1.10/` evidence if `0.1.10` is intended to be the active release-handoff baseline. - Future validation command entries that are present only in source posture registries remain unsupported until exposed through user-callable help. - Generalized mutation receipts, renewable leases, and repository-wide atomic write adoption remain outside this phase; this command family reports focused revision/write/no-op evidence only. - Generated and packaged duplicate trees were sampled rather than exhaustively enumerated; source and manifest evidence remain the semantic authority. - Generated and packaged duplicate trees were sampled, not exhaustively enumerated. - Generated output evidence is classified from parsed status paths while normalized scoped changed paths continue to use the existing write-destination safety boundary. - Guidance wording and no-write recovery options are refined in task `02-report-lightweight-promotion-guidance`. - HAG-01, HAG-03, and HAG-04 should remain in human workflow surfaces because they are human collaboration, chat handoff, or read-order routing responsibilities. - Help wording may need minor adjustment after the final data model and text renderer are implemented. - Helper deletion remains deferred to milestone 04. - Helper/fixture deletion remains blocked until milestone 08 resolves retained legacy tests. - Historical `.day-shift/planning/` artifacts remain on supported legacy `overview.md` paths. - Historical `.day-shift/planning/` artifacts still use legacy `overview.md`; no migration was performed. - Historical heuristic warnings remain in the read-only review transcript but are accepted as non-blocking because current completed reconciliation evidence is sufficient. - Historical planning references remain intentionally broad and must be classified separately from active guidance. - Host-sensitive elapsed timing is intentionally advisory. - Hosted Vercel project linkage and application-root assignment. - Hosted Vercel state remains intentionally outside local regression coverage and requires authenticated deployment evidence. - Hosted preview URL inspection and promoted production deployment acceptance. - Human review still owns qualitative usefulness beyond the deterministic minimum of substantive body length, forbidden placeholder phrases, and onward links. - Implementation-summary review reports advisory warnings for task-definition artifact updates outside declared implementation target paths. - Include structural-pressure policy inside the validation/review reference material before reducing reconciliation workflow prose. - Investigate and repair the existing `runtime-planning-navigation.test.js` phase-review fixture drift that appears after recompiling `dist`. - Judgment-heavy closeout body evidence still requires scoped manual authoring after command-supported build/review evidence. - Keep retained legacy overview naming references where they are intentionally exercising backward compatibility; new V2 tests should resolve both `overview.md` and `*-overview.md` where the behavior under test is. - Later CRUD and validation-integration milestones should add command-level tests that consume this storage contract. - Later CRUD commands must be the first write-capable surface that creates or mutates the storage file. - Later CRUD work should reuse the same storage path and selector conventions when it adds write-capable disposition management. - Later apply command work must decide how to compute changed/skipped/conflict/unresolved path lanes from previews. - Later apply implementation should call `isTraceLinkDispositionRewriteEligible` before proposing migrated-link replacements. - Later boundary mapping should inspect `.day-shift/workflows/02-plan-from-spec.md`, `.day-shift/workflows/03-implement-from-task.md`, and `.day-shift/workflows/04-summarize-and-reconcile.md` for mixed human procedure,. - Later cleanup tasks may evaluate HAG-02, HAG-05, HAG-07, HAG-08, HAG-09, HAG-10, HAG-13, HAG-14, HAG-16, HAG-17, and HAG-18, but only by applying the recorded cleanup readiness gates. - Later command-posture regression work should compare registry entries directly against the Commander command tree and reserved surface contracts so future command additions cannot drift silently. - Later commerce and license-delivery phases still need to implement the actual server route handlers behind this policy. - Later delivery/recovery milestones must provide private persistence and customer-facing download/recovery routes. - Later documentation work should create or sharpen reference destinations for command-family boundaries, prompt layer/action matrix ownership, planning hierarchy/decomposition rules, structural-pressure. - Later documentation work should create or sharpen stable reference destinations before aggressive human workflow cleanup for HAG-06, HAG-11, HAG-12, HAG-15, HAG-19, and HAG-20 in `human-agent-boundary-map.md`. - Later helper/fixture cleanup must decide whether to move or retain `tests/fixtures` after remaining legacy imports are gone. - Later milestone follow-up: add registry-to-Commander completeness checks and posture drift regression tests. - Later milestone tasks must replace the minimal placeholder orientation payload with the full shared data model and final text rendering. - Later milestones must extend validation again when webhook verification, license issuance, delivery, and recovery routes are implemented. - Later milestones must extend validation for public license delivery and recovery routes when those are implemented. - Later milestones must keep schemas, generated types, and validators aligned with this envelope order and feature-manifest shape. - Later milestones must prove each public consumer actually calls the shared decision and must perform production leakage verification. - Later milestones must replace deferred command-contract output with real local state inspection, shim dispatch, and runtime diagnostics without changing the manager-owned `day-shift version ...` boundary established. - Later milestones must update their own task evidence if implementation discovers additional retained V1 consumers. - Later milestones must update this classification if implementation discovers a retained surface has already been fully migrated or is still consumed unexpectedly. - Later milestones must validate that deleted V1 files have equivalent V2 coverage or explicit retirement rationale before final closeout. - Later milestones own frontmatter schema enforcement and the complete initial information architecture. - Later milestones should add storage-specific parse and no-partial-write tests once the storage file contract exists. - Later milestones still need to add generated/planning/source category classification and implementation-summary closeout consumption. - Later milestones still own final compact text rendering and reminder-specific payload selection. - Later milestones that add repository context gathering, final orientation data, or reminder rendering must keep this no-write test passing and extend JSON alias no-write coverage if alias-specific data. - Later phase or milestone reviews can decide whether similar concise entrypoint markers are needed in the phase and slice lifecycle guides; this task intentionally sharpened only the task and milestone. - Later phases still need to implement actual commerce, webhook, license delivery, recovery, and authenticated support route handlers behind this policy. - Later publication filtering should consume these enums rather than creating a second metadata vocabulary. - Later reminder-rendering work must replace the current shared placeholder data selection with correction-focused reminder content without introducing a divergent command implementation. - Later rendering milestones should keep help text compact and avoid duplicating the full orientation prose in help output. - Later route and server-boundary milestones will extend this validation script for route inventory and static/server policy checks. - Later selector/install phases may change the producer of `selected-version.json`; that should be handled as an intentional compatibility update to the read contract. - Later storage and CRUD tasks must reuse these helpers instead of accepting raw target strings directly. - Later tasks in this milestone still need to tighten default-format assertions, compactness boundaries, and the complete focused assertion set. - Later workflow cleanup can reduce duplicated detail only after verifying equivalent destination coverage in the new references, `.day-shift/agents.md`, lifecycle guides, prompts, templates, or manifests. - Later workflow cleanup phases can now rely on these canonical reference homes, but this task intentionally did not remove or shorten procedural workflow detail. - Later workflow cleanup should still verify destination coverage before shortening or deleting existing procedural text. - Later write-capable commands should parse the current file completely before deciding whether any write can proceed. - Legacy `tests/cli/runtime-helpers.js` must remain while retained legacy importers exist. - Legacy planning creation tests intentionally remain in place pending a later explicit retirement decision. - Legacy planning creation tests remain available pending a later explicit retirement decision. - Legacy planning update tests intentionally remain in place pending a later explicit retirement decision. - Legacy planning update tests remain available pending a later explicit retirement decision. - Legacy runner retirement remains blocked by `tests/cli/cross-command-workspace-root-regression.test.js` at line 42 (`false !== true`). - Legacy runner retirement remains blocked by the retained workspace-root regression in `tests/cli/cross-command-workspace-root-regression.test.js`. - Legacy spec command tests intentionally remain in place pending a later explicit retirement decision. - Legacy spec command tests remain available pending a later explicit retirement decision. - Live Vercel event receipt and dashboard-side internal-production-traffic filtering were not available from the repository. - Live Vercel event receipt and dashboard-side internal-production-traffic filtering were unavailable from the repository. - Live Vercel receipt, consent behavior supplied by the provider/browser, and dashboard-side internal traffic filtering need production operational review. - Live provider receipt and dashboard-side internal-production-traffic filtering remain the accepted operational residual. - Live provider receipt, exported mobile/desktop p75 samples, and provider-side internal-production-traffic filtering were unavailable from the repository. - Manual browser and assistive-technology review remains necessary; source and type validation do not establish full interaction accessibility. - Manual exception boundaries remain pending for task `02-record-manual-exception-boundaries`. - Manual interaction/accessibility review remains accepted residual phase validation. - Manual narrow/wide viewport, keyboard, and assistive-technology review remains phase validation evidence; structural source tests do not establish full WCAG behavior. - Milestone 02 must add deterministic cursor pagination; milestone 03 must enforce byte budgets and bound nested/prose lanes. - Milestone 02 must add selector-impact coverage for selected targets; milestone 03 must add license-resolution coverage beyond the preservation smoke checks in this milestone. - Milestone 02 must test the qualification implications against one implemented workflow and preserve explicit missing stages. - Milestone 03 must add full fail-closed consistency validation for missing files, checksum drift, byte-size mismatch, latest pointer mismatch, and release-note visibility. - Milestone 03 must generate TypeScript from these exact schema files and validate emitted runtime envelopes without introducing a second handwritten authority. - Milestone 03 still owns mixed licensed/unlicensed release-line coverage. - Milestone 05 must repoint `pnpm test` and remove or retire `scripts/run-node-test-files.js`. - Milestone 05 must repoint `pnpm test` because the legacy runner can no longer run without `tests/`. - Milestone 08 owns the final runner-retirement evidence and decision. - Milestone 2 must consume the verified upgrade intent before creating Stripe checkout and discount material. - Milestone 2 must repair spec 15 linked-slice registry evidence and synchronize spec 20 lifecycle metadata before closeout eligibility is reviewed. - Milestone 3 must archive only specs 15 and 20 in this cycle; specs 16, 17, and 21 must remain active. - Milestone 3 must decide whether this accepted legacy-path advisory is compatible with archival; no archive command ran in this task. - Milestone 3 must make independent closeout decisions and keep specs 92, 94, and 103 active. - Milestone `02-legacy-retirement-decisions`: make deletion decisions using `coverage-inventory.md`, and do not delete `tests/cli/runtime-helpers.js` unless retained legacy imports are removed or the helper remains. - Milestone `04-runtime-target-alignment` owns target alignment and replacement-target deviation behavior. - Milestone reconciliation can now evaluate this completed task together with the earlier command inventory tasks. - Milestone reconciliation is now eligible because both declared task implementation summaries are completed and non-placeholder. - Milestone reconciliation remains intentionally pending until task 2 also has a completed, non-placeholder implementation summary. - Milestone reconciliation remains intentionally pending until the sibling task implementation summary is completed. - Missing referenced files are intentionally ignored in this milestone; milestone 03 owns explicit stale/missing exclusion reporting. - Mixed-posture families require subcommand-level guidance to avoid overstating read-only or write-capable behavior. - Mixed-posture families such as `release`, `workspace migrate`, `completion`, and `version` require subcommand-level guidance wording. - Named screen-reader and live external-validator evidence remain required before full milestone acceptance; no accessibility-conformance or platform-preview claim is made. - Native Windows execution was unavailable locally. - Native execution remains unverified for every published platform/architecture; no independent coding-assistant certification or adoption evidence exists. - Native-execution evidence is not available for every published macOS, Linux arm64, or Windows target; publication and layout checks remain the maximum supported claim. - No M3 residual risk identified. - No accepted residual remains for the narrow explicit handoff case. - No blocked work remains for this task. - No blocking residual risk. - No blocking risk or discovered work. - No discovered work outside the declared milestone scope. - No discovered work outside the milestone scope. - No follow-up for milestone `01-active-guidance-reference-alignment`. - No follow-up for milestone `02-package-script-and-runner-reference-check`. - No follow-up from this task. - No follow-up is required for task 1. - No follow-up is required for task 2. - No follow-up is required for this task. - No follow-up required for install command wiring. - No follow-up required for metadata and receipt writing. - No follow-up required for metadata validation. - No follow-up required for source resolution. - No follow-up required for target-scoped package writes. - No follow-up required for this task. - No follow-up task artifacts were created during this consistency pass. - No follow-up task artifacts were created. - No follow-up work discovered for completion, reconciliation, task planning, or metadata parent-link resolution. - No follow-up work discovered for scaffold command help or generation behavior. - No follow-up work discovered for this milestone. - No follow-up work discovered for this task. - No follow-up work discovered. - No follow-up work identified for this task. - No follow-up work identified. - No follow-up work is required for blocker rendering coverage. - No follow-up work is required for the compatibility wording corrected by this task. - No follow-up work is required for the stale CLI availability wording corrected by this task. - No follow-up work is required for this task. - No follow-up work is required from the focused validation pass. - No follow-up work remains inside this milestone. - No follow-up work was discovered for this milestone. - No follow-up work was discovered. - No generated command-docs workflow was discovered for this repository surface; task 3 records coverage through CLI help tests and focused README inspection instead. - No helper or fixture files were deleted because retained consumers remain. - No independent coding-assistant certification, endorsement, customer adoption, or third-party outcome evidence exists or is claimed. - No known residual risk. - No lifecycle drift remains in spec 20 planning inventory; milestone 3 may now evaluate its archival eligibility independently. - No live Stripe API call was made during validation; the implementation is covered by strict TypeScript and static validation because live secret-backed Stripe testing is outside this local task. - No live Stripe API call was performed locally because it requires production or test secrets and network interaction. - No machine-readable command inventory export was observed for family/subcommand/posture/selected-artifact/no-write metadata. - No migrated V2 closeout blocker remains. - No milestone 05 residual implementation work remains. - No milestone-02 regression gap remains. - No milestone-blocking residual risk. - No standalone generated command documentation harness was discovered, so generated-doc validation was not run. - No task-blocking residual risk. - No task-scoped blocker remains. - No unplanned work was discovered. - No-write tests cover workspace file mutation, not process-external side effects outside the isolated environment. - Non-blocking builder issue carried from task 01: `implementation-summary build` duplicated placeholder authoring guidance, which manual closeout replaced with concrete evidence. - Non-blocking discovered work: `implementation-summary build` duplicated authoring-guidance blocks in the scaffold summary. - Operational next step: after deployment, verify provider receipt and filtering, then populate a reviewed baseline only when each metric/device segment has at least 75 representative samples across 28 consecutive days. - Operators still need a live Stripe test-mode checkout with real test secrets before public launch; repository validation intentionally does not call Stripe. - Ordered task 02 must exercise success, failure, collision, cleanup, and portability behavior before the milestone can reconcile. - Original discovery: the CLI had no explicit argument or structured input for conversation-derived active artifact context. - PATH conflict reporting is first-pass local evidence and should be revisited when installer shims define the final expected shim path. - Partial selector and `latest-installed` expansion remain deferred to task 02. - Pending evidence: start and assess the 28-day window only after production deployment and qualifying representative samples exist. - Phase 2 should inspect `src/lib/evidence-freshness/decision-trace.ts` narrowly so its subsystem-specific trace is not mistaken for a general decision model. - Phase 2 should use a representative planning write command for the required end-to-end trace and preserve unavailable user-local state as `Not verifiable`. - Phase `06-command-surface-adoption-audit` remains declared later work. - Plan a later adoption pass if existing command-specific read-only findings should all emit the richer no-write evidence helper fields. - Planned reference paths are intentionally not created in this milestone; they remain future planning targets, not current links. - Planning update command migration remains deferred to milestone 03. - Platform-specific durability fallbacks are verified through injected Node error codes; native Windows filesystem execution remains a broader cross-platform CI concern, not a blocker for this portable primitive contract. - Preview and apply command milestones should add command-level tests around these helpers. - Preview rendering still needs to classify matched migrated references into proposed updates, already-updated artifacts, conflicts, and unresolved cases in milestone 02. - Preview-specific output shaping remains for milestone `02-migration-preview-output`. - Private beta/VIP license-operation details are intentionally omitted from public release notes; recipient-facing release guidance covers signed license installation and local status checks. - Production Astro output filtering remains owned by later phase milestones; this task validates generated inference outputs only. - Production Core Web Vitals remain pending until the declared representative sample window is available; no field verdict is claimed. - Prompt Markdown and artifact template Markdown files may need visible "prompt instruction" or "artifact template shape" markers for direct human browsing. - Prompt, workflow, and reference families currently receive one-visible-H1 validation but no required H2 ordering unless a concrete contract is added later. - Protocol pages must track future protocol-version changes through focused tests. - Provider-side receipt and internal-production-traffic filtering remain operational follow-up evidence. - Public consumers are not yet wired to the decision; that is intentionally assigned to later phase milestones. - Publication eligibility filtering remains intentionally deferred to phase 02. - Raw stale-term search output remains noisy by design; the correction task should not remove legitimate lifecycle/status wording merely because it matches broad terms. - Read-only consumers outside the five selected modules continue using `planning-document-utils.ts`; broad repository-wide consolidation belongs to spec 103 and was not claimed. - Real command adoption may choose workflow-specific baselines later; this milestone supplies and verifies the reusable local measurement and gate contract without enabling telemetry. - Real static-output validation remains the Node 22.12+ follow-up recorded above. - Reconcile the documentation migration inventory with the public route registry in its owning canonical documentation work. - Reconcile the documentation migration inventory with the public route registry in its owning documentation work. - Reference-lane ownership is still needed for command-family boundaries, prompt layer/action matrix ownership, planning hierarchy/decomposition rules, structural-pressure policy, review command semantics, and. - Registry-only entries remain intentional inventory evidence for non-callable capability metadata. - Registry-only entries remain visible as non-callable evidence: `slice review`, `validation diff-check`, `validation impact-analysis`, and `validation scope-guard`. - Regression assertions that lock the new guidance fields are handled by task `03-cover-lightweight-pressure-boundaries`. - Regression coverage validates source/evidence consistency; it does not independently certify marketing comprehension. - Regression fixture coverage is completed by the next declared task. - Regression tests for concrete lightweight fixture categories are deferred to task `03-cover-lightweight-pressure-boundaries`. - Release and reconciliation hotspots were not addressed by this bounded milestone. - Release, reconciliation, spec 94, and spec 103 remain outside scope. - Remaining `tests/cli/*.test.js` files are direct-library or script-specific retained tests owned by milestone `03-retained-lib-and-script-v2-migration`. - Remaining `tests/cli/*.test.js` files are owned by milestone 03. - Remaining `tests/cli` and helper/fixture cleanup is owned by later declared milestones. - Remaining later-owner candidates are already recorded in `init-lib-fixture-inventory.md` and milestone 05 reconciliation. - Remaining milestone work must update README documentation and ensure coverage evidence is recorded in later declared tasks before milestone reconciliation. - Remaining planning creation and planning update command migrations are deferred to milestones 02 and 03. - Remaining retained consumers are documented for milestone 08. - Remaining risk: command renderers that do not use shared finding or terminal boundary helpers may need later command-specific adoption. - Render and assert the expanded lightweight and emergent guidance across text and JSON outputs. - Render and assert the expanded planning-flow guidance across text and JSON outputs. - Rendering and focused contract assertions remain in sibling tasks 02 and 03 as planned. - Rendering and focused regression assertions remain in sibling tasks 02 and 03 as planned. - Rendering parity and dedicated missing-entrypoint no-write coverage remain intentionally deferred to sibling tasks 02 and 03 in this milestone. - Repair and recertify the runtime-evidence workflow wording before reconsidering specs 16 or 21. - Repair and recertify the spec 13 `execution_mode` fixture before reconsidering spec 17. - Repair or refresh the broad `tests/cli/metadata-update.test.js` planning/spec-registry compatibility fixtures so the whole metadata update test file can be used as clean validation evidence. - Repair the runtime-evidence workflow wording through the owning documentation/runtime-evidence workflow, then recertify specs 16 and 21. - Repository pin and config selector sources remain intentionally deferred to milestone 02. - Repository pin/config sources are intentionally deferred to milestone 02. - Repository pin/config sources remain deferred to milestone 02. - Repository-specific documentation additions and explicit runtime-eligible exceptions remain planned for milestone `02-repository-path-policy`. - Repository-wide helper consolidation remains owned by spec 103; schema-grade YAML remains owned by spec 94. - Representative field traffic and provider-side exclusion evidence remain pending operational evidence, not testable success claims. - Representative integration is complete for the template/manifest family and the shared helper surfaces. - Representative smoke coverage in milestone `03-representative-smoke-migration` should exercise `runCli` against a real command family before broader migrations rely on the helper. - Representative smoke coverage should validate that these helper APIs are ergonomic for a real migrated CLI family before broad command-family migrations begin. - Rerun `pnpm --filter @day-shift/website run validate` after the documentation inventory mismatch is resolved. - Residual review risk is limited to the shared test file already containing unrelated pre-existing edits for sibling milestone coverage; those edits were preserved. - Residual risk is limited to any other stale retained legacy expectations outside the commands executed here. - Residual risk is limited to future JSON data-section additions that may require extending the stable section assertions without converting them to full payload snapshots. - Residual risk is limited to future compact-text wording changes that may require adjusting the stable phrase assertions without widening them into full snapshots. - Residual risk is limited to future policy wording drift that remains semantically acceptable but outside the exact snippets asserted by the focused contract test. - Residual risk is limited to future routing changes that might require additional command-surface tests if new agent aliases are introduced. - Residual risk is limited to future wording drift; the focused guardrail test now covers the stable rule codes, required state categories, selected-evidence kinds, evidence-only boundaries, and compact line budget. - Residual risk is limited to future wording or asset discovery drift, covered by task 02's focused policy-pack contract test. - Residual risk is limited to output wording drift, covered by task 02's focused regression test. - Residual risk is limited to representative coverage. - Residual risk is limited to representative coverage: command families are sampled through stable supported invocations rather than every registered read-only command. - Residual risk is low: closeout responsibilities are now represented in structured JSON, rendered in all intended text surfaces, and covered by focused no-write regression tests. - Resolved in milestone scope: a clean-first run exposed that the existing information-architecture test unconditionally required `dist`. - Retained files requiring later owner decisions or migration: - Retained helper and fixture files remain shared until later cleanup milestones prove they are no longer imported. - Retained helpers and fixtures under `tests/cli/runtime-helpers.js`, `tests/helpers/*.js`, and `tests/fixtures/**` remain because current retained legacy and V2 tests still use them. - Retained legacy `tests/cli/cross-command-workspace-root-regression.test.js` currently fails under `pnpm test` independently of the retired source-inventory files. - Retained legacy `tests/cli/cross-command-workspace-root-regression.test.js` currently fails under `pnpm test` while asserting an init-derived non-root workspace created the expected slice overview. - Retained legacy `tests/cli/cross-command-workspace-root-regression.test.js` remains out-of-scope follow-up from milestone `02`; no V2 runner follow-up was discovered. - Retained legacy `tests/cli/cross-command-workspace-root-regression.test.js` remains separate retained-suite follow-up if full legacy `pnpm test` must pass before release. - Retained legacy cross-command workspace-root files remain runner-retirement blocker evidence until a later fix or explicit failing-V2 acceptance path is approved. - Retained legacy runner retirement remains blocked by `tests/cli/cross-command-workspace-root-regression.test.js`; see task 03. - Retained legacy workspace-root blocker evidence is accepted for this milestone and remains a runner-retirement blocker for later workspace/runtime cleanup. - Retained legacy workspace-root regression failure should be handled under separate ownership if full legacy `pnpm test` is required to pass before release. - Retained workflow responsibilities: HAG-01, HAG-03, and HAG-04 should remain in human workflow surfaces because they are human collaboration, chat handoff, or read-order routing content. - Reviewers should not interpret the one config test failure as a configuration behavior regression; it is an absolute-versus-relative formatting expectation and is explicitly preserved as discovered work. - Risk: `src/lib/validation/artifact-family.ts` and `tests/lib/artifact-family.test.js` were already untracked in the worktree, so review should account for their full-file introduction separately from this task's. - Risk: child parsing intentionally reads ordered backticked bullets from the relevant parent section only; prose-only child lists remain governed by existing readiness and validation behavior rather than this drift check. - Risk: several target files had broad pre-existing uncommitted changes before this task, so final review should evaluate task-specific hunks rather than treating all diff lines in those files as new task 1 work. - Route model validation is broadened in the next declared task to enforce coverage and server exception limits. - Route-level runtime tests for valid and invalid signed envelopes are not present because the website package currently has no test script; behavior is covered by strict TypeScript boundaries and launch validation in. - Run a named screen reader on representative routes and record environment/findings/disposition. - Runtime Delta readiness and closeout enforcement remains planned in milestone `02-runtime-delta-contract`; it is not a blocker for accepting this metadata milestone. - Runtime Delta section completeness and runtime/hybrid path evidence enforcement are follow-up scope for milestone `02-runtime-delta-contract`. - Runtime Delta section enforcement tests remain follow-up scope for milestone `02-runtime-delta-contract`. - Runtime Delta target alignment and deviation handling remain planned for milestone `04-runtime-target-alignment`. - Runtime population of the model is intentionally left to the later declared tasks in this milestone. - Schema-grade YAML interpretation and validation remain owned by spec 94. - Selected-artifact shape reporting is accepted for this milestone. - Selector discovery is intentionally bounded to global aliases and selectors visible from the current working directory. - Selector replacement and selected-target confirmation are not implemented here and remain milestone 02 work. - Selector-impact confirmation remains intentionally deferred to milestone 02; uninstall can currently remove a selected version after exact target validation. - Separate boundary-review files should not be forced into subprocess CLI migration if direct library placement is the correct contract. - Separate-boundary and direct-library candidates remain for milestone 06 or milestone 07 classification/migration work. - Separate-boundary/direct-library candidates are accepted residual work for later init/lib/helper/runner cleanup milestones, not blockers for subprocess-first CLI migration closure. - Several implementation and test files were already modified or untracked before this milestone run. - Shape-specific contract fields are deferred to task 02. - Shared helpers and fixtures remain intentionally retained until later cleanup proves no retained legacy or V2 tests require them. - Sibling tasks still need to wire generation, inference, and reporting call sites to this shared helper. - Some duplicated wording remains intentionally where prompts or workflows need local execution context; no follow-up task is required for that retained context. - Source assertions can detect copy and hierarchy drift but cannot establish visitor comprehension. - Source-link coverage is intentionally deferred to task 02. - Spec 103 remains the owner of the repository-wide duplication inventory and consolidation analysis; this milestone intentionally adds one seam without broad helper consolidation. - Spec 15 retains five advisory link/smoke findings because legacy child phases use `overview.md` while canonical resolution probes `phase-overview.md`. - Spec 94 and spec 103 remain independently active and unclaimed. - Spec 94 remains the owner of schema-grade YAML parsing and validation guarantees; this milestone intentionally parses only lightweight top-level scalar evidence. - Spec 94 schema-grade YAML guarantees and spec 103 repository-wide duplication inventory remain active and explicitly unclaimed. - Specs 16, 17, and 21 remain active until their focused test blockers are repaired and recertified. - Specs 22, 92, 94, and 103 remain active by ownership decision, not because of archive-command failure. - Storage location and parse failure behavior remain for milestone 2. - Structured offer values intentionally mirror visible pricing and must change with that source if pricing changes. - Structured validation exception: planned command `pnpm --filter @day-shift/docs build`; blocker Node `20.19.0` is below Astro's required `>=22.12.0`; substitute evidence is passing generation, metadata checking, all 6. - Structured validation exception: planned command `pnpm --filter @day-shift/docs build`; blocker Node `20.19.0` is below Astro's required `>=22.12.0`; substitute evidence is successful `docs:generate`, `docs:check`, and. - Submit deployed URLs to applicable live social-preview and structured-data validators and record results/dispositions. - Substantive content authoring and marketing migration remain deferred to their declared later scope. - Substantive documentation quality remains outside this structural milestone. - Task 01 discovered failing runtime smoke coverage from legacy fixture/test assumptions; task 03 resolved that work. - Task 02 adds focused funnel regression coverage. - Task 02 must exercise malformed and insufficient evidence, every threshold boundary, confidence-bound rejection, attribution, and deterministic repeatability from checked-in provider-free fixtures. - Task 02 must expose the store through descriptor-backed commands and fresh-only context. - Task 02 must implement the `/api/checkout/*` redirect boundary used by the new page links. - Task 02 must integrate the validator into both shared emitters and prove generated-file drift plus malformed-envelope rejection without creating recursive error emission. - Task 02 must keep sequencing tied to this current inventory rather than assuming migration or deletion has already happened. - Task 02 must make `verbose: true` select expanded text instead of the compact renderer. - Task 02 must make route/page coverage and uniqueness deterministic. - Task 02 must preserve the seven statuses unless a cited correction is recorded. - Task 02 must restrict automatic budgets to approved read surfaces and safely translate typed failures before the capability is advertised. - Task 02 must translate cursor exceptions into structured CLI errors and bind actual emitted command/projection scope before the capability is advertised. - Task 02 must update additive canonical fixtures and freeze adversarial cross-surface behavior. - Task 02 must use this authority in both success and error emitters and feature discovery. - Task 02 must validate race-sensitive and crash-sensitive behavior. - Task 02 must verify every declared adversarial lane and exact budget boundaries. - Task 02 must wire the pure projection boundary into JSON emission and prove default full-detail compatibility before the milestone can be accepted. - Task 02 owns executable byte, stale-source, invalid-input, and parity regressions. - Task 02 owns the active scope definition. - Task 02 owns the classification contract. - Task 02 owns the final disposition choice. - Task 02 should decide whether to add a gap-report alias or keep the documented split. - Task 02 should define which generated sections can become cleaner without implying completed reconciliation. - Task 02 still needs to add explicit workspace migration blocker routing; task 01 intentionally left that out of scope. - Task 02 still needs to freeze the new fields with adversarial fixtures. - Task 02 still needs to make the new shared fields visible in human-readable output and structured output contracts. - Task 02 still needs to refine command-map and canonical reference handoffs in the same guide after this flow update. - Task 02 still needs to verify text-facing disposition output and artifact-specific applied-migration suppression in its own closeout evidence. - Task 02 still owns descriptor resolution and terminal CLI serialization. - Task 03 discovered hard-coded generic `overview.md` validation in spec registry routing/traceability and task promotion; the compatibility fixes were completed in task scope because they blocked the declared regression. - Task 03 must add explicit test coverage for verbose option behavior and no-write boundaries. - Task 03 must add explicit tests for verbose primary/alias output, JSON independence, compact default preservation, and no-write behavior. - Task 03 must harden coverage for the exact closeout evidence model rather than relying only on existing broad agent command tests. - Task 03 must rerun or classify the known workspace-root retained-suite blocker before downstream migration proceeds. - Task 03 must turn the contract into source behavior and tests. - Task 03 must update validation so the new commerce entrypoint contract is enforced. - Task 03 must update website validation so the single allowed checkout route is enforced and all other route handlers remain forbidden during this milestone. - Task 03 owns final validator evidence for the route and helper. - Task 03 owns implementation and validation. - Task 03 owns source changes, tests, build, and focused validation. - Task 03 owns source/test implementation. - Task 03 owns the script surface. - Task 03 should cover both the current sufficient-closure behavior and clearer accepted-residual advisory wording in source-level tests. - Task 03 still needs fixture coverage for explicit root, config marker, agents marker, git marker, and cwd fallback cases. - Task 03 still needs representative integration across command families that emit findings through the shared contract. - Task 03 still needs to complete final rendering/coverage review across health and migration blockers. - Task 06 must compare completed task summaries before deleting retained legacy files. - Task 06 must compare remaining legacy assertions before deleting `tests/cli/prompt-edit.test.js`, `tests/cli/prompt-init.test.js`, `tests/cli/prompt-update.test.js`, `tests/cli/template-materialize.test.js`, or. - Task 06 must compare the remaining legacy assertions before deleting `tests/cli/agent-command-surface.test.js` or `tests/cli/config-runtime.test.js`. - Task 06 must compare the remaining legacy assertions before deleting `tests/cli/manifest-update.test.js`, `tests/cli/metadata-sync-inventory.test.js`, or `tests/cli/metadata-update.test.js`. - Task 1 validation discovered that milestone reconciliation rendering did not preserve authored Accepted Residual Work when the template still contained the legacy `None accepted yet.` literal. - Task 2 must add explicit validation for the new contract module and route-specific wording; task 1 only confirmed the existing foundation validator, typecheck, and build remain green. - Task 2 must integrate this validator into `pnpm --filter @day-shift/website validate` before milestone reconciliation. - Task 2 must route `agent remind` text to the reminder data and renderer. - Task 2 must stop if current registry evidence diverges from this ledger before either archive command. - Task 2 must wire route data to the newly published public release metadata. - Task 2 owns focused CLI regression coverage for the generated task scaffold behavior. - Task 2 owns focused CLI regression coverage for the new milestone scaffold behavior and metadata preservation. - Task 2 should avoid treating every repeated warning as removable duplication; the audit marks local procedural context that should remain inline. - Task 2 should implement declared-child drift checks rather than extending the task 1 review-message changes opportunistically. - Task 3 is broad and includes large additive test coverage; final targeted validation passed, but repository-wide `pnpm test` was not run because the task declared targeted command-posture/navigation validation. - Task 3 still needs to switch `agent remind --format json` from the full orientation payload to structured reminder data. - Task 3 still owns unsupported or wrong-family status-field rejection evidence. - Task 4 should add/confirm final alias assertions for no-write reminder JSON and milestone-level compactness/read-only guarantees. - Task `02-implement-human-workflow-audience-markers` should add human workflow markers that route to these new reference homes where broad responsibility detail is mentioned. - Task `03-add-layer-specific-overview-regressions` must update runtime smoke/reminder fixture expectations so regression coverage aligns with canonical layer-specific overview filenames. - Template workspace drift still relies on `templates list` for filesystem existence checks because `validateArtifactShape` intentionally receives only artifact path and content. - Tests prevent claim drift but cannot create missing native-execution, certification, or adoption proof. - Text rendering for the new root-context facts remains for task 02. - The CLI does not currently expose a machine-readable command inventory report that emits command family, subcommand, posture, selected-artifact arguments, and no-write boundary metadata in one JSON payload. - The V2 helper help-output fallback remains accepted helper behavior for migrated completion coverage. - The V2 runner is now the default; milestone 06 will provide final closeout evidence. - The V2 smoke intentionally covers a narrow license status path. - The accepted documentation-only planning warning is appropriate because the milestone's declared deliverable is this contract evidence record. - The accepted task-level deviations route the generated contract through the existing explicit public-contract allowlist and extend existing architecture/publication tests. - The actual fail-closed Stripe configuration reader and checkout creation route are intentionally owned by `02-create-discounted-upgrade-checkout-session`. - The aggregate website validation command is blocked before milestone-owned checks by a documentation migration inventory/public-route registry mismatch outside this milestone's changed paths. - The aggregate website validation command remains blocked at the documentation migration inventory/public-route registry mismatch identified during milestone 01. - The aggregate website validation command remains blocked at the documentation migration inventory/public-route registry mismatch identified in milestones 01 and 02. - The allowlist is intentionally explicit; newly added high-volume read commands require a deliberate allowlist and regression update before automatic compact budgeting applies. - The artifact-shape lane is selected-artifact scoped in smoke validation to avoid turning repository-wide historical placeholders into this task's repair scope. - The assessment inherits phase 01's dirty-tree and unavailable-user-state caveats. - The broad test wrapper behavior should be treated as discovered work for later test tooling cleanup if single-file wrapper execution is expected. - The broad test wrapper single-file argument behavior remains discovered work from task 01, but focused `node --test` validation is passing. - The broader `node --test tests/cli/runtime-planning-navigation.test.js` command fails after recompiling `dist` because an existing phase-review fixture reports missing or stale completed task summary evidence. - The broader persistent context model remains out of scope by design. - The broader runtime planning navigation test file has an unrelated phase-review fixture failure after recompiling `dist`; this should be addressed separately or accepted as pre-existing validation drift before using. - The broader runtime planning navigation test file remains affected by unrelated phase-review fixture drift after recompiling `dist`; focused task 02 warning coverage passes. - The broader runtime planning navigation test file remains affected by unrelated phase-review fixture drift after recompiling `dist`; focused task 03 stale-risk coverage passes. - The canonical walkthrough's singular illustrative task slug is stale relative to current CLI full-set expansion; public evidence explicitly discloses and follows the current two-task runtime contract. - The catalog is not accepted until task 02 compiles every reference and validates positive, negative, recursive, and union fixtures with Ajv 8. - The checked-in fixture is explicitly synthetic contract evidence and does not claim that any external model was called. - The classification inherits the frozen-revision, dirty-tree provenance, sampling, and unavailable external/user-local-state limitations recorded upstream. - The command intentionally requires Astro's supported Node 22.12+ runtime. - The command pins exact stable versions only. - The command-posture fixture failure continues to block spec 17. - The compact public fixture proves the rule engine and planning lifecycle, not a production browser-game UI or independent third-party outcome. - The complete page tree remains intentionally deferred to milestone 03. - The composer treats descriptor-declared selection preconditions directly and current relevant blockers as the state-aware transition gate. - The concurrent multi-file `node --test` invocation showed cross-file interference when `runtime-planning-navigation.test.js` ran alongside the broader Task 03 set, while the same file passed directly and the sequential. - The concurrent multi-file `node --test` invocation showed cross-file interference, so sequential per-file validation is the reliable evidence for this task. - The coordinator cannot close the optimistic time-of-check/time-of-use window without locking, and its rollback seam does not supply a default rollback strategy. - The coordinator remains optimistic rather than lock-protected, and rollback remains an opt-in callback seam. - The deleted legacy init/lib paths remain mentioned as historical deletion evidence in task summaries; planning smoke reports that as advisory missing-input evidence, not as a coverage blocker. - The detector is intentionally not wired into validation smoke yet; task 03 owns reporting integration. - The deterministic corpus intentionally does not establish provider-backed generalization or promotion thresholds; those remain milestone 03 responsibilities. - The disposition record intentionally allows neutral fixture retention when V2 or compatibility coverage still consumes fixture data. - The documentation migration inventory still does not exactly match the public route registry. - The exact selection argv remains explicitly marked `planned` until milestone 2 implements `work select`; candidate discovery itself remains advisory and non-writing. - The focused regression contract and environment-qualified success-path evidence are complete. - The full V2 runner currently executes all discovered V2 test files in one `node --test` invocation, while CLI-focused mode executes files sequentially. - The full `tests/cli/metadata-update.test.js` file currently includes unrelated planning/spec-registry workspace compatibility fixture failures. - The full runtime-planning-navigation test-file failure is accepted as residual validation drift for this milestone because focused warning coverage and TypeScript compilation pass, and the failure is unrelated to the. - The guard intentionally runs only when `linked_slice.*` fields are updated so unrelated spec metadata edits do not become broad planning validation. - The guard intentionally validates selected artifact path and explicit metadata, not conversational context. - The in-page workflow section is an intentionally lightweight evaluation destination until the later demonstration milestone supplies deeper, reproducible product proof. - The inherited parent-slug language warning is carried forward as non-blocking administrative evidence. - The inventory depends on observable Commander object properties; the logic is isolated behind one helper and covered by regression tests. - The inventory is a baseline rather than final phase-09 closure; task 02 adds drift enforcement so later page changes cannot silently bypass it. - The inventory is derived from compiled `dist/**`; repository contributors must build the CLI before docs generation when descriptor source changes. - The isolated config runtime suite has one stale assertion expecting an absolute provenance path; the current CLI returns canonical repository-relative `./.day-shift/config.toml`. - The known `tests/cli/cross-command-workspace-root-regression.test.js` retained failure remains runner-retirement blocker evidence; it was intentionally not claimed as passing V2 migration evidence. - The later `/downloads/[version]` route fix has now been captured in this evidence refresh; no additional URL-contract follow-up remains for the observed `/downloads/0.1.10` 404. - The later `/downloads/[version]` route fix has now been captured in this evidence refresh; the publication validation evidence remains read-only over release assets. - The live worktree still contains retained V1 files, fixtures, helpers, and the legacy default `pnpm test` runner. - The matrix inherits phase 01's frozen-commit, dirty-tree, generated-sampling, and unavailable-user-state caveats. - The matrix inherits the frozen baseline's pre-existing dirty-tree, generated/packaged sampling, and unavailable user-local/external-state caveats. - The milestone does not establish that current production Core Web Vitals are good; it establishes collection, thresholds, qualification rules, and deterministic pre-field budgets. - The model inherits the frozen revision's explicit dirty-tree and generated/release sampling caveats. - The model is bounded to the inspected commit plus explicitly caveated working-tree evidence. - The next milestone should add mutation regression tests for read-only command fixtures. - The one-second acquisition wait and two-minute stale threshold are local selection safeguards, not the generalized renewable lock/receipt system planned for the later repository-wide atomicity phase. - The only residual validation risk is scanning a real Astro build under Node 22.12+. - The parent-slug `define` heuristic warning remains administrative evidence; it does not affect the concrete task contract or runtime readiness result. - The per-file packaged authoring set is version-dependent; the guide intentionally documents stable families and directs readers to dry-run/manifest evidence instead of freezing a stale 73-file list. - The pre-existing dirty tree means working-tree-only citations require explicit provenance caveats. - The prompt manifest remains a dense reference surface, but this task intentionally avoided broader manifest cleanup to preserve scope and behavior. - The public fixture demonstrates executable game rules rather than a styled Next.js browser game; it is intentionally synthetic proof of lifecycle and state behavior, not a production application or customer result. - The regression pins vocabulary in the named guidance files, but future new prompt or workflow surfaces should be added to the same vocabulary test when they start rendering source-spec lifecycle guidance. - The repo test wrapper command `node scripts/run-node-test-files.js tests/cli/agent-command-surface.test.js` appears to ignore the single-file argument and ran broader tests; that surfaced an unrelated release-notes. - The report retains upstream frozen-revision, dirty-tree provenance, sampling, and unavailable-state caveats. - The residual sampling and dirty-state caveats are accepted for this baseline because they are explicit and do not prevent later targeted inspection. - The resolver is typechecked but not yet reachable from the CLI. - The retained legacy CLI files are separately owned or blocked and should be handled by a dedicated follow-up before runner retirement. - The retained legacy runner still fails on `tests/cli/cross-command-workspace-root-regression.test.js`; this is the same known workspace-root blocker recorded by milestones 04 and 05. - The retained workspace-root failure is accepted as residual retained-suite evidence for this inventory milestone. - The retained workspace-root files remain runner-retirement blocker evidence for later workspace/runtime cleanup. - The sandbox blocks nested process spawning in some cases, so `.js` managed bins have an in-process fallback after `EPERM`. - The schema retains the two legacy action variants for protocol-v1 compatibility. - The selected workflow represents repository-local planning mutation, not all commands or external effects. - The selection argv is intentionally marked `planned` until milestone 2 implements the write-capable selection command. - The sequence intentionally defers metadata status updates until phase review or explicit metadata authorization. - The task-01 readiness heuristic warned that contract analysis is documentation-only while the milestone concerns executable behavior. - The template manifest remains a dense reference surface, but this task intentionally avoided broader manifest cleanup to preserve scope and behavior. - The template-contract wording failure continues to block specs 16 and 21. - The template-family check is intentionally narrow: it rejects prompt-only front matter fields on template Markdown but does not introduce a broad template Markdown schema beyond existing front matter and. - The test protects operational contract claims but intentionally does not exercise disposable customized or stale workspaces; those procedures remain milestone 03/04 scope. - The tests intentionally consume compiled descriptor output; CLI source changes require a fresh repository build before this evidence is authoritative. - The three focused test blockers remain discovered work and keep specs 16, 17, and 21 active. - The trace cannot verify unavailable operator reasoning, external state, or general outcome reproduction. - The unrelated documentation inventory/public-route mismatch remains the only aggregate-suite blocker and should be resolved in its owning documentation work. - The upgrade form posts to `/api/upgrade/eligibility`, but the endpoint is intentionally implemented by `02-implement-server-side-license-verification`. - The validator checks source contracts; the Next.js build supplies complementary framework integration evidence. - The working tree was dirty before inspection, so later analysis must preserve source-specific dirty-state caveats. - The workspace/runtime migration batch must decide whether to fix this `init --directory` behavior, preserve it as failing retained evidence, or split it into equivalent V2 regression coverage before legacy. - The write path intentionally reports the selected-artifact gate but defers actual mutation until the source-location and rewrite-engine milestones complete. - These evidence-boundary caveats are accepted because the model records them explicitly and does not infer missing contents or reproducibility. - These references are intentionally compact and do not replace full workflow, prompt, template, manifest, or lifecycle guide contracts. - This task covers registry and shared-helper behavior. - This task intentionally added markers without removing existing duplicated procedural detail, so some duplication remains until a later cleanup task. - Threshold calibration remains explicitly owned by the later evaluation phase. - Trust-lane/adversarial coverage and unified authorization/redaction/sanitization remain declared work in milestones 02 and 03. - Unavailable named assistive-technology and external-validator access prevents full acceptance without overstating local evidence. - Unrelated dirty workspace changes were observed outside this task's owned paths and were not reverted. - Until task 02 renders the structured entries, compact text still primarily exposes the legacy closeout list plus the new no-write boundary. - Verify spec-index and parent-planning traceability and path existence. - Verify whether each intended destination already contains equivalent guidance and record partial or missing coverage as cleanup blockers. - Website download metadata includes `0.1.10`, but no matching local `release/0.1.10/` directory exists in this checkout for release-handoff comparison. - Website download metadata includes newer `0.1.10` files, but no matching local `release/0.1.10/` directory was present for release-handoff comparison in this checkout. - Workflow cleanup remains backlog work outside this milestone. - Write commands increment revisions but do not yet accept or enforce caller preconditions. - Write-oriented `front-matter-utils.ts` remains intentionally separate and unchanged. - `.day-shift/agents.md` still describes an evolving CLI implementation, so future CLI surface additions should keep the installed-command versus repo-development-entrypoint distinction current. - `.day-shift/local.toml` and `.day-shift/config.toml` default selectors remain deferred to task 02. - `.day-shift/prompts/user/manifest.json` also participates in task 1's prompt-guidance scope; this overlap is intentional because the prompt manifest carries both prompt-family and manifest-family guidance. - `.day-shift/prompts/user/manifest.json` and `.day-shift/templates/manifest.json` contain command-contract and family-boundary reference notes that should remain distinct from onboarding procedure. - `.day-shift/workflows/04-summarize-and-reconcile.md` includes structural-pressure and review-command policy that may deserve a reference lane if human workflow readability suffers. - `/tmp` contains a `.git` marker in this execution environment, so the cwd fallback fixture runs from `/` instead of a temp workspace. - `03-pin-command-write` was added after initial milestone reconciliation because phase acceptance requires repository pin writes, not only pin reads. - `04-adopt-command-inventory-guidance-surfaces` - `dist` artifacts are generated but not tracked in this worktree status; runtime tests were rerun after `tsc` emitted updated local `dist` files. - `docs.tnsds.tech` DNS and Vercel domain assignment. - `implementation-summary build` duplicates authoring-guidance blocks in scaffold summaries. - `pnpm --filter @day-shift/website validate` is wired but intentionally completed by the next declared task, which creates `apps/website/scripts/validate-foundation.mjs`. - `pnpm test` and `scripts/run-node-test-files.js` remain intentionally retained legacy surfaces. - `pnpm test` and `scripts/run-node-test-files.js` remain retained legacy surfaces until milestone 08 resolves the known retained failure. - `scripts/run-node-test-files.js` and `package.json` `test` remain stale until milestone `05-v2-default-runner-repoint`. - `scripts/run-node-test-files.js` is broken until milestone 05 repoints or removes the legacy runner. - `tests/cli/cross-command-workspace-root-regression.test.js` remains an accepted blocker because it fails the `init --directory` non-root planning-generation subtest at line 42 with `false !== true`. - `tests/cli/cross-command-workspace-root-regression.test.js` still fails in the `init --directory produces a non-root workspace that supports planning generation validation smoke and reconciliation build` subtest. - `tests/cli/cross-command-workspace-root-regression.test.js`: retained workspace-root blocker. - `tests/cli/cross-command-workspace-root-reporting.test.js`: retained workspace-root reporting coverage tied to blocker lane. - `tests/cli/metadata-update.test.js`: retained pending spec-registry mutation assertion comparison. - `tests/cli/planning-overview-policy.test.js`: separate planning/lib boundary review. - `tests/cli/release-notes-source.test.js`: separate release/lib boundary review. - `tests/cli/release-version-parser.test.js`: direct parser/library candidate. - `tests/cli/runtime-helpers.js` remains because retained legacy files still import it. - `tests/cli/runtime-helpers.js` remains for milestone 04 cleanup. - `tests/cli/runtime-helpers.js` remains for milestone `04-fixture-helper-and-tests-tree-cleanup`. - `tests/cli/runtime-helpers.js` remains present for milestone `04-fixture-helper-and-tests-tree-cleanup`; deletion is intentionally out of scope for milestone 02. - `tests/cli/validation-runtime.test.js`: retained pending explicit comparison against existing V2 validation runtime coverage. - `tests/cli/version-install-source-validation.test.js`: direct validation/library candidate. - `tests/cli/version-state-layout.test.js`: direct state-layout/library candidate. - `tests_v2/cli/license/cross-layer-regressions.test.js` cannot initialize its sandbox because the expected runtime-evidence policy-pack asset is missing after `init`; ownership is init/policy-pack copying and license. - `tests_v2/cli/runtime/command-posture-regression.test.js` exposes a spec 13 fixture task missing `execution_mode`; this blocks spec 17's current command-posture gate. - `tests_v2/cli/runtime/command-posture-regression.test.js` retains the phase-01-known failure because a spec-13 fixture task definition lacks `execution_mode`; ownership remains that planning fixture. - `tests_v2/init/template-contract.test.js` exposes missing exact runtime-evidence wording in `.day-shift/workflows/task.agent-lifecycle-guide.md`; this blocks specs 16 and 21 from archival. ## Source Trace - .day-shift/planning/12-website/phases/01-nextjs-site-foundation/milestones/01-workspace-and-build-contract - .day-shift/planning/12-website/phases/01-nextjs-site-foundation/milestones/02-route-and-rendering-model - .day-shift/planning/12-website/phases/01-nextjs-site-foundation/milestones/03-shared-content-and-server-boundary-policy - .day-shift/planning/12-website/phases/02-downloads-and-release-publication/milestones/01-download-url-contract - .day-shift/planning/12-website/phases/02-downloads-and-release-publication/milestones/02-release-asset-consumption - .day-shift/planning/12-website/phases/02-downloads-and-release-publication/milestones/03-publication-consistency-validation - .day-shift/planning/12-website/phases/03-public-content-and-positioning/milestones/01-marketing-and-product-positioning - .day-shift/planning/12-website/phases/03-public-content-and-positioning/milestones/02-install-license-and-troubleshooting-docs - .day-shift/planning/12-website/phases/03-public-content-and-positioning/milestones/03-support-privacy-and-limitation-pages - .day-shift/planning/12-website/phases/04-commerce-and-license-delivery/milestones/01-checkout-and-upgrade-entrypoints - .day-shift/planning/12-website/phases/04-commerce-and-license-delivery/milestones/02-webhook-and-license-issuance-boundary - .day-shift/planning/12-website/phases/04-commerce-and-license-delivery/milestones/03-license-delivery-and-recovery-flow - .day-shift/planning/12-website/phases/05-visual-system-and-route-experience/milestones/01-design-tokens-and-shell-components - .day-shift/planning/12-website/phases/05-visual-system-and-route-experience/milestones/02-download-install-and-license-surfaces - .day-shift/planning/12-website/phases/05-visual-system-and-route-experience/milestones/03-commerce-and-content-route-polish - .day-shift/planning/12-website/phases/06-publication-validation-and-launch-readiness/milestones/01-route-content-and-build-validation - .day-shift/planning/12-website/phases/06-publication-validation-and-launch-readiness/milestones/02-release-commerce-and-secret-boundary-validation - .day-shift/planning/12-website/phases/06-publication-validation-and-launch-readiness/milestones/03-launch-readiness-and-handoff - .day-shift/planning/12-website/phases/07-automated-upgrade-discount-checkout/milestones/01-license-submission-and-verification - .day-shift/planning/12-website/phases/07-automated-upgrade-discount-checkout/milestones/02-server-created-stripe-upgrade-checkout - .day-shift/planning/12-website/phases/07-automated-upgrade-discount-checkout/milestones/03-upgrade-flow-validation-and-handoff - .day-shift/planning/13-test-infrastructure/phases/01-v2-harness-baseline/milestones/01-tests-v2-structure-and-scripts - .day-shift/planning/13-test-infrastructure/phases/01-v2-harness-baseline/milestones/02-subprocess-helper-contract - .day-shift/planning/13-test-infrastructure/phases/01-v2-harness-baseline/milestones/03-representative-smoke-migration - .day-shift/planning/13-test-infrastructure/phases/02-spec-and-planning-command-migrations/milestones/01-spec-registry-command-migration - .day-shift/planning/13-test-infrastructure/phases/02-spec-and-planning-command-migrations/milestones/02-planning-creation-command-migration - .day-shift/planning/13-test-infrastructure/phases/02-spec-and-planning-command-migrations/milestones/03-planning-update-command-migration - .day-shift/planning/13-test-infrastructure/phases/03-paired-artifact-template-and-completion-migrations/milestones/01-implementation-summary-command-migration - .day-shift/planning/13-test-infrastructure/phases/03-paired-artifact-template-and-completion-migrations/milestones/02-reconciliation-command-migration - .day-shift/planning/13-test-infrastructure/phases/03-paired-artifact-template-and-completion-migrations/milestones/03-template-completion-and-runtime-validation-migration - .day-shift/planning/13-test-infrastructure/phases/04-legacy-retirement-and-runner-alignment/milestones/01-equivalent-coverage-review - .day-shift/planning/13-test-infrastructure/phases/04-legacy-retirement-and-runner-alignment/milestones/02-legacy-retirement-decisions - .day-shift/planning/13-test-infrastructure/phases/04-legacy-retirement-and-runner-alignment/milestones/03-runner-alignment-and-follow-up - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/01-active-guidance-reference-alignment - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/02-package-script-and-runner-reference-check - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/03-final-v2-closeout-evidence - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/04-retained-cli-family-inventory-and-sequencing - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/05-retained-cli-subprocess-migration - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/06-init-and-lib-v2-migration - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/07-v1-helper-fixture-and-runner-cleanup - .day-shift/planning/13-test-infrastructure/phases/05-v2-build-test-reference-alignment/milestones/08-final-v1-retirement-evidence - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/01-reviewer-accepted-residual-semantics - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/02-planning-command-option-aliases - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/03-reconciliation-build-evidence-quality - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/04-retired-file-validation-classification - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/05-active-reference-audit-surface - .day-shift/planning/13-test-infrastructure/phases/06-post-migration-lifecycle-and-validation-polish/milestones/06-retained-workspace-root-blocker - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/01-final-retained-v1-disposition - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/02-retained-cli-runtime-v2-migration - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/03-retained-lib-and-script-v2-migration - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/04-fixture-helper-and-tests-tree-cleanup - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/05-v2-default-runner-repoint - .day-shift/planning/13-test-infrastructure/phases/07-final-v1-disposal-and-v2-default-validation/milestones/06-final-v2-default-closeout-evidence - .day-shift/planning/15-agent-guidance-command-contract/phases/01-command-surface-and-output-contract/milestones/01-register-agent-command-family - .day-shift/planning/15-agent-guidance-command-contract/phases/01-command-surface-and-output-contract/milestones/02-define-orientation-data-model - .day-shift/planning/15-agent-guidance-command-contract/phases/01-command-surface-and-output-contract/milestones/03-render-default-text-orientation - .day-shift/planning/15-agent-guidance-command-contract/phases/01-command-surface-and-output-contract/milestones/04-render-reminder-alias - .day-shift/planning/15-agent-guidance-command-contract/phases/02-repository-orientation-context/milestones/01-report-effective-root-context - .day-shift/planning/15-agent-guidance-command-contract/phases/02-repository-orientation-context/milestones/02-report-agent-entrypoint-status - .day-shift/planning/15-agent-guidance-command-contract/phases/02-repository-orientation-context/milestones/03-recommend-health-and-runtime-discovery - .day-shift/planning/15-agent-guidance-command-contract/phases/02-repository-orientation-context/milestones/04-recommend-planning-and-spec-discovery - .day-shift/planning/15-agent-guidance-command-contract/phases/02-repository-orientation-context/milestones/05-agent-verbose-output-mode - .day-shift/planning/15-agent-guidance-command-contract/phases/03-workflow-rules-and-command-boundaries/milestones/01-encode-planning-flow-rules - .day-shift/planning/15-agent-guidance-command-contract/phases/03-workflow-rules-and-command-boundaries/milestones/02-classify-command-surfaces - .day-shift/planning/15-agent-guidance-command-contract/phases/03-workflow-rules-and-command-boundaries/milestones/03-encode-finding-and-state-guardrails - .day-shift/planning/15-agent-guidance-command-contract/phases/03-workflow-rules-and-command-boundaries/milestones/04-encode-migration-and-health-blockers - .day-shift/planning/15-agent-guidance-command-contract/phases/04-closeout-and-memory-guidance/milestones/01-define-implementation-summary-closeout - .day-shift/planning/15-agent-guidance-command-contract/phases/04-closeout-and-memory-guidance/milestones/02-define-reconciliation-readiness - .day-shift/planning/15-agent-guidance-command-contract/phases/04-closeout-and-memory-guidance/milestones/03-define-review-and-validation-evidence-boundaries - .day-shift/planning/15-agent-guidance-command-contract/phases/04-closeout-and-memory-guidance/milestones/04-define-repository-memory-checkpoint-boundary - .day-shift/planning/15-agent-guidance-command-contract/phases/05-validation-docs-and-regression-coverage/milestones/01-test-command-aliases-and-output-modes - .day-shift/planning/15-agent-guidance-command-contract/phases/05-validation-docs-and-regression-coverage/milestones/02-test-root-entrypoint-and-discovery-context - .day-shift/planning/15-agent-guidance-command-contract/phases/05-validation-docs-and-regression-coverage/milestones/03-test-workflow-boundaries-and-guardrails - .day-shift/planning/15-agent-guidance-command-contract/phases/05-validation-docs-and-regression-coverage/milestones/04-test-no-write-regression-contract - .day-shift/planning/15-agent-guidance-command-contract/phases/05-validation-docs-and-regression-coverage/milestones/05-update-agent-command-documentation - .day-shift/planning/16-onboarding-experience-redesign/phases/01-audience-and-responsibility-separation/milestones/01-audience-marker-inventory - .day-shift/planning/16-onboarding-experience-redesign/phases/01-audience-and-responsibility-separation/milestones/02-human-agent-boundary-mapping - .day-shift/planning/16-onboarding-experience-redesign/phases/01-audience-and-responsibility-separation/milestones/03-prompt-template-reference-boundaries - .day-shift/planning/16-onboarding-experience-redesign/phases/01-audience-and-responsibility-separation/milestones/04-reference-and-marker-materialization - .day-shift/planning/16-onboarding-experience-redesign/phases/02-reference-and-layer-relationship-docs/milestones/01-command-registry-and-metadata-reference - .day-shift/planning/16-onboarding-experience-redesign/phases/02-reference-and-layer-relationship-docs/milestones/02-prompt-template-validation-reference - .day-shift/planning/16-onboarding-experience-redesign/phases/02-reference-and-layer-relationship-docs/milestones/03-planning-layer-relationship-reference - .day-shift/planning/16-onboarding-experience-redesign/phases/03-human-onboarding-entrypoints/milestones/01-human-workflow-routing - .day-shift/planning/16-onboarding-experience-redesign/phases/03-human-onboarding-entrypoints/milestones/02-first-project-guide-refinement - .day-shift/planning/16-onboarding-experience-redesign/phases/03-human-onboarding-entrypoints/milestones/03-existing-repository-onboarding - .day-shift/planning/16-onboarding-experience-redesign/phases/04-evidence-navigation-and-workflow-handoffs/milestones/01-workflow-input-output-handoffs - .day-shift/planning/16-onboarding-experience-redesign/phases/04-evidence-navigation-and-workflow-handoffs/milestones/02-evidence-source-navigation - .day-shift/planning/16-onboarding-experience-redesign/phases/04-evidence-navigation-and-workflow-handoffs/milestones/03-read-only-discovery-command-guidance - .day-shift/planning/16-onboarding-experience-redesign/phases/05-doc-hygiene-validation-and-migration/milestones/01-stale-cli-wording-cleanup - .day-shift/planning/16-onboarding-experience-redesign/phases/05-doc-hygiene-validation-and-migration/milestones/02-duplication-and-canonical-link-cleanup - .day-shift/planning/16-onboarding-experience-redesign/phases/05-doc-hygiene-validation-and-migration/milestones/03-compatibility-and-validation-pass - .day-shift/planning/17-programmatic-workflow-enforcement/phases/01-command-capability-and-no-write-boundaries/milestones/01-command-capability-registry - .day-shift/planning/17-programmatic-workflow-enforcement/phases/01-command-capability-and-no-write-boundaries/milestones/02-read-only-boundary-reporting - .day-shift/planning/17-programmatic-workflow-enforcement/phases/01-command-capability-and-no-write-boundaries/milestones/03-command-posture-regression-tests - .day-shift/planning/17-programmatic-workflow-enforcement/phases/02-lifecycle-and-scaffold-gates/milestones/01-source-spec-and-planning-advancement-gates - .day-shift/planning/17-programmatic-workflow-enforcement/phases/02-lifecycle-and-scaffold-gates/milestones/02-create-revise-and-selected-artifact-boundaries - .day-shift/planning/17-programmatic-workflow-enforcement/phases/02-lifecycle-and-scaffold-gates/milestones/03-linked-slice-parent-traceability-and-conflicts - .day-shift/planning/17-programmatic-workflow-enforcement/phases/03-artifact-shape-and-family-validation/milestones/01-artifact-family-parser-and-shape-rules - .day-shift/planning/17-programmatic-workflow-enforcement/phases/03-artifact-shape-and-family-validation/milestones/02-prompt-template-manifest-and-scaffold-lanes - .day-shift/planning/17-programmatic-workflow-enforcement/phases/03-artifact-shape-and-family-validation/milestones/03-trace-link-and-file-scoped-validation - .day-shift/planning/17-programmatic-workflow-enforcement/phases/04-closeout-and-reconciliation-evidence/milestones/01-implementation-summary-evidence-review - .day-shift/planning/17-programmatic-workflow-enforcement/phases/04-closeout-and-reconciliation-evidence/milestones/02-lifecycle-status-coherence - .day-shift/planning/17-programmatic-workflow-enforcement/phases/04-closeout-and-reconciliation-evidence/milestones/03-reconciliation-eligibility-gates - .day-shift/planning/17-programmatic-workflow-enforcement/phases/05-heuristics-and-derived-state-gates/milestones/01-planning-language-and-decomposition-warnings - .day-shift/planning/17-programmatic-workflow-enforcement/phases/05-heuristics-and-derived-state-gates/milestones/02-lightweight-promotion-pressure - .day-shift/planning/17-programmatic-workflow-enforcement/phases/05-heuristics-and-derived-state-gates/milestones/03-derived-state-sync-eligibility - .day-shift/planning/17-programmatic-workflow-enforcement/phases/06-reporting-guidance-and-regression-coverage/milestones/01-finding-taxonomy-and-output-guidance - .day-shift/planning/17-programmatic-workflow-enforcement/phases/06-reporting-guidance-and-regression-coverage/milestones/02-workflow-prompt-reference-alignment - .day-shift/planning/17-programmatic-workflow-enforcement/phases/06-reporting-guidance-and-regression-coverage/milestones/03-cross-family-regression-coverage - .day-shift/planning/17-programmatic-workflow-enforcement/phases/07-layer-specific-overview-filename-migration/milestones/01-destination-contract-and-compatibility-policy - .day-shift/planning/17-programmatic-workflow-enforcement/phases/07-layer-specific-overview-filename-migration/milestones/02-scaffold-navigation-and-link-resolution - .day-shift/planning/17-programmatic-workflow-enforcement/phases/07-layer-specific-overview-filename-migration/milestones/03-docs-templates-and-regression-coverage - .day-shift/planning/18-day-shift-version-manager/phases/01-command-surface-and-shim-runtime/milestones/01-command-family-contract - .day-shift/planning/18-day-shift-version-manager/phases/01-command-surface-and-shim-runtime/milestones/02-shim-dispatch-runtime - .day-shift/planning/18-day-shift-version-manager/phases/01-command-surface-and-shim-runtime/milestones/03-runtime-diagnostics - .day-shift/planning/18-day-shift-version-manager/phases/02-managed-state-and-install-validation/milestones/01-state-root-and-layout - .day-shift/planning/18-day-shift-version-manager/phases/02-managed-state-and-install-validation/milestones/02-local-source-install-validation - .day-shift/planning/18-day-shift-version-manager/phases/02-managed-state-and-install-validation/milestones/03-managed-version-write-path - .day-shift/planning/18-day-shift-version-manager/phases/03-selection-aliases-and-pinning/milestones/01-resolution-precedence - .day-shift/planning/18-day-shift-version-manager/phases/03-selection-aliases-and-pinning/milestones/02-repository-pins-and-config-defaults - .day-shift/planning/18-day-shift-version-manager/phases/03-selection-aliases-and-pinning/milestones/03-aliases-and-partial-selectors - .day-shift/planning/18-day-shift-version-manager/phases/04-uninstall-and-license-preservation/milestones/01-targeted-uninstall-contract - .day-shift/planning/18-day-shift-version-manager/phases/04-uninstall-and-license-preservation/milestones/02-selector-impact-and-replacement - .day-shift/planning/18-day-shift-version-manager/phases/04-uninstall-and-license-preservation/milestones/03-license-preservation-and-coverage - .day-shift/planning/18-day-shift-version-manager/phases/05-inspection-network-and-cross-platform-diagnostics/milestones/01-list-current-and-doctor-output - .day-shift/planning/18-day-shift-version-manager/phases/05-inspection-network-and-cross-platform-diagnostics/milestones/02-approval-gated-network-check - .day-shift/planning/18-day-shift-version-manager/phases/05-inspection-network-and-cross-platform-diagnostics/milestones/03-cross-platform-path-diagnostics - .day-shift/planning/18-day-shift-version-manager/phases/06-regression-coverage-and-release-handoff/milestones/01-runtime-selection-regressions - .day-shift/planning/18-day-shift-version-manager/phases/06-regression-coverage-and-release-handoff/milestones/02-install-uninstall-license-regressions - .day-shift/planning/18-day-shift-version-manager/phases/06-regression-coverage-and-release-handoff/milestones/03-diagnostics-and-release-handoff - .day-shift/planning/19-trace-link-lifecycle-management/phases/01-disposition-model-and-storage-contract/milestones/01-disposition-schema-and-identity - .day-shift/planning/19-trace-link-lifecycle-management/phases/01-disposition-model-and-storage-contract/milestones/02-storage-location-and-file-contract - .day-shift/planning/19-trace-link-lifecycle-management/phases/01-disposition-model-and-storage-contract/milestones/03-apply-evidence-and-safety-boundaries - .day-shift/planning/19-trace-link-lifecycle-management/phases/02-discovery-and-preview-surfaces/milestones/01-affected-artifact-discovery - .day-shift/planning/19-trace-link-lifecycle-management/phases/02-discovery-and-preview-surfaces/milestones/02-migration-preview-output - .day-shift/planning/19-trace-link-lifecycle-management/phases/02-discovery-and-preview-surfaces/milestones/03-read-only-posture-regressions - .day-shift/planning/19-trace-link-lifecycle-management/phases/03-disposition-crud-cli/milestones/01-command-family-routing-and-help - .day-shift/planning/19-trace-link-lifecycle-management/phases/03-disposition-crud-cli/milestones/02-add-update-delete-behavior - .day-shift/planning/19-trace-link-lifecycle-management/phases/03-disposition-crud-cli/milestones/03-list-show-and-error-output - .day-shift/planning/19-trace-link-lifecycle-management/phases/04-forward-link-apply-workflow/milestones/01-apply-selection-and-dry-run-parity - .day-shift/planning/19-trace-link-lifecycle-management/phases/04-forward-link-apply-workflow/milestones/02-safe-forward-link-mutation - .day-shift/planning/19-trace-link-lifecycle-management/phases/04-forward-link-apply-workflow/milestones/03-apply-reporting-and-rollback-guidance - .day-shift/planning/19-trace-link-lifecycle-management/phases/05-validation-integration/milestones/01-links-check-disposition-findings - .day-shift/planning/19-trace-link-lifecycle-management/phases/05-validation-integration/milestones/02-smoke-and-rollup-lifecycle-evidence - .day-shift/planning/19-trace-link-lifecycle-management/phases/05-validation-integration/milestones/03-validation-no-write-regressions - .day-shift/planning/19-trace-link-lifecycle-management/phases/06-guidance-regression-and-release-handoff/milestones/01-guidance-and-help-text-alignment - .day-shift/planning/19-trace-link-lifecycle-management/phases/06-guidance-regression-and-release-handoff/milestones/02-regression-coverage-matrix - .day-shift/planning/19-trace-link-lifecycle-management/phases/06-guidance-regression-and-release-handoff/milestones/03-release-handoff-and-deferred-scope - .day-shift/planning/20-lifecycle-friction-reduction/phases/01-scaffold-contract-intelligence/milestones/01-milestone-scaffold-inheritance - .day-shift/planning/20-lifecycle-friction-reduction/phases/01-scaffold-contract-intelligence/milestones/02-task-scaffold-inheritance - .day-shift/planning/20-lifecycle-friction-reduction/phases/01-scaffold-contract-intelligence/milestones/03-upstream-metadata-preservation - .day-shift/planning/20-lifecycle-friction-reduction/phases/02-evidence-aware-review-behavior/milestones/01-active-evidence-warning-downgrade - .day-shift/planning/20-lifecycle-friction-reduction/phases/02-evidence-aware-review-behavior/milestones/02-declared-later-work-classification - .day-shift/planning/20-lifecycle-friction-reduction/phases/02-evidence-aware-review-behavior/milestones/03-actionable-review-findings - .day-shift/planning/20-lifecycle-friction-reduction/phases/03-closeout-build-and-status-sync/milestones/01-implementation-summary-build-closeout - .day-shift/planning/20-lifecycle-friction-reduction/phases/03-closeout-build-and-status-sync/milestones/02-reconciliation-build-closeout - .day-shift/planning/20-lifecycle-friction-reduction/phases/03-closeout-build-and-status-sync/milestones/03-explicit-status-metadata-sync - .day-shift/planning/20-lifecycle-friction-reduction/phases/04-task-scoped-change-evidence/milestones/01-task-scope-change-report - .day-shift/planning/20-lifecycle-friction-reduction/phases/04-task-scoped-change-evidence/milestones/02-path-category-classification - .day-shift/planning/20-lifecycle-friction-reduction/phases/04-task-scoped-change-evidence/milestones/03-summary-closeout-evidence-feed - .day-shift/planning/20-lifecycle-friction-reduction/phases/05-regression-guidance-and-release-handoff/milestones/01-command-family-regression-update - .day-shift/planning/20-lifecycle-friction-reduction/phases/05-regression-guidance-and-release-handoff/milestones/02-workflow-guidance-alignment - .day-shift/planning/20-lifecycle-friction-reduction/phases/05-regression-guidance-and-release-handoff/milestones/03-release-handoff-evidence - .day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/milestones/01-command-surface-inventory - .day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/milestones/02-guidance-command-adoption-map - .day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/milestones/03-prompt-reference-workflow-alignment - .day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/milestones/04-adoption-validation-and-gap-report - .day-shift/planning/20-lifecycle-friction-reduction/phases/06-command-surface-adoption-audit/milestones/05-machine-readable-command-inventory-export - .day-shift/planning/20-lifecycle-friction-reduction/phases/07-markdown-link-materialization/milestones/01-materialization-command-contract - .day-shift/planning/20-lifecycle-friction-reduction/phases/07-markdown-link-materialization/milestones/02-body-reference-source-locations - .day-shift/planning/20-lifecycle-friction-reduction/phases/07-markdown-link-materialization/milestones/03-markdown-link-rewrite-engine - .day-shift/planning/20-lifecycle-friction-reduction/phases/07-markdown-link-materialization/milestones/04-cli-integration-and-guidance - .day-shift/planning/20-lifecycle-friction-reduction/phases/07-markdown-link-materialization/milestones/05-regression-and-validation-coverage - .day-shift/planning/21-runtime-evidence-gates/phases/01-execution-mode-and-runtime-delta-contracts/milestones/01-execution-mode-metadata - .day-shift/planning/21-runtime-evidence-gates/phases/01-execution-mode-and-runtime-delta-contracts/milestones/02-runtime-delta-contract - .day-shift/planning/21-runtime-evidence-gates/phases/01-execution-mode-and-runtime-delta-contracts/milestones/03-contract-closeout-boundary - .day-shift/planning/21-runtime-evidence-gates/phases/02-path-classification-and-change-evidence/milestones/01-default-doc-path-classifier - .day-shift/planning/21-runtime-evidence-gates/phases/02-path-classification-and-change-evidence/milestones/02-repository-path-policy - .day-shift/planning/21-runtime-evidence-gates/phases/02-path-classification-and-change-evidence/milestones/03-changed-path-evidence - .day-shift/planning/21-runtime-evidence-gates/phases/02-path-classification-and-change-evidence/milestones/04-runtime-target-alignment - .day-shift/planning/21-runtime-evidence-gates/phases/03-closeout-review-and-validation-gates/milestones/01-task-readiness-mode-gates - .day-shift/planning/21-runtime-evidence-gates/phases/03-closeout-review-and-validation-gates/milestones/02-summary-closeout-gates - .day-shift/planning/21-runtime-evidence-gates/phases/03-closeout-review-and-validation-gates/milestones/03-reconciliation-runtime-evidence - .day-shift/planning/21-runtime-evidence-gates/phases/03-closeout-review-and-validation-gates/milestones/04-validation-exception-policy - .day-shift/planning/21-runtime-evidence-gates/phases/04-workflow-separation-and-loop-detection/milestones/01-contract-to-runtime-handoff - .day-shift/planning/21-runtime-evidence-gates/phases/04-workflow-separation-and-loop-detection/milestones/02-documentation-loop-detection - .day-shift/planning/21-runtime-evidence-gates/phases/04-workflow-separation-and-loop-detection/milestones/03-breakout-task-requirement - .day-shift/planning/21-runtime-evidence-gates/phases/04-workflow-separation-and-loop-detection/milestones/04-phase-and-milestone-review-alignment - .day-shift/planning/21-runtime-evidence-gates/phases/05-guidance-template-and-policy-pack-alignment/milestones/01-template-mode-and-delta-content - .day-shift/planning/21-runtime-evidence-gates/phases/05-guidance-template-and-policy-pack-alignment/milestones/02-prompt-and-workflow-guidance - .day-shift/planning/21-runtime-evidence-gates/phases/05-guidance-template-and-policy-pack-alignment/milestones/03-command-output-guidance - .day-shift/planning/21-runtime-evidence-gates/phases/05-guidance-template-and-policy-pack-alignment/milestones/04-portable-policy-pack - .day-shift/planning/21-runtime-evidence-gates/phases/06-regression-and-ci-enforcement/milestones/01-mode-and-delta-regressions - .day-shift/planning/21-runtime-evidence-gates/phases/06-regression-and-ci-enforcement/milestones/02-classifier-and-evidence-regressions - .day-shift/planning/21-runtime-evidence-gates/phases/06-regression-and-ci-enforcement/milestones/03-review-gate-regressions - .day-shift/planning/21-runtime-evidence-gates/phases/06-regression-and-ci-enforcement/milestones/04-ci-policy-enforcement - .day-shift/planning/22-small-model-agent-efficiency/phases/01-consolidate-and-close-related-specifications/milestones/01-build-related-spec-coverage-matrix - .day-shift/planning/22-small-model-agent-efficiency/phases/01-consolidate-and-close-related-specifications/milestones/02-recertify-linkage-and-lifecycle-evidence - .day-shift/planning/22-small-model-agent-efficiency/phases/01-consolidate-and-close-related-specifications/milestones/03-record-closeout-and-archive-eligible-specs - .day-shift/planning/22-small-model-agent-efficiency/phases/02-version-automation-protocol-and-schemas/milestones/01-define-protocol-version-and-feature-negotiation - .day-shift/planning/22-small-model-agent-efficiency/phases/02-version-automation-protocol-and-schemas/milestones/02-establish-canonical-schema-catalog - .day-shift/planning/22-small-model-agent-efficiency/phases/02-version-automation-protocol-and-schemas/milestones/03-integrate-runtime-validation-and-generated-types - .day-shift/planning/22-small-model-agent-efficiency/phases/03-bound-and-page-output-contracts/milestones/01-implement-detail-grouping-and-filter-contracts - .day-shift/planning/22-small-model-agent-efficiency/phases/03-bound-and-page-output-contracts/milestones/02-add-deterministic-pagination-and-completeness - .day-shift/planning/22-small-model-agent-efficiency/phases/03-bound-and-page-output-contracts/milestones/03-enforce-output-budgets-and-bounded-failures - .day-shift/planning/22-small-model-agent-efficiency/phases/04-authoritative-command-descriptors-and-tool-discovery/milestones/01-establish-authoritative-command-descriptor-registry - .day-shift/planning/22-small-model-agent-efficiency/phases/04-authoritative-command-descriptors-and-tool-discovery/milestones/02-deliver-focused-discovery-and-tool-manifests - .day-shift/planning/22-small-model-agent-efficiency/phases/04-authoritative-command-descriptors-and-tool-discovery/milestones/03-add-structured-input-and-drift-validation - .day-shift/planning/22-small-model-agent-efficiency/phases/05-explicit-work-selection-and-concurrency/milestones/01-deliver-actionable-candidate-discovery - .day-shift/planning/22-small-model-agent-efficiency/phases/05-explicit-work-selection-and-concurrency/milestones/02-implement-local-selection-lifecycle-and-precedence - .day-shift/planning/22-small-model-agent-efficiency/phases/05-explicit-work-selection-and-concurrency/milestones/03-protect-selection-state-with-concurrency-evidence - .day-shift/planning/22-small-model-agent-efficiency/phases/06-artifact-scoped-context-and-context-packs/milestones/01-deliver-artifact-scoped-agent-context - .day-shift/planning/22-small-model-agent-efficiency/phases/06-artifact-scoped-context-and-context-packs/milestones/02-build-relevance-ranked-context-packs - .day-shift/planning/22-small-model-agent-efficiency/phases/06-artifact-scoped-context-and-context-packs/milestones/03-integrate-budget-freshness-and-exclusion-reporting - .day-shift/planning/22-small-model-agent-efficiency/phases/07-scoped-health-and-relevant-blockers/milestones/01-separate-health-domains-and-command-surfaces - .day-shift/planning/22-small-model-agent-efficiency/phases/07-scoped-health-and-relevant-blockers/milestones/02-classify-action-relevant-blockers - .day-shift/planning/22-small-model-agent-efficiency/phases/07-scoped-health-and-relevant-blockers/milestones/03-integrate-scoped-health-with-context-and-validation - .day-shift/planning/22-small-model-agent-efficiency/phases/08-executable-workflow-actions-and-recovery/milestones/01-model-executable-workflow-state-and-actions - .day-shift/planning/22-small-model-agent-efficiency/phases/08-executable-workflow-actions-and-recovery/milestones/02-standardize-typed-failures-and-recovery-actions - .day-shift/planning/22-small-model-agent-efficiency/phases/08-executable-workflow-actions-and-recovery/milestones/03-add-evidence-backed-resume-capsules - .day-shift/planning/22-small-model-agent-efficiency/phases/09-atomic-mutations-and-crash-recovery/milestones/01-establish-atomic-single-file-write-primitive - .day-shift/planning/22-small-model-agent-efficiency/phases/09-atomic-mutations-and-crash-recovery/milestones/02-deliver-multi-file-plans-preconditions-and-receipts - .day-shift/planning/22-small-model-agent-efficiency/phases/09-atomic-mutations-and-crash-recovery/milestones/03-add-locking-rollback-and-crash-recovery - .day-shift/planning/22-small-model-agent-efficiency/phases/10-canonical-policy-composition-and-trust-boundaries/milestones/01-establish-canonical-policy-rules-and-composition - .day-shift/planning/22-small-model-agent-efficiency/phases/10-canonical-policy-composition-and-trust-boundaries/milestones/02-enforce-trust-lanes-and-prompt-injection-boundaries - .day-shift/planning/22-small-model-agent-efficiency/phases/10-canonical-policy-composition-and-trust-boundaries/milestones/03-unify-authorization-redaction-and-sanitization - .day-shift/planning/22-small-model-agent-efficiency/phases/11-constrained-execution-profiles-and-task-sizing/milestones/01-define-constrained-profile-and-readiness-gates - .day-shift/planning/22-small-model-agent-efficiency/phases/11-constrained-execution-profiles-and-task-sizing/milestones/02-add-advisory-task-sizing-and-decomposition - .day-shift/planning/22-small-model-agent-efficiency/phases/11-constrained-execution-profiles-and-task-sizing/milestones/03-integrate-profile-decisions-and-calibration-hooks - .day-shift/planning/22-small-model-agent-efficiency/phases/12-shared-artifact-parsing-and-architecture-decomposition/milestones/01-characterize-and-build-shared-artifact-parser - .day-shift/planning/22-small-model-agent-efficiency/phases/12-shared-artifact-parsing-and-architecture-decomposition/milestones/02-migrate-planning-and-validation-callers - .day-shift/planning/22-small-model-agent-efficiency/phases/12-shared-artifact-parsing-and-architecture-decomposition/milestones/03-decompose-command-adapters-and-priority-hotspots - .day-shift/planning/22-small-model-agent-efficiency/phases/13-evidence-freshness-observability-and-performance/milestones/01-implement-incremental-state-and-freshness-indexing - .day-shift/planning/22-small-model-agent-efficiency/phases/13-evidence-freshness-observability-and-performance/milestones/02-add-cache-lifecycle-and-bounded-decision-traces - .day-shift/planning/22-small-model-agent-efficiency/phases/13-evidence-freshness-observability-and-performance/milestones/03-establish-performance-benchmarks-and-regression-gates - .day-shift/planning/22-small-model-agent-efficiency/phases/14-small-model-evaluation-and-calibration/milestones/01-build-deterministic-trajectory-harness - .day-shift/planning/22-small-model-agent-efficiency/phases/14-small-model-evaluation-and-calibration/milestones/02-add-adversarial-corpus-and-payload-budgets - .day-shift/planning/22-small-model-agent-efficiency/phases/14-small-model-evaluation-and-calibration/milestones/03-calibrate-real-model-baselines-and-promotion-gates - .day-shift/planning/23-eadl-qualification-analysis/phases/01-repository-model-and-evidence-baseline/milestones/01-revision-and-evidence-inventory - .day-shift/planning/23-eadl-qualification-analysis/phases/01-repository-model-and-evidence-baseline/milestones/02-implemented-repository-model - .day-shift/planning/23-eadl-qualification-analysis/phases/02-qualification-and-trace-analysis/milestones/01-thirteen-criterion-evidence-matrix - .day-shift/planning/23-eadl-qualification-analysis/phases/02-qualification-and-trace-analysis/milestones/02-representative-workflow-trace - .day-shift/planning/23-eadl-qualification-analysis/phases/03-classification-and-report-synthesis/milestones/01-classification-and-qualification-boundary - .day-shift/planning/23-eadl-qualification-analysis/phases/03-classification-and-report-synthesis/milestones/02-ten-section-report - .day-shift/planning/24-canonical-documentation-application/phases/01-application-and-content-foundation/milestones/01-starlight-application-scaffold - .day-shift/planning/24-canonical-documentation-application/phases/01-application-and-content-foundation/milestones/02-frontmatter-and-content-collection - .day-shift/planning/24-canonical-documentation-application/phases/01-application-and-content-foundation/milestones/03-initial-information-architecture - .day-shift/planning/24-canonical-documentation-application/phases/02-publication-and-artifact-pipeline/milestones/01-publication-eligibility-contract - .day-shift/planning/24-canonical-documentation-application/phases/02-publication-and-artifact-pipeline/milestones/02-inference-artifact-generation - .day-shift/planning/24-canonical-documentation-application/phases/02-publication-and-artifact-pipeline/milestones/03-command-and-build-lifecycle - .day-shift/planning/24-canonical-documentation-application/phases/03-marketing-content-migration/milestones/01-website-content-inventory - .day-shift/planning/24-canonical-documentation-application/phases/03-marketing-content-migration/milestones/02-canonical-content-migration - .day-shift/planning/24-canonical-documentation-application/phases/03-marketing-content-migration/milestones/03-website-entry-point-transition - .day-shift/planning/24-canonical-documentation-application/phases/04-integrated-verification-and-deployment/milestones/01-end-to-end-publication-verification - .day-shift/planning/24-canonical-documentation-application/phases/04-integrated-verification-and-deployment/milestones/02-cross-application-and-domain-verification - .day-shift/planning/24-canonical-documentation-application/phases/04-integrated-verification-and-deployment/milestones/03-vercel-readiness-and-release-gate - .day-shift/planning/24-canonical-documentation-application/phases/05-installation-init-and-workspace-onboarding/milestones/01-canonical-page-inventory-and-entry-points - .day-shift/planning/24-canonical-documentation-application/phases/05-installation-init-and-workspace-onboarding/milestones/02-installation-and-version-management - .day-shift/planning/24-canonical-documentation-application/phases/05-installation-init-and-workspace-onboarding/milestones/03-init-and-workspace-anatomy - .day-shift/planning/24-canonical-documentation-application/phases/05-installation-init-and-workspace-onboarding/milestones/04-configuration-shell-and-first-health-checks - .day-shift/planning/24-canonical-documentation-application/phases/06-end-to-end-workflow-and-artifact-lifecycle/milestones/01-operating-model-and-artifact-concepts - .day-shift/planning/24-canonical-documentation-application/phases/06-end-to-end-workflow-and-artifact-lifecycle/milestones/02-intake-to-implementation-workflow - .day-shift/planning/24-canonical-documentation-application/phases/06-end-to-end-workflow-and-artifact-lifecycle/milestones/03-evidence-review-and-reconciliation-lifecycle - .day-shift/planning/24-canonical-documentation-application/phases/06-end-to-end-workflow-and-artifact-lifecycle/milestones/04-resume-trace-archive-and-release-handoff - .day-shift/planning/24-canonical-documentation-application/phases/07-prompts-templates-and-customization/milestones/01-prompt-and-template-catalogs - .day-shift/planning/24-canonical-documentation-application/phases/07-prompts-templates-and-customization/milestones/02-discovery-rendering-and-trust-boundaries - .day-shift/planning/24-canonical-documentation-application/phases/07-prompts-templates-and-customization/milestones/03-workspace-customization-workflows - .day-shift/planning/24-canonical-documentation-application/phases/07-prompts-templates-and-customization/milestones/04-upgrade-merge-and-drift-maintenance - .day-shift/planning/24-canonical-documentation-application/phases/08-complete-cli-and-automation-reference/milestones/01-command-and-capability-inventory - .day-shift/planning/24-canonical-documentation-application/phases/08-complete-cli-and-automation-reference/milestones/02-core-workflow-command-reference - .day-shift/planning/24-canonical-documentation-application/phases/08-complete-cli-and-automation-reference/milestones/03-operational-and-administration-reference - .day-shift/planning/24-canonical-documentation-application/phases/08-complete-cli-and-automation-reference/milestones/04-structured-automation-and-extension-contracts - .day-shift/planning/24-canonical-documentation-application/phases/09-documentation-coverage-and-drift-verification/milestones/01-page-disposition-and-substance-closure - .day-shift/planning/24-canonical-documentation-application/phases/09-documentation-coverage-and-drift-verification/milestones/02-product-surface-coverage-verification - .day-shift/planning/24-canonical-documentation-application/phases/09-documentation-coverage-and-drift-verification/milestones/03-example-link-and-troubleshooting-verification - .day-shift/planning/24-canonical-documentation-application/phases/09-documentation-coverage-and-drift-verification/milestones/04-continuous-documentation-drift-gates - .day-shift/planning/25-website/phases/01-measurement-and-baseline/milestones/01-analytics-runtime-and-privacy-contract - .day-shift/planning/25-website/phases/01-measurement-and-baseline/milestones/02-funnel-and-commercial-confirmation - .day-shift/planning/25-website/phases/01-measurement-and-baseline/milestones/03-field-performance-and-baseline-window - .day-shift/planning/25-website/phases/02-positioning-navigation-and-product-proof/milestones/01-first-contact-positioning-and-actions - .day-shift/planning/25-website/phases/02-positioning-navigation-and-product-proof/milestones/02-homepage-narrative-and-navigation - .day-shift/planning/25-website/phases/02-positioning-navigation-and-product-proof/milestones/03-reproducible-product-demonstration - .day-shift/planning/25-website/phases/02-positioning-navigation-and-product-proof/milestones/04-compatibility-and-proof-boundaries - .day-shift/planning/25-website/phases/03-commercial-journey-and-trust/milestones/01-authoritative-plan-and-pricing-contract - .day-shift/planning/25-website/phases/03-commercial-journey-and-trust/milestones/02-checkout-delivery-upgrade-and-recovery - .day-shift/planning/25-website/phases/03-commercial-journey-and-trust/milestones/03-publisher-support-privacy-and-security-trust - .day-shift/planning/25-website/phases/03-commercial-journey-and-trust/milestones/04-public-copy-and-documentation-reconciliation - .day-shift/planning/25-website/phases/04-discovery-accessibility-and-performance/milestones/01-route-metadata-canonical-and-social-contracts - .day-shift/planning/25-website/phases/04-discovery-accessibility-and-performance/milestones/02-crawl-surfaces-and-structured-data - .day-shift/planning/25-website/phases/04-discovery-accessibility-and-performance/milestones/03-accessible-semantics-and-interactions - .day-shift/planning/25-website/phases/04-discovery-accessibility-and-performance/milestones/04-responsive-and-performance-budgets - .day-shift/planning/25-website/phases/05-integrated-validation-and-release-evidence/milestones/01-deterministic-website-and-cross-app-gates - .day-shift/planning/25-website/phases/05-integrated-validation-and-release-evidence/milestones/02-critical-marketing-and-commerce-journeys - .day-shift/planning/25-website/phases/05-integrated-validation-and-release-evidence/milestones/03-manual-quality-and-external-review