plugin add omits a newly fetched candidate from its dirty-domain preview and activation plan #423

Closed
opened 2026-10-23 10:52:51 +02:00 by buildagent · 0 comments
Member

Reported via A1X by the TimeLineE4 partner on official core/daemon 0.41.12 (49068746), independently reproduced with the published Linux binaries and official signed Svelte 0.2.0 (sha256:8eedf0104a0b34082f28e04b7f6f2d994708f13a768ff5f61c982d3eb1c8f7b7).

Reproduction: index an isolated root containing App.svelte, then run plugin add de.h-dv.svelte --yes --grant requested in a fresh operator home against the signed channel. It reports reindex_domain 0 of 1 walked files (reparse 0, reresolve 0, CHANGING HANDS 0) and finally NOTHING TO BUILD.

Source witness: cmd_add computes domain_between(root, db, &store, &record, &next) before the approval and before Store::install. domain_between resolves the prospective record only through the current store, so the new candidate's bytes/claims are absent. The same planned activations feed execution. A preview must include the already verified in-memory candidate without installing or running it before consent, and must retain duplicate-package-id selection and effective-grant rules.

The partner's original 'no reparse' conclusion was too broad: later contribution rows prove its daemon did attempt embedded extraction. This issue is specifically the directly reproduced preview/planned-activation defect; do not infer that no subsequent startup path can reparse. A fresh one-shot index reparsed the local fixture, then hit the separately reproduced embedded-dispatch failure.

Add a regression using a package not already present in the store and a previously text-only file. Require the expected dirty domain, change-of-owner count, actual successful module extraction, no pre-consent store/DB mutations, and duplicate-id controls. Local reproduction artifacts: /tmp/cosi-svelte-04112-repro.

Reported via A1X by the TimeLineE4 partner on official core/daemon 0.41.12 (49068746), independently reproduced with the published Linux binaries and official signed Svelte 0.2.0 (sha256:8eedf0104a0b34082f28e04b7f6f2d994708f13a768ff5f61c982d3eb1c8f7b7). Reproduction: index an isolated root containing App.svelte, then run `plugin add de.h-dv.svelte --yes --grant requested` in a fresh operator home against the signed channel. It reports `reindex_domain 0 of 1 walked files (reparse 0, reresolve 0, CHANGING HANDS 0)` and finally `NOTHING TO BUILD`. Source witness: `cmd_add` computes `domain_between(root, db, &store, &record, &next)` before the approval and before `Store::install`. `domain_between` resolves the prospective record only through the current store, so the new candidate's bytes/claims are absent. The same planned activations feed execution. A preview must include the already verified in-memory candidate without installing or running it before consent, and must retain duplicate-package-id selection and effective-grant rules. The partner's original 'no reparse' conclusion was too broad: later contribution rows prove its daemon did attempt embedded extraction. This issue is specifically the directly reproduced preview/planned-activation defect; do not infer that no subsequent startup path can reparse. A fresh one-shot index reparsed the local fixture, then hit the separately reproduced embedded-dispatch failure. Add a regression using a package not already present in the store and a previously text-only file. Require the expected dirty domain, change-of-owner count, actual successful module extraction, no pre-consent store/DB mutations, and duplicate-id controls. Local reproduction artifacts: /tmp/cosi-svelte-04112-repro.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index#423
No description provided.