fix(release): harden acceptance and qualify v0.41.19 #462
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!462
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/release-acceptance-hardening"
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?
The signed release acceptance could fail while repairing a missing embedded TypeScript producer because the daemon's cold-start approval writer briefly holds the project lease. The repair now retries only the explicit
plugin_mutation_busyrefusal within the original 180-second command deadline. Other errors, hung commands and persistent contention still fail. Runtime locking and every semantic repair assertion are unchanged. Fixes #461.Host version discovery now excludes the independently versioned package and frozen-fixture trees, matching the version-site registry. The execution regression preserves the exact worker provenance note, package version and frozen pin while moving the host version/archive rows. Fixes #460.
A permanent rollback regression deliberately forces SQLite to reuse the same file id for both an edited path and a replacement path. It checks actual reuse, preservation of the replacement's live facts, durable re-extraction for invalidated retained facts, and whole-tree equality with a cold index of current bytes. The existing path-based queue refresh handles both cases; no schema migration is required. Original multi-file regressions remain. Closes #321.
The freshness self-heal fixtures require a complete comparison within the shipped 250 ms probe deadline. Native Windows run6651 exhausted that budget beside the parallel suite before measuring a missing path. Both fixtures now run in the existing serial ci-timing lane and are registered as indirect bounds. The 250 ms deadline, one-comparison premise, exact counts, path/tree repair assertions and 30-second healing bound remain unchanged. Fixes #463.
Validation: 19 Python harness controls, 14 owner-switch/rollback tests, 9 version-site tests, strict affected-test Clippy, formatting and diff checks pass. The full signed generic release acceptance passes with all four locally built release-profile binaries. A real kernel-lease control produces three busy refusals, verifies unchanged approvals and readable status, then succeeds after release. The provenance test fails with the old bump script; disabling the existing queue path refresh makes the new rowid-reuse regression fail at the replacement's live-contribution check. Both freshness fixtures pass in the actual ci-timing profile (2 passed, 0 skipped), all 3 timing-registry checks pass, and affected-test Clippy passes. The registry is RED with the old profiles and GREEN with the corrected inclusion/exclusion. The corrected fixture uses the existing PACKAGE_TREES roots, with the live-package boundary allowlist unchanged. All 52 CI-routing checks, all 5 live-package boundary checks, the version-site checks and strict affected-test Clippy pass locally. All four normal workflows passed on exact head
9854283a: Windows 6659, core 6660, packages 6661 and pilots 6662. Windows passed 4846 ordinary tests and 35 timing tests; Linux passed 5073 ordinary tests and 45 timing tests, plus dedicated daemon transport and tier-1 corpus. All 11 package suites and all 11 package-corpus legs passed. Windows shipped-profile build checks passed. No force merge or CI waiver.The failed v0.41.18 tag is preserved and has no published release assets. This source head now carries 0.41.19. After its own full qualification and normal merge/tree/ancestry checks, tag this exact source head using docs/releasing.md's already-versioned-source path; no separate version PR is needed. The version-only guard deliberately refuses this source-containing commit, so qualification cannot be inherited or skipped.
Full signed generic release acceptance has now passed locally using all four freshly built, release-profile generic binaries (separate non-Wasm CLI/daemon/MCP build and Wasm plugin-host build). It covers signed package installs, real daemon MCP queries, embedded Svelte/Vue scripts, XAML bridges, watch/restart, Python layouts, bounded PHP mappings, missing-inner refusal and repair in the same DB, and no-native-fallback controls. Report: /tmp/cosi-461-generic-acceptance/report.json. All23 package CI jobs for this PR have also passed; the two scheduled-only jobs are correctly skipped. Core/Windows qualification remains in progress.
fix(release): handle approval contention and preserve package provenanceto fix(release): harden acceptance and qualify v0.41.19Released and independently verified: core v0.41.19, annotated on exact qualified source
9854283a; normal master mergee4752610 has the identical tree. Source workflows 6659–6662 and release 6667 all passed, including Windows archive smoke. The merge classifiers skipped duplicate core/Windows qualification.Independent checks of the published files:
Local receipts: /tmp/cosi-shipped-04119-final/bundle-verification.json; /tmp/cosi-04119-runtime-proof/report.json; /tmp/cosi-04119-python-importers-proof/dependencies.json; /tmp/cosi-04119-self-dogfood/report.json.
Removed three verified own merged/superseded remote branches using leases tied to the expected commit IDs and atomic deletion, plus their unused local branches/worktree and abandoned private Cargo output. Release tags and Claude WIP were retained. Remaining language gaps (#445/#447/#448) and the Windows post-summary delay (#435) remain open.