Release 0.41.12: stable extraction identity, recovery and CI qualification #420
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!420
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/release-0.41.12"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Core upgrades currently invalidate extraction based on release/build labels, long successful startup can exhaust the idle window, and recovery can reject a daemon that becomes ready just after re-attach fails. This release separates extraction compatibility from release labels, hashes effective grants consistently, resets the idle window after successful startup/reactivation, rechecks a starting owner with an authenticated identity handshake, and excludes exited Linux zombies from live owners. Existing reconnect/tool budgets, foreign-root refusal and protection against duplicate daemons remain enforced.
CI qualification now falls back from the newest 150 global task rows to commit-filtered run/job evidence and discovers identical-tree parents directly from Git. Newer failures and pending work, rerun ordering, malformed metadata and API failures still block qualification. Semantic readiness/resource-accounting and bounded-freshness tests are corrected without changing production time budgets.
Exact head
490687462d5dc337d3ba8e70dc2ed296e328c9a7passed all four normal required workflows:This head contains master and already carries 0.41.12, allowing a normal fast-forward-only PR merge and a tag on the actual fully qualified source. The annotated notes must pass the real release-notes script before pushing. The failed, unpublished v0.41.11 tag remains unchanged.
Entering the new extraction/activation identity contract requires one conservative migration rebuild. Schema 88, fact ABI 1.4, guest ABI 2, SDK versions and signed language-package bytes remain unchanged. Package-upgrade recovery #410 and cache backend/reuse #408 remain open.
Closes #421.
Closes #422.
Release code-index 0.41.12 with validated tag notesto Preserve CI qualification history and prepare code-index 0.41.12Preserve CI qualification history and prepare code-index 0.41.12to Release 0.41.12: stable extraction identity, recovery and CI qualification