docs(wiki): sweep stale .js filenames now that the tree is all-TypeScript
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- documentation
Research direction
Review .wiki/Architecture.md, .wiki/Development-Workflow.md, .wiki/Source-Map.md, and .wiki/Product-and-Features.md, then compare every referenced path with the current TypeScript tree. Verify each filename individually because modules may have been split or renamed; done means all stale references are corrected without blanket-renaming valid paths.
Written by the indexing model from the issue text.
Description
Found during the 2026-08-03 wiki in-repo migration (commit 5cd3f22), deferred as out of scope for that reconciliation pass.
.wiki/Architecture.md, .wiki/Development-Workflow.md, .wiki/Source-Map.md, and .wiki/Product-and-Features.md still reference .js filenames (main.js, app.js, state.js, ch-client.js, …) although the hand-written tree has been all-.ts since ADR-0002 completed (#267). Needs a path-by-path audit of every file reference in those four pages against the current tree — a mechanical sweep, but each path should be verified rather than blanket-renamed (some modules were also split or renamed since the pages were written).
Why deferred: the migration pass only reconciled claims that were made false by ADR-0004 / the 2026-08-03 main reset; filename staleness predates both.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 2
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Altinity/altinity-sql-browser
-
inbox
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Altinity/altinity-sql-browser#605 ·
-
inbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Altinity/altinity-sql-browser#509 ·
-
inbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Altinity/altinity-sql-browser#489 ·
-
flamegraph Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Altinity/altinity-sql-browser#684 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Altinity/altinity-sql-browser#680 · 2 comments ·
All issues in Altinity/altinity-sql-browser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·