Fix plugin activation previews and live refusal reporting for v0.41.13 #426
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!426
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/svelte-activation-followup"
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?
plugin addcould preview zero dirty files for a newly fetched package because its bytes were not installed yet. CLI and MCP now include the verified in-memory candidate in the same grant and duplicate-version selection used for installed packages. The CLI activates the transition it previewed; declining still installs and approves nothing.Empty outlines and coverage now read refusals from the live contribution projection, so a cleared legacy file verdict cannot turn an extraction refusal into accepted empty facts. Pending/superseded refusals stay outside that projection; unreadable evidence stays unreported. The query retains its cached statement and file-index pin.
Confirmation text distinguishes reserved language domains from native extractors present in the build. It warns when the explicit enabled list excludes a reserved language and uses its public name in the enable command. Approval preserves the operator's list. Prepares core v0.41.13; signed package bytes, schema and SDK/ABI are unchanged.
Validation: workspace all-target Clippy with warnings denied; rustfmt; 15 activation/duplicate-version tests, 9 version-site checks, 14 CLI add tests, 4 displacement/enablement tests, package displacement and daemon verdict tests. MCP add/coverage tests pass on snapshot and daemon transports with their Rust healthy control, including CLI/elicitation parity and a nonzero candidate domain. Fresh parser-free four-binary proofs with published signed packages confirm: Svelte activates and emits App without a second index; a real live embedded refusal with NULL legacy parse_error reaches both tools; JavaScript stays disabled until explicitly enabled, then emits greet.
Fixes #423 and #425. Partially addresses #424 (honest disclosure only): generic-runtime embedded TS/JS extraction in Svelte/Vue remains open. The empty-index activation-policy edge found during validation is tracked in #427; its positive-control gate remains intact.
The independent signed-package replay caught a warning-name defect before merge: StoredPackage carries wire IDs, whereas the public enable command takes reserved row IDs. The follow-up commit maps through langid::row_lang and limits enablement warnings to languages the setting actually controls. The regression now checks that explicitly enabling
rubyremoves the warning for the same signed fixture.Both published-package proofs pass with the parser-free candidate: plain Svelte produces the App module immediately after add (no second index); JavaScript preserves its explicit disabled state on approval, prints the accepted public enable command, and produces greet after explicit enablement. A separate genuinely empty-index policy case is recorded as #427; the existing positive-control gate remains intact. Clippy for the correction passes. Merge must qualify the new PR head.