plugin add preview describes absent builtins as losing files and hides an explicitly disabled language #425

Closed
opened 2026-10-23 11:03:48 +02:00 by buildagent · 1 comment
Member

A1X field report from TimeLineE4 on CLI/daemon 0.41.12 (49068746), de.h-dv.javascript 0.1.3. Related to #423 but distinct from its missing prospective candidate.

The add preview says compiled-in javascript loses ext:cjs, ext:js, ext:jsx, ext:mjs, while languages list says no JavaScript builtin exists in the same production build. Static reserved-domain overlap is not evidence that a compiled-in producer is running.

The project has an explicit [languages] enabled list excluding JavaScript. There are 107 .js files, but approval activates a generation with zero JavaScript files. plugin add gives no clear warning that package approval does not enable that language. After the partner explicitly runs languages enable javascript, the daemon indexes 107 files and symbol count increases from101024 to103310. This is partner-reported evidence, not yet an independent reproduction of this exact configuration.

Required: show actual host availability/ownership separately from declared reserved-domain displacement; disclose explicit language exclusion and the supported enable action in the approval preview. Preserve operator intent: do not silently widen an explicit enabled list merely because --grant requested was supplied. Dirty-domain measurement must reflect effective configuration rather than promise indexing for an excluded language. Add no-default-features tests with an explicitly disabled first-party language and an enabled control.

A1X field report from TimeLineE4 on CLI/daemon 0.41.12 (49068746), de.h-dv.javascript 0.1.3. Related to #423 but distinct from its missing prospective candidate. The add preview says `compiled-in javascript loses ext:cjs, ext:js, ext:jsx, ext:mjs`, while `languages list` says no JavaScript builtin exists in the same production build. Static reserved-domain overlap is not evidence that a compiled-in producer is running. The project has an explicit `[languages] enabled` list excluding JavaScript. There are 107 .js files, but approval activates a generation with zero JavaScript files. `plugin add` gives no clear warning that package approval does not enable that language. After the partner explicitly runs `languages enable javascript`, the daemon indexes 107 files and symbol count increases from101024 to103310. This is partner-reported evidence, not yet an independent reproduction of this exact configuration. Required: show actual host availability/ownership separately from declared reserved-domain displacement; disclose explicit language exclusion and the supported enable action in the approval preview. Preserve operator intent: do not silently widen an explicit enabled list merely because `--grant requested` was supplied. Dirty-domain measurement must reflect effective configuration rather than promise indexing for an excluded language. Add no-default-features tests with an explicitly disabled first-party language and an enabled control.
Author
Member

Backlog reconciliation: this issue's requested preview/enablement fixes shipped in merged PR #426 and stable v0.41.13. That PR explicitly records Fixes #425 and the published parser-free proof: absent builtins are distinguished from reserved domains; an explicit language exclusion is disclosed and preserved; JavaScript emits greet only after the operator enables it. Closing the stale open entry. The separate genuinely-empty-index activation policy remains tracked in #427.

Backlog reconciliation: this issue's requested preview/enablement fixes shipped in merged PR #426 and stable v0.41.13. That PR explicitly records Fixes #425 and the published parser-free proof: absent builtins are distinguished from reserved domains; an explicit language exclusion is disclosed and preserved; JavaScript emits greet only after the operator enables it. Closing the stale open entry. The separate genuinely-empty-index activation policy remains tracked in #427.
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#425
No description provided.