Skip to content

chore: strip implementation comments and remove an orphaned API report - #59

Open
eordano wants to merge 1 commit into
mainfrom
reduce-tokens
Open

chore: strip implementation comments and remove an orphaned API report#59
eordano wants to merge 1 commit into
mainfrom
reduce-tokens

Conversation

@eordano

@eordano eordano commented Aug 3, 2026

Copy link
Copy Markdown
Member

Token-reduction pass

  • Remove implementation comments from 41 source and test files, and from pnpm-workspace.yaml and the two workflows. Public JSDoc on exported API is kept, since it reaches consumers through the emitted .d.ts, as are functional directives (eslint-disable and friends). Every file here is a comment-only change: re-running the strip over each file's previous revision reproduces the new contents byte-for-byte, so no behaviour is affected.
  • Delete libs/urn-resolver/etc/urn-resolver.api.md, an API Extractor report with no generator left in the repo. Nothing produces or checks it, so it was silently drifting stale.

Stripping the workflow comments removes the rationale for pinning actions by commit SHA, and stripping pnpm-workspace.yaml removes the explanation of why allowBuilds and publicHoistPattern list what they do. Both were verified to be comment-only with no behavioural effect, but that reasoning is now recorded nowhere.

Token-reduction pass, independent of the toolchain modernization.

- Remove implementation comments from 41 source and test files, and from
  pnpm-workspace.yaml and the two workflows. Public JSDoc on exported API is
  kept, since it reaches consumers through the emitted .d.ts, as are functional
  directives (eslint-disable and friends). Every file here is a comment-only
  change: re-running the strip over each file's previous revision reproduces the
  new contents byte-for-byte, so no behaviour is affected.
- Delete libs/urn-resolver/etc/urn-resolver.api.md, an API Extractor report with
  no generator left in the repo. Nothing produces or checks it, so it was
  silently drifting stale.

Stripping the workflow comments removes the rationale for pinning actions by
commit SHA, and stripping pnpm-workspace.yaml removes the explanation of why
allowBuilds and publicHoistPattern list what they do. Both were verified to be
comment-only with no behavioural effect, but that reasoning is now recorded
nowhere.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011Kio4QZqSB6LcjcjQbxWZy
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