docs: record PR16 landing plus side-chain restacks - #17
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 29f91f9c65
ℹ️ 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".
|
|
||
| On 2026-09-09 the review-to-merge loop collapsed the writer stack through ordinary merge commits without force-push, branch deletion, or protection changes, following the PR #9 precedent for unprotected stacked branches. PRs #2, #3, #4, #5, #6, #7, and #8 merged bottom-up between 01:10:44Z and 01:14:13Z, each with exact-head `verify` GREEN, zero unresolved review threads, and MERGEABLE/CLEAN state re-fetched immediately before its merge. The local-only restore-contract commit `878d0ce` was pushed as a new branch and opened as successor PR #14 on the PR #8 head; its Codex P2 review correctly showed the URL and `collection_without_retention_count` markers could not detect a coupled revision-`...0003` seed-plus-query change from `none` to `applies`. Commit `d0da193` binds the `...0003`/`none` seed tuple, its `support_email` item seed, and the revision-specific query predicates together; a negative control proved the old markers pass that coupled mutation while the new predicates fail it, and the review thread was resolved with that evidence. CI `34298653319` passed on `d0da193`, and PR #14 merged at 01:25:12Z. PR #13 (dependency pin and toolchain classification for issue #12) merged at 01:19:32Z on its immutable GREEN pair of head `eff7ec19f511` and CI `34251045288`, advancing the docs readiness branch to `bbea5c9`, whose fresh `verify` (`34298735574`) is GREEN. No PR was closed: 9 merges leave drafts #1, #10, and #11 open, each retaining a valid delta. `develop` still declares 16 `latest` occurrences, which explains PR #1's `dependency-review` failure; the pinned manifest (zero `latest`) sits at the top of the side chain and reaches `develop` only through the PR #10 to #11 to down-chain successor path. PR #1's remaining failures are the two CodeQL compatibility analyses plus `dependency-review`; `verify`, Noema, OpenCode, Strix, Semgrep, Trivy, OSV, and Scorecard are GREEN on its current head. Central-workflow run logs live in the organization central repository, so a leaf-side run fetch returns 404; such incidents go through the central owner path rather than leaf-side churn or bypass. The chain tip carrying the full writer delta is `origin/codex/policyweave-concurrent-writer-evidence` (`df9eef5`), with sibling successors `codex/policyweave-json-export` (PR #10, draft; its buyer-visible export enablement needs product review plus a base update now that its base moved) and this ledger branch stacked above it. The repository has no scheduled workflow (only `ci.yml`, no `schedule` trigger), so the hourly cadence is served by the autoresearch loop's own status messages rather than an in-repo scheduler. This remains CI durability evidence with no hosted adapter, tenant authorization, audit, encryption, or released datastore. | ||
|
|
||
| PR #16 landed the full writer-stack tip in `develop` at `7bf0fa9`. The side chain was then restacked without force: PR #10 head merged tip `111400a` via `cef8c0b` (auto-merged baseline/test regions verified coherent with no markers; merged-tree local gates GREEN with 71/71 tests), and PR #11 head merged the restacked export head via `e67c34c` with one Active-order conflict resolved by preserving both sides. Merged-tree local gates were GREEN (lint, 76/76 tests, build). Both restacks requested fresh CodeRabbit review; exact-head CI `34301731941` (PR #10) and `34302266597` (PR #11) are GREEN on the restacked heads with zero unresolved threads on either. PR #1 on the new `develop` head still fails only the two CodeQL compatibility analyses plus `dependency-review` (16 `latest` declarations remain in `develop`; pins travel down-chain after the export/readiness drafts land), while every other central check is GREEN. No PR was closed in this turn; drafts #1, #10, and #11 retain valid deltas. |
There was a problem hiding this comment.
This update records that PR #16 landed the full writer-stack tip, but the document's current “Active commercialization order” still lists landing that same tip as its first outstanding action at line 84. Anyone using this baseline to plan the next work is therefore directed to repeat a completed operation; update the active order to begin with the remaining PR #10/#11 and PR #1 work.
AGENTS.md reference: AGENTS.md:L11-L11
Useful? React with 👍 / 👎.
1 participant
Docs-only ledger on develop. Records PR #16 tip landing, non-force restacks of PRs #10/#11 with exact-head CI evidence (34301731941, 34302266597), zero unresolved threads, and PR #1's remaining blockers. Local note: full-suite runs on this machine show load-dependent flakes in timing-sensitive UI tests (failing set varies 7/2/1 across runs; failing files pass in isolation; hosted verify passed identical code for PR #16). Hosted CI is the gate. Merges via ordinary merge commit without force-push.