Skip to content

chore(lint): satisfy no-shop-metaphor-jargon across main - #226

Closed
John-David Dalton (jdalton) wants to merge 2 commits into
mainfrom
chore/jargon-sweep
Closed

chore(lint): satisfy no-shop-metaphor-jargon across main#226
John-David Dalton (jdalton) wants to merge 2 commits into
mainfrom
chore/jargon-sweep

Conversation

@jdalton

Copy link
Copy Markdown
Collaborator

The no-shop-metaphor-jargon rule landed ahead of the repo — whole-repo lint (and therefore every PR's Check gate, including #225's) failed on 44 pre-existing sites. This sweep fixes them contextually, comment-only:

  • seaminjection point where the comment means a DI/test injection (spawn injection point, test injection path, injectable launch point, test-seam)
  • seamboundary where it means a plain architecture boundary (factory boundary, streaming boundary, node:http boundary, describe boundaries)
  • seams (plural, naming pure helper modules) → helpers
  • wedgedunresponsive (3 sites)

Verification: socket lint error count 0, whole-repo pre-push lint green. Unit tests: the git temp-repo suites are flaky on this machine — extended-real-ops's 'temporary git repository' fails intermittently on pristine main too (1 failure both with and without this change); all other suites pass.

Contextual rewrites at all 44 sites: 'seam' becomes 'injection point'
where the comment means a DI/test injection (spawn injection point,
test injection path, injectable launch point) and 'boundary' where it
means a plain architecture boundary (factory boundary, streaming
boundary, node:http boundary); 'wedged' becomes 'unresponsive';
the plural 'seams' naming pure helper modules becomes 'helpers'.
Comment-only — no behavior changes.

The git temp-repo suites are flaky on this machine
(extended-real-ops 'temporary git repository' fails intermittently on
pristine main too); every other suite passes, and the socket lint
error count is 0.
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH: the lockfile's catalogs block drifted
from pnpm-workspace.yaml's catalog config (broken on main — every recent
CI run fails the frozen install in setup-and-install). Regenerated with
pnpm install --no-frozen-lockfile; the workspace yaml and .gitignore are
untouched. The catalog entries refresh within their declared ranges;
pnpm install --frozen-lockfile now passes.
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​types/​node@​26.2.01001008196100
Addednpm/​typebox@​1.3.111001009996100
Addednpm/​taze@​20.0.09810010097100
Addednpm/​@​playwright/​mcp@​0.0.7910010010099100

View full report

@socket-security-staging

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​types/​node@​26.2.01001008196100
Addednpm/​typebox@​1.3.111001009996100
Addednpm/​taze@​20.0.09910010097100
Addednpm/​@​playwright/​mcp@​0.0.7910010010099100

View full report

@jdalton

Copy link
Copy Markdown
Collaborator Author

Closing unmerged: fleet members land changes directly to main; both commits (jargon sweep + lockfile realign) are being landed there instead of via PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant