Flutter build/Dart AOT results (4) and Android manifest component and text
coverage (3) each spelled a local ["complete", "partial"] enum. They now
derive it from coverageStatusSchema without "unknown": every producer
derives "partial" from failures, caps or truncation it recorded, so its
coverage is always known. The Android parser's coverage parameter uses the
same type. Advertised schemas are unchanged. local-completeness-enum
-7.
* refactor(javascript): ask one owner whether opaque code changed an intrinsic global read
Six intrinsic global readers combined semanticOpaqueGlobalMayHaveChanged and semanticOpaqueNameMayHaveChanged themselves, each choosing which effect kinds applied and where to time them.
isIntrinsicGlobalReference and opaqueCodeMayChangeGlobalRead in javascriptSemanticGlobalReference.ts now own both proofs: a sloppy direct eval visible from the reference may introduce its root name, and global code that may run before the observation site may replace a writable global. The owner also knows that undefined, NaN and Infinity are non-writable, so global code cannot replace them. Map lookups and XMLHttpRequest open calls pass the call as the observation site, keeping their call-time timing. An architecture guard forbids the two helpers outside their owners.
Slice 1 of docs/adr/javascript/pushed-effect-invalidation.md (#11188).
* refactor(javascript): ask one owner whether opaque code rebound a binding (#11254)
Ten binding readers combined semanticBindingCanBeRebound, semanticBindingMayHaveOpaqueEffect and semanticOpaqueBindingReadMayHaveChanged themselves; three repeated the same rebindability-and-effect pairing.
opaqueCodeMayRebindBinding(binding, state, read?) and opaqueCodeMayReachBindingReference(binding, state, capturePoint) in javascriptSemanticOpaqueEffects.ts now own the rebinding, read-timing, capture and introduced-name proofs. semanticBindingMayHaveOpaqueEffect is private to the owner and semanticOpaqueBindingReadMayHaveChanged is removed, so a reader cannot pick effect kinds again.
Slice 2 of docs/adr/javascript/pushed-effect-invalidation.md (#11188).
* refactor(javascript): ask one owner whether an intrinsic instance method changed (#11266)
* refactor(javascript): ask one owner whether an intrinsic instance method changed
Map lookups and XMLHttpRequest.open each walked receiver aliases and combined
member-effect checks for the method, the instance prototype link and the
intrinsic prototypes. isIntrinsicInstanceMethodCall now owns that walk; Map
lookups also gain the prototype-link check XHR already made. The member-effect
view asks semanticOpaqueReferenceEffects for opaque sites instead of combining
the rebinding and reach helpers, which become private.
Refs docs/adr/javascript/pushed-effect-invalidation.md (slice 3).
* refactor(javascript): keep global opaque-effect checks private to their owner
opaqueCodeMayChangeGlobalRead moves into javascriptSemanticOpaqueEffects.ts, so
semanticOpaqueGlobalMayHaveChanged and semanticOpaqueNameMayHaveChanged are no
longer exported and the slice 1 text guard is replaced by the compiler.
* refactor(javascript): make the effect log the one reader of recorded opaque sites (#11282)
* refactor(javascript): make the effect log the one reader of recorded opaque sites
Rename javascriptSemanticOpaqueEffects.ts to javascriptSemanticEffectLog.ts
(ADR decision 1) and move the reference-effects view
(visitSemanticReferenceEffectsAtSite, the effect report, the member-path
query and its completeness gate) out of javascriptSemanticAnalysis.ts into it.
Recorded opaque sites move behind javascriptSemanticEffectRecord.ts accessors
(direct-eval site, recorded direct eval, global-code sites), which the timing
producer in javascriptSemanticMutationInitializers.ts and the call frontier in
javascriptSemanticCalls.ts now ask instead of reading state.opaqueEffects.
The member-mutation completeness WeakSet duplicated
state.memberMutationFactsComplete and is removed.
An architecture guard keeps `.opaqueEffects` reads inside the log and its
record module.
* refactor(javascript): keep the opaque reference-effect generator private to the effect log
* refactor(javascript): drop analysis-hub imports that only the moved effect queries used
* refactor(javascript): ask the effect log for a binding reference's recorded effects (#11295)
The value engine applied member writes, escapes and direct-eval reach to a
binding's reference itself, with its own capture proofs. That application
moves into javascriptSemanticEffectLog.ts as
applySemanticBindingReferenceEffects, and opaqueCodeMayReachBindingReference
becomes private to the log.
A counted guard (javascript-effect-index-read) records every remaining read
of the per-kind effect indexes outside the log; it can only shrink, so new
reader-side checks fail the guard.
* refactor(javascript): ask the effect log whether an ambient path may have changed (#11308)
* refactor(javascript): ask the effect log mayObserve for member-path reads (#11313)
* refactor(javascript): name the member-path effect query mayObserve
* refactor(javascript): ask the effect log whether an ambient path effect may precede a read
* refactor(javascript): ask the effect log about require and process rebinding (#11318)
refactor(javascript): ask the effect log about require and process rebinding and effect generations
* refactor(javascript): build the ambient-write module interop in one owner (#11323)
* refactor(javascript): build the ambient-write module interop in one owner and ask the effect log in CommonJS receivers
* refactor(javascript): ask the effect log whether binding assignments precede a read (#11329)
refactor(javascript): ask the effect log whether binding assignments or prototype writes precede a read
* fix(javascript): count prototype escapes before resolving a URL object request target (#11368)
fix(javascript): count URL and Object prototype escapes before resolving a URL object target
inspect_analysis_view and inspect_il2cpp_metadata wrote "--evidence-bundle"
and "--ghidra-seeds needs --binary" into their own input issues, copying
the CLI's option spelling into the service. They now name the field
(binary_path) or the input ("An Evidence bundle"), and the CLI's field
binding keeps owning option spellings.
A counted architecture guard records the 41 remaining REA CLI option
spellings outside src/cli (mostly "(CLI: --flag)" remediation hints) so
the list can only shrink.
* refactor(domain): charge the Interface Builder, NativeAOT, managed and runtime budgets through Budget
* test(browser): show a refused runtime retention charge leaves the room intact
* refactor(domain): charge the remaining fixed allowances through Budget (#11383)
* refactor(domain): charge CUDA metadata and SQLite reply budgets through Budget
CudaMetadataBudget (visits, section reads, temporary index) and the SQLite
OutputBudget kept hand-written allowances whose field names escaped the
budget-arithmetic guard; the SQLite reply budget also charged each part
before checking it. Both now charge Budget, which refuses an oversized
charge without changing the remainder.
The guard now also counts, inside any hand-written ...Budget class, a field
that is adjusted by hand and compared with < or >, whatever its name.
Unchecked tallies (a yield counter, a reservation ledger) stay uncounted.
Firmware arena cursors are write offsets, not allowances: they are renamed
#arenaWriteOffset and leave the guard's scope. Baseline 17 -> 15.
* refactor(domain): move cache, re-priced, checkpointed and ledger retention onto Budget
Budget gains chargeEvicting (evict the oldest cache entries until a charge
fits) and restore (refund everything charged since a used mark, never
re-charging). With them:
- the Bun metadata range cache evicts through chargeEvicting and charges
physical reads through a second Budget;
- Playwright scenario events refund an event's old cost and try-charge its
re-priced cost, and admission charges with tryCharge;
- WebNetworkProjectionAccumulator keeps one shared allowance plus retained
and temporary shares whose checkpoints restore by refunding;
- EvidenceLedger commits its admitted delta (charge, or refund when a
replacement shrinks) and clears with restore(0);
- the web bundle worker charges an admitted result, and on the completed-
snapshot path retains facts only when they still fit;
- the Pyc nested code walk charges steps and retained references.
budget-arithmetic 15 -> 4 (JavaScriptAnalysisWorker only).
* build(verify): declare the budget-arithmetic guard's counter for typed tests
Every counted-baseline change edited scripts/verify/architecture-guard-baselines.json, so PRs touching unrelated guards conflicted there. Each guard now keeps its baseline in scripts/verify/baselines/<guard-key>.json with paths sorted by code unit; --shrink-baselines rewrites, and deletes a guard's file when its last count is removed, and the guard rejects unsorted files and files that name no counted guard.