Daemon labels shadowed plugin approvals as unapproved after successful updates #441
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#441
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Partners independently reproduced on core v0.41.15 (
065c8864), with their database retained:Startup first says another digest is live and this approval stands, then counts the same old digests as
2 awaiting approval/unapproved=2and warns that they are not approved.plugin statuscorrectly identifies them as shadowed.PackageSet::unapproved()retains several diagnostic reason families, includingpackage_id_already_active. The startup count and generic warning incorrectly treat all rows as missing approvals. Preserve the reason-specific diagnostics and duplicate-id disclosure, but exclude shadowed approvals from the awaiting-approval count and generic not-approved warning.Separate observation, not a proven cause: E3 saw a 15.5-minute no-op scan over22,131 stat-skipped files with no progress line. This warning fix should not be presented as fixing scan performance.
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.v0.41.17 field confirmation from E4 (build
7da3598f; CLI/daemon/MCP/plugin-host match): all 10 exact approval rows retained; 8 active packages, 0 refused, 0 awaiting approval, 2 correctly diagnosed shadowed digests. The misleading generic approval warning is gone. The expected host-fingerprint rebuild completed in about 3.9 minutes with 0 parse errors and no file-contribution refusals; files/symbols and sampled Svelte outlines/reference counts match the previous release. No [update] entries were configured, and no background check was expected or observed.E4 separately reported a possibly undisclosed post-promotion resolution window (active generation visible before final reference counts). That is under investigation; it is not counted as fixed by this release.
Third v0.41.17 field confirmation, 16.0 (
7da3598f; all four binaries matched): active=8 refused=0 unapproved=0 shadowed=2, 0 awaiting approval, no generic not-approved WARN. Per-digest retained-approval diagnostics remain. Exact approval rows/digests and DB kept. C#/XAML private bOk_Click bridge and plain Name= controls unchanged; XAML call resolution 501/524 (95.6%), type 385/389 (99.0%). Only two expected partial template XAML sources. Generation 8 settled.