feat: check configured plugin updates after daemon readiness #443
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!443
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/plugin-update-automation"
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?
Projects with
[update."<id>"]policies currently need a manual command, and configured registry updates can read an embedded catalog that cannot discover later releases. The daemon now invokes the matching sibling CLI updater after readiness and daily while running, with a durable per-project 24-hour cooldown. Its existing signature, publisher, grant, semver, withdrawal, conformance, extraction-cost and activation checks govern every apply. False remains check-only, and no prompt is answered. Detailed logs stay in the operator store.Fixes #442. Also fixes #441: shadowed approvals remain visible in duplicate/reason diagnostics but no longer count as awaiting approval or receive the generic unapproved startup warning. No new dependencies, configuration keys, MCP schema or workflow changes.
Local validation passed 75 affected CLI tests (38 registry, 21 configured-update, 16 named-update), two updater state tests, two real-store duplicate-disclosure tests, and all 17 bound-registry tests. Real-daemon cases wait for the new digest in the ACTIVE generation, preserve exact approvals in check-only mode, verify offline signed-channel reporting, and cover restart cooldown. Strict all-target Clippy, formatting, whitespace checks and code-index review completed; subprocess/store regressions supply evidence where the resolved graph has low coverage.
CI caught an inline checkpoint bound in the first head. Corrected source
21ab63bfnames and registersMAX_UPDATE_STATE_BYTESand refuses oversized checkpoints whole. The first head is superseded; the comment records its failed gate. Normal core, Windows, package and pilot qualification applies to the corrected head.The separately qualified v0.41.16 concurrency hotfix has completed publication. This PR targets the next core release; package versions and ABI remain unchanged.
CI caught a repository-wide bound-registration defect in source
c31782bd:.take(64)on the private updater checkpoint used an inline limit. Linux workspace ran5,063 tests:5,062 passed and this gate failed; native Windows reports the same gate failure. This head is not qualified and will not be merged.Correction names
MAX_UPDATE_STATE_BYTES, registers the framing bound with its disclosure decision, and refuses an oversized checkpoint whole instead of trusting a truncated timestamp. The existing cooldown test now includes the oversized-checkpoint case. The completebounding_site_registrysuite passes locally (17 tests); normal source qualification will run on the corrected head. No gate, assertion, retry policy or workflow is weakened.Corrected source
21ab63bfpassed all normal workflows: Windows 6569, core 6570, packages 6571 and pilots 6572. Linux workspace/timing summaries are 5,063/5,063 and 44/44 passed; native Windows workspace is 4,841/4,841, followed by all native profile/smoke gates. Normal merge isac1e3d2f61a9b4643a3b9000ed712d660f82d9c7, with treeef3b7eadc101799778c9fb541bbed0d7bcc91368identical to the qualified head, which is a merged ancestor.Version-only release PR #444 starts directly from that qualified head. It passes the four-site version-only proof. Publication will follow the normal version checks/merge, classifier proof, annotated tag validation and independent published-binary verification. The release notes disclose the conservative host-fingerprint/startup rebuild cost; the previous .16 no-rebuild receipt is not generalized to this source update.
Stable v0.41.17 is released and independently verified. All normal source/version/release gates passed, plus published-artifact signatures/hashes, .16→.17 upgrade/concurrency checks, the native daemon's configured background update check, and self-dogfood. Full receipt: #442 (comment)
The host-source fingerprint changes and may require a startup activation rebuild. Existing databases and approvals are retained. Independent package checks follow existing
[update]policies; this release adds no manual MCP updater tool.