From 7708ad42d67e0f3c58dc7658929d3a312652c523 Mon Sep 17 00:00:00 2001 From: leynos Date: Sun, 14 Jun 2026 07:33:01 +0200 Subject: [PATCH] Mark 6.1.2 nested-fixture execplan complete The roadmap-6.1.2 work shipped on `main` via PR #340, but the execplan document was merged with a stale `Status: IN PROGRESS` header and two unchecked Progress items for the pull request lifecycle. Update the execplan to record completion: set `Status` to `COMPLETE`, check the ready-for-review and merged Progress items against PR #340, add a completion summary to `Outcomes & retrospective`, and log the edit in the revision history. Co-Authored-By: Claude Opus 4.8 (1M context) --- ...ested-command-tree-behavioural-fixtures.md | 26 ++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/docs/execplans/6-1-2-nested-command-tree-behavioural-fixtures.md b/docs/execplans/6-1-2-nested-command-tree-behavioural-fixtures.md index 137106db..1772769e 100644 --- a/docs/execplans/6-1-2-nested-command-tree-behavioural-fixtures.md +++ b/docs/execplans/6-1-2-nested-command-tree-behavioural-fixtures.md @@ -5,7 +5,7 @@ This ExecPlan (execution plan) is a living document. The sections `Decision Log`, and `Outcomes & Retrospective` must be kept up to date as work proceeds. -Status: IN PROGRESS +Status: COMPLETE This plan covers roadmap item 6.1.2 only. It builds on roadmap item 6.1.1 (see `docs/execplans/6-1-1-recursive-doc-metadata-subcommands-values.md`), @@ -1256,8 +1256,8 @@ section must always reflect the actual current state of the work. - [x] (2026-06-04) Milestone 5 complete (documentation, changelog, schema round-trip fixture, roadmap entry, full gates, and CodeRabbit clear). -- [ ] Draft pull request moved to ready-for-review. -- [ ] Pull request merged into `main`. +- [x] (2026-06-14) Draft pull request moved to ready-for-review (PR #340). +- [x] (2026-06-14) Pull request merged into `main` (PR #340). Use timestamps to detect tolerance breaches and to feed retrospectives. @@ -1486,6 +1486,22 @@ what would be done differently next time. nested-fixture coverage. The focused schema test passed, followed by `make check-fmt`, `make lint`, `make test`, `make markdownlint`, and `make nixie`. `coderabbit review --agent` reported zero findings. +- 2026-06-14: Plan complete. All five milestones landed on `main` via + PR #340 ("Nested command tree behavioural fixtures (6.1.2)"), merged on + 2026-06-14. The roadmap entry 6.1.2 and its three sub-bullets are marked + done. Measured against the original purpose, the plan delivered: the + `NestedDocsConfig` behavioural fixture, recursive `rstest` IR assertions, + rstest-bdd scenarios, roff/`PowerShell`/MAML renderer compatibility + coverage, `insta` golden snapshots, an end-to-end bridge smoke test, and + the schema round-trip and documentation updates — all without an IR + schema change or new public API, staying inside the stated tolerances. + Deferred work surfaced during implementation (parent-to-child + `WindowsMetadata` propagation; normalising the pre-existing BDD-harness + Clippy debt behind the newly registered `rstest_bdd` target) was recorded + for a future roadmap item rather than expanded into this one. Lesson for + next time: register dormant integration-test targets early — the + `rstest_bdd` target gap (see "Surprises & discoveries") meant the + behavioural suite was not observable under `make test` until Milestone 2. ## Notes for the accompanying draft pull request @@ -1528,3 +1544,7 @@ remaining work. - 2026-06-04 (implementer): recorded Milestone 5 documentation, schema round-trip, roadmap close-out, validation, and CodeRabbit review outcome. +- 2026-06-14 (implementer): set `Status` to `COMPLETE`, checked the + remaining Progress items, and added the completion entry to + `Outcomes & retrospective` after PR #340 merged the full plan into + `main`.