docs: conclude 2026-05-29 session — MASTERPLAN, RFAI status, failure ledger, ADRs#1121
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the project documentation to reflect the completion of the RFAI roadmap and details recent hardening and dependency updates. Specifically, it introduces ADR-0034, which establishes dependency version caps for Entity Framework Core (8.x) and FluentAssertions (7.x) to prevent recurring major-version update churn. The reviewer suggests using a wildcard pattern for Microsoft.EntityFrameworkCore.* and capping the design-time tools package (Microsoft.EntityFrameworkCore.Tools) alongside the runtime packages to ensure toolset compatibility and avoid design-time errors.
| - `Microsoft.EntityFrameworkCore`, `Microsoft.EntityFrameworkCore.Sqlite`, | ||
| `Microsoft.EntityFrameworkCore.Design` — stay on 8.x until the runtime EF stack is | ||
| migrated together in one deliberate PR. `Microsoft.EntityFrameworkCore.Tools` is a | ||
| design-time-only package (`PrivateAssets`) tracked separately on its 10.x line and is | ||
| intentionally **not** capped (it does not affect the runtime compile). |
There was a problem hiding this comment.
Using a wildcard pattern like Microsoft.EntityFrameworkCore.* in .github/dependabot.yml is more robust as it automatically covers all EF Core ecosystem packages (such as .Relational or test-specific providers) and prevents partial upgrades that could reintroduce version splits.
Additionally, keeping Microsoft.EntityFrameworkCore.Tools on a different major version (10.x) than the runtime packages (8.x) and Microsoft.EntityFrameworkCore.Design (8.x) is generally discouraged. Mismatched design-time tools can cause errors during migration generation or database updates. Capping the tools package alongside the rest of the EF Core stack ensures complete toolset compatibility.
| - `Microsoft.EntityFrameworkCore`, `Microsoft.EntityFrameworkCore.Sqlite`, | |
| `Microsoft.EntityFrameworkCore.Design` — stay on 8.x until the runtime EF stack is | |
| migrated together in one deliberate PR. `Microsoft.EntityFrameworkCore.Tools` is a | |
| design-time-only package (`PrivateAssets`) tracked separately on its 10.x line and is | |
| intentionally **not** capped (it does not affect the runtime compile). | |
| - All Microsoft.EntityFrameworkCore.* packages (including .Sqlite, .Design, and .Tools via a wildcard pattern) — stay on 8.x until the runtime EF stack is migrated together in one deliberate PR. Capping the tools package alongside the runtime and design packages ensures toolset compatibility and prevents design-time errors during migration generation. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0588e2504e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Delivered in the latest cycle: | ||
|
|
||
| Continuous-cycle wave (2026-05-29, 18 PRs merged, backlog cleared to zero open PRs; 2 independent adversarial reviews per PR, all findings of every severity addressed including bot comments): |
There was a problem hiding this comment.
Align the merged-PR count with STATUS
This new cycle summary records "18 PRs merged", but the same commit leaves docs/STATUS.md (the documented source of truth) saying "17 PRs merged" for the same 2026-05-29 wave. Agents use these canonical docs for handoff and planning, so this reintroduces docs drift immediately after noting that STATUS had been reconciled; please update STATUS in the same conclusion change or make the Masterplan count match it.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
Docs-only session wrap-up for the 2026-05-29 continuous-cycle wave, updating roadmap, execution, failure-ledger, and ADR records to reflect completed RFAI work and dependency-cap decisions.
Changes:
- Marks RFAI-10/11/12 and the overall RFAI roadmap as delivered.
- Adds a 2026-05-29 masterplan cycle outcome and new failure-ledger entries.
- Ratifies ADR-0033 and adds ADR-0034 for dependency version caps.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
docs/ISSUE_EXECUTION_GUIDE.md |
Updates RFAI roadmap issue statuses to delivered. |
docs/IMPLEMENTATION_MASTERPLAN.md |
Adds latest cycle outcome and updates the document date. |
docs/agentic/FAILURE_LEDGER.md |
Records recurring CI/dependency/worktree failure patterns and mitigations. |
docs/decisions/INDEX.md |
Updates ADR-0033 status and indexes ADR-0034. |
docs/decisions/ADR-0033-ambient-channel-vscode-over-voice.md |
Ratifies the ambient channel decision as accepted. |
docs/decisions/ADR-0034-dependency-version-caps.md |
Documents EF Core and FluentAssertions major-version cap policy. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| Delivered in the latest cycle: | ||
|
|
||
| Continuous-cycle wave (2026-05-29, 18 PRs merged, backlog cleared to zero open PRs; 2 independent adversarial reviews per PR, all findings of every severity addressed including bot comments): |
Adversarial Review 2 of 2 (independent) + Fix EvidenceIndependent fact-check verified every PR/issue citation, both ADRs, the FAILURE_LEDGER entries, the identity/authz claims, and PR-count mismatch (fixed). MASTERPLAN said "18 PRs" while the already-merged STATUS.md said "17"; the authoritative
All other content verified accurate (the reviewer specifically confirmed the stacked-PR ledger entry: #1095 merged 18:10:16 → #1096 auto-closed 18:10:19 → recovered as #1104). Both reviews complete; the one finding is addressed. |
Concludes the 2026-05-29 continuous-cycle session by recording it in the canonical docs (STATUS.md was already updated in #1119).
Changes
docs/IMPLEMENTATION_MASTERPLAN.md— new "Current Cycle Outcome" entry for the 18-PR wave (RFAI complete, composable/identity-authz hardening, dependency wave + ignore rules, a11y/housekeeping);Last Updated→ 2026-05-29.docs/ISSUE_EXECUTION_GUIDE.md— RFAI-10/11/12 marked delivered; RFAI roadmap noted complete (12/12, RFAI-01: Safety invariants, IA cut, eval seed, and recertification #973–RFAI-12: Learning loop UI, provenance drawer, Ollama flag, and beta gate #984).docs/agentic/FAILURE_LEDGER.md— logged the recurring failures + workarounds: EF Core 8/9 dependabot split (resolved via ignore rule), FluentAssertions v8 re-proposal (resolved), E2E Smoke board-restore flake (investigate-then-rerun), and the stacked-PR--delete-branchauto-close gotcha (retarget/rebase first).docs/decisions/— ADR-0033 ratified Accepted (RFAI-11 RFAI-11: Ambient channel hardening — VS Code extension + voice prototype #1079 shipped the VS Code extension); new ADR-0034 documents the dependency version-cap policy (EF Core 8.x + FluentAssertions 7.x via dependabot ignore rules, incl. the v8 licensing rationale); INDEX updated.Verification
node scripts/check-docs-governance.mjs→ passed.Docs-only; no code change.