product: checkpoint — 1.4.0 shipped to all channels (PDR-0009)#85
Conversation
…anches cleaned; CI-floor reading + wardline-drift recurrence Closing checkpoint for the 2026-06-29 session. No new decision (PDR-0008 already recorded + merged); this persists the session delta: metrics.md gets the PR #79 CI-floor GREEN reading and flags the wardline_taint_fact_conformance_oracle local-red/CI-green blind spot as RECURRED (promote clarion-72e1c1a07d to a guardrail); current-state refreshed to the true end-state (both warpline pieces shipped, branches deleted, fixed binary installed to local uv, stale "#77 open" docs corrected) and points the next session at DECIDE-a-new-Now. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…PDR-0009 Checkpoint for the 2026-07-01 session. New decision PDR-0009 (ship & publish loomweave 1.4.0 — owner-authorized): minor bump on 45 commits since 1.3.1, prepared as a held tag then pushed on owner say-so; PyPI + GitHub Release + crates.io all at 1.4.0. current-state + metrics refreshed: the 2026-06-29 wardline-drift (open question 4b) was re-vendored via #80 this cycle, but the CI-invisibility blind spot itself remains — clarion-72e1c1a07d promotion stays open. roadmap/vision untouched (no bet moved horizon; the Now field is still the three recorded candidates, DECIDE not run). Folds forward the prior owner-session checkpoint 1823911 (committed to local main but never pushed — it diverged behind this session's release PRs) via cherry-pick, so origin/main carries both its 2026-06-29 delta and this 2026-07-01 delta; the stranded local 1823911 is now superseded. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![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: e1ab182ae6
ℹ️ 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".
| - North-star (open collision families) = 0, **not re-swept** (this was federation | ||
| correctness, not graph identity — no identity/extraction code touched). |
There was a problem hiding this comment.
This 2026-07-01 checkpoint also records 1.4.0 shipping Rust-plugin dead-code reachability roots and #80's plugin-anchor hardening, so the cycle did touch graph/extraction-adjacent surfaces. Carrying the north-star reading forward specifically because “no identity/extraction code touched” can mislead the next session into treating the 0-defect reading as validated after a release that changed the surfaces it measures; either re-sweep or state the real reason the reading is being carried without that claim.
Useful? React with 👍 / 👎.
| - `READING (2026-07-01): GREEN across the 1.4.0 release` (PDR-0009) — the | ||
| release verify gate + PRs #80 (P2 fixes), #83 (crates.io order), #84 (test | ||
| time-bomb) all passed (Rust + Rust aarch64 + Python + Sprint-1 e2e). Locally, | ||
| full-workspace `nextest` **1977 passed** with `WARDLINE_REPO=/home/john/wardline` |
There was a problem hiding this comment.
This adds the 1.4.0 release reading, but the same metrics file still scopes the identity-stability target to “stays 0 across the 1.3.x line”. Once 1.4.0 is published, that target no longer covers the released line, so SEI churn regressions in 1.4.x fall outside the documented guardrail; please retarget it to the current release line or mark the old target superseded.
Useful? React with 👍 / 👎.
| pushed on explicit owner say-so. **PyPI** (all 3 packages) + **GitHub Release** | ||
| (cosign/Rekor-verified) + **crates.io** (all 9 crates) now at 1.4.0. Local | ||
| `loomweave` reinstalled to 1.4.0 via uv. |
There was a problem hiding this comment.
This checkpoint declares PyPI and crates.io live for 1.4.0, but the operator getting-started guide still tells users that the current 1.x line deliberately does not publish to PyPI or crates.io (docs/operator/getting-started.md lines 107-109). After this release, following the user-facing install docs points operators away from the newly published channels and contradicts the release state; please update the install guidance as part of this checkpoint.
Useful? React with 👍 / 👎.
1 participant
Product-ownership CHECKPOINT for the 2026-07-01 session (docs-only,
docs/product/).New decision — PDR-0009: ship & publish loomweave 1.4.0 (owner-authorized in-session). Minor bump on 45 commits since 1.3.1; tag prepared-and-held, then pushed on explicit owner say-so; PyPI + GitHub Release + crates.io all at 1.4.0. Reversal trigger: a critical 1.4.0 regression → cut 1.4.1 (never re-push a published version).
Workspace refresh:
current-state.md/metrics.md— added the 1.4.0 CI-floor-green reading; folded open question 4b forward: the 2026-06-29 wardline-conformance drift was re-vendored via fix: restrict anchor_entity_id to trusted findings; re-vendor wardline taint golden #80 this cycle (drift cleared) but the local-red/CI-green blind spot itself is unfixed →clarion-72e1c1a07dpromotion stays open.roadmap.md/vision.md— untouched (no bet moved horizon, no strategy change; the Now field is still the three recorded candidates, DECIDE has not run).Concurrency — folds forward a stranded checkpoint. The prior owner-session checkpoint
1823911was committed to localmainbut never pushed (it diverged behind this session's release PRs). This branch cherry-picks it (preserving authorship) soorigin/maincarries both its 2026-06-29 delta and this 2026-07-01 delta; the stranded local1823911is now superseded and can be dropped on the owner's next reconcile.🤖 Generated with Claude Code