docs: track the scroll-FAB extraction plan and the hardcoded-strings audit - #486
Merged
RonenMars merged 1 commit intoAug 1, 2026
Merged
Conversation
…audit [skip-ci] Both existed only as untracked files in the working tree, so neither survived a fresh clone. The scroll-FAB plan covers the extraction that #476 deferred when the top-FAB overlay fix made the third copy converge on the other two, and no commit since has done it. `docs/superpowers/plans/` is where the repo already keeps active plans, so it goes there alongside the other fourteen. The audit inventories user-facing strings in `app/` and `components/` that are not routed through `react-i18next`. The i18n CI job enforces locale key parity rather than coverage, so nothing else in the repo records which strings are still hardcoded. Its line numbers will drift, but the inventory itself is still accurate — spot-checked against `components/ui/FAB.tsx` and `components/ui/AvatarMenu.tsx`. [skip-ci]
RonenMars
force-pushed
the
docs/scroll-fab-plan-and-i18n-audit
branch
from
August 1, 2026 15:24
ca105cc to
9268c5a
Compare
RonenMars
added a commit
that referenced
this pull request
Aug 1, 2026
…audit (#486) Both files existed only as untracked files in a working tree, so neither survived a fresh clone. The scroll-FAB plan covers the extraction that #476 deferred when the top-FAB overlay fix made the third copy converge on the other two, and no commit since has done it. `docs/superpowers/plans/` is where the repo already keeps its active plans. The audit inventories user-facing strings in `app/` and `components/` that are not routed through `react-i18next`. The i18n CI job enforces locale key parity rather than coverage, so nothing else in the repo records which strings are still hardcoded. Its line numbers will drift, but the inventory is still accurate — spot-checked against `components/ui/FAB.tsx` and `components/ui/AvatarMenu.tsx`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both files existed only as untracked files in a working tree, so neither survived a fresh clone.
docs/superpowers/plans/2026-08-01-extract-scroll-fab.mdcovers the extraction that #476 deferred, when the top-FAB overlay fix made the third copy converge on the other two.No commit since has done it, so the plan is still live, and
docs/superpowers/plans/is where this repo already keeps its fourteen active plans.docs/hardcoded-strings-audit.mdinventories user-facing strings inapp/andcomponents/that are not routed throughreact-i18next.The i18n CI job enforces locale key parity rather than coverage, so nothing else in the repo records which strings are still hardcoded.
Its line numbers will drift over time, but the inventory is still accurate — spot-checked against
components/ui/FAB.tsxandcomponents/ui/AvatarMenu.tsx, both of which still carry the hardcoded labels it lists.Documentation only, no code or config touched, so the commit carries
[skip-ci].