ledger: 0.22.0 ship cycle + first retroactive-closure pattern

[klappy]

What

Closeout ledger for the oddkit 0.22.0 ship cycle — two envelope-conformance bug fixes (PR #124 telemetry_public, PR #125 oddkit_catalog), their promotion cycle, and the first retroactive-closure pattern executed under the new release-validation-gate canon.

File: odd/ledger/2026-04-20-0-22-0-envelope-fixes-and-retroactive-closure.md

Why this ledger matters

This was the first post-canon application of klappy://canon/constraints/release-validation-gate (tier 1, landed earlier today via P1.3.3). All three rules applied end-to-end across 5 PRs; 4 Sonnet 4.6 validator dispatches + 1 post-merge follow-up smoke — all GO.

But one thing almost bent: operator sequencing put load-bearing code on prod via PR #127 before its dedicated full-pattern validator ran. The response was neither revert nor "wave it through" — it was retroactive closure via the next promotion PR's validator. This ledger names that pattern and gives future sessions the four criteria that make it legitimate:

1. Already-shipped code must be verifiable against live prod with concrete evidence (not inferred from review)
2. Retroactive smoke must perform the full P1.3.1 five-corroboration pattern, not a lighter touch
3. Gap must be named in the subsequent promotion PR body, validator brief, and closeout ledger
4. Retroactive corroborations must PASS — a FAIL escalates to revert, not accept

All four met; retroactive closure was valid. Future sessions now have the pattern documented if similar sequencing pressure creates a similar gap.

What the ledger captures

Standard P1.3.x structure:

• Summary — 4-paragraph narrative arc (what shipped, where the gap was, how it closed)
• Decisions (3) — batch into single 0.22.0, run the full gate, retroactive closure with criteria
• Observations (3) — bash-container rate-limit mid-session, pre-existing package-lock.json drift, operator out-of-sequence merge
• Learnings (4) — gate works when followed; feature-branch ≠ promotion validators; Managed Agents bypass orchestrator-IP throttle; version-bump chore as separate PR is the right shape
• Constraints (3) — PR canon: release-validation-gate + contract-governs-handoff-drift + bootstrap hook (P1.3.3 root-cause fix) #126 off-limits (other session), release-validation-gate binds every ship, bash egress assumed throttled
• Handoffs (5) — full-pattern on feat validators question, P11 (gate mechanical enforcement), regression-sweep open items (nonexistent_tool, doc-count drift), encode bug agent-skill v1.2.3: Canon refresh with ODD compliance #3 deferred, Version Sync CI may be missing root lockfile field (graduation signal)
• Encodes — DOLCHE summary, governance_source: knowledge_base, 18 artifacts
• Validation Evidence — every agent session ID, every validator verdict, post-merge observable closures
• Timeline — UTC log from regression-sweep start through post-merge verification
• Refs — canon docs, PRs, agent sessions, related ledgers

Writing canon gate

• ✅ Blockquote with compressed argument (retroactive-closure framing)
• ✅ Summary section
• ✅ Descriptive headers (Close the PR #127 gap retroactively via the PR #129 validator rather than reverting, not Decision 3)

Frontmatter

Validated locally: parses as valid YAML, all 4 required fields per canon-frontmatter CONTRACT (uri, title, tier, tags) present, types match canon/meta/frontmatter-schema (tier unquoted integer, dates unquoted, simple identifiers unquoted). audience: odd matches P1.3.1 and P1.3.2 convention (P1.3.3 used audience: ledger, which is non-schema).

Refs

• fix(telemetry_public): add server_time + full envelope to match tool convention oddkit#124, canon: graduate cache-fetches-and-parses to tier-2 principle (P1.3.3 Phase 1) #125, ledger: P1.3.3 closeout — challenge canon-parity landed (incl. process failure post-mortem); supersede predecessor handoff #127, handoff: P1.3.4 encode canon-parity refactor (D5 + D9) — closes the sweep #128, canon: envelope-time-fields principle (tier-2 draft) #129 (all merged; prod at 0.22.0)
• klappy://canon/constraints/release-validation-gate (tier 1)
• klappy://odd/ledger/2026-04-20-p1-3-3-challenge-canon-parity-landed (parent — landed the canon this session applied)
• klappy://odd/ledger/2026-04-20-p1-3-1-challenge-canary-landed (source of the 5-corroboration pattern)

---

Note

Low Risk
Documentation-only change adding a new session ledger; no runtime code, config, or dependency changes.

Overview
Adds a new session ledger, odd/ledger/2026-04-20-0-22-0-envelope-fixes-and-retroactive-closure.md, documenting the 0.22.0 release cycle (envelope fixes in telemetry_public and oddkit_catalog) and the first retroactive-closure approach used to close an under-corroborated promotion under the release-validation-gate canon.

Captures the decision criteria for when retroactive validation is acceptable, plus the associated validation evidence, timeline, and operational notes (e.g., Cloudflare egress throttling and version-sync drift signal) for future sessions.

^{Reviewed by Cursor Bugbot for commit 9edd383. Bugbot is set up for automated code reviews on this repo. Configure here.}