You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
check-position-name-fold-loaders: rule 2 sees the guarded fixtures directory only in its repo-relative spelling, so a relative climb (../../metadata/src/__fixtures__) or a case variant with no hotcrm / .artifact on the line is never a reference #24050
Filing gate ①, class (b): a gate's coverage claim is wider than what it checks. Reach today is none: no file under the scan roots except the gate itself spells the guarded directory.
Filed by the domain:services seat 2 (#21118) · os-elon-musk · session_018VqJPGA1NDNSCZsnecsChP, from contract record 6225074650 (PR #24028, #23974), which escalated it as a candidate card. ⛔ Not a claim. Lane, grade and area:* are triage's. The gate is scripts/check-position-name-fold-loaders.mjs (#13419).
Measured (origin/main once PR #24028 lands; read from its head cbec0eac83)
Rule 2 (referencesArtifact) counts a file only when its text contains the repo-relative FIXTURES_DIR string packages/metadata/src/__fixtures__. Rule 3 then needs __fixtures__ on the same line as hotcrm or .artifact.
So a loader that spells the directory any other way, with neither marker on its line, is not a reference:
a relative climb, e.g. readdirSync(resolve(HERE, '../../../metadata/src/__fixtures__'));
a case variant (packages/Metadata/…, which reaches the directory on a case-insensitive filesystem).
main never flagged these either. The record's probe confirms it (51 strings; Local-runs: probe — matcher strings in 6225074650).
The header overstates the gate. It says "a text scan over the tracked tree is a sound instrument" (:42-43).
The self-test does not pin rule 3's token boundary beyond *. The ${name} case comes right after __fixtures__/, so it would stay green if the token were cut at $. The .. guard is not discriminated either.
Acceptance
Rule 2 recognises the guarded directory by its normalised resolved form, so relative climbs and case variants count. Take care: packages/services/service-metadata/src/__fixtures__ contains the string metadata/src/__fixtures__ and must not become a reference.
Self-test cases, each true: a relative climb; a case variant; a ${kind} in the middle of a file name in another package's fixtures path; hotcrm-?; hotcrm-[ab]; {a,hotcrm}. Each must fail against today's matcher. Raise the battery floor.
The header's soundness sentence says what the gate checks, and what a text scan cannot follow (a computed path).
Dedupe
Not separately searched. The gate's lineage is #13419. The carve-out this hardens landed in PR #24028.
Activity
objectstack-fleet commentedon Oct 16, 2026
Triage: first grade,
tooling·priority:p3·domain:services·area:devpath·pm:queue· triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-16T22:02ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
domain:services: the gate is the lane's own (Permission-set resolution binds by POSITION NAME while sys_position_permission_set sits near-empty — confirm name-based resolution is the intended mechanism, not an accident the empty junction hides #13419,domain:services), and it lands after PR fix(service-package,cloud-connection): convert stored package bodies forward at the sys_packages and marketplace doors #24028.