Close the launcher entry-guard item now that its fix has merged
Record-keeping only — no source changes.
pm-linear#63 merged the fix but left its
tracking item open. This closes it with the resolution fields the policy requires, and
regenerates the changelog afterwards (closing an item adds it to the release window, so the
regeneration has to follow the close rather than precede it).
What it records
isMainInvocation in the shared scripts/script-launcher.ts caught a realpathSync failure
and returned false. runIfMain reads false as "not the entry point", so the guarded
script never ran and npm run docstring exited 0 having scanned nothing.
This repository was missed by the original fleet sweep because the guard had been refactored
out of scripts/docstring-gate.ts into the shared launcher, which the gate only re-exports —
so a survey keyed on the gate's filename reported it clean.
The both-sides realpathSync comparison was retained: it normalises Windows drive-letter
casing, so only the catch was removed. CodeRabbit confirmed all three properties in review —
the dual-path normalization is unchanged, a different resolvable entry still returns false,
and the new test fails against the prior implementation.
pm items
- pm-linear-lonp — closed,
resolution: fixed
Summary by Sourcery
Document the launcher entry-guard fix in the changelog and close its associated PM tracking item.
Documentation:
- Add a changelog entry describing the launcher skipping guarded gates when a path could not be resolved.
Chores:
- Update and close the pm-linear-lonp tracking item with the required resolution metadata.
Summary by cubic
Closes the pm-linear-lonp tracking item now that PR #63 merged the shared launcher fix (unresolvable paths are propagated so gates can’t exit 0 without running). Regenerates the changelog to include the closed item in the current release window; no source changes.