Two Luxon issues — registered instrumentation

Registered before these solver and review calls. Two previously unattempted open Luxon issues, complete discussion snapshots, fixed checks and randomized paired order are bound by the manifest, SHA-256 e86aa0178042f3070f312e37ed3d66b6034751485857d8815ce8e69f38bf403c. Selection followed prior outcomes; these two issues share a project and the separate registrations are not an independent 30–50-task cohort.

Issue	Frozen acceptance	Source-only reference
#1366	An unsupported requested locale falls back to Luxon’s configured French default for two UTC dates; valid English and ordinary date controls remain valid.	PR #1800
#1189	With Intl.ListFormat absent, two multi-unit durations render with a comma fallback; ordinary date and duration operations remain valid when it is available.	PR #1585

The qualification ledger records baseline failures and source-reference passes for public and acceptance checks, with controls passing on both. These are partial checks, not full upstream tests or maintainer acceptance. Node module hooks load the pinned source without npm dependencies; this is not the published build. Public comments and PRs can disclose solutions or appear in training.

The VM, paired randomization, tools, rubric, model budgets and logged 503-only retries follow the validator registration. No timeout is retried; provider failure or missing usage stops each stage. The registered adjudicator has the same model name as the solver, selected after earlier failures, and is not independent. All AI names share one proxy with unverified provenance. Estimated model-call target is below $1, not a hard cap. Short seeded issue discussions do not establish production effects, savings or autonomous memory management.