Context
docs/screens-map.md (RN ↔ Android screens mapping) was last touched on 2026-03-06 and no longer reflects the Compose tree.
Measured at head d888261 (PR #1200):
|
count |
*Screen.kt files in app/src/main/java |
155 |
listed in docs/screens-map.md |
92 |
| screens with no mapping entry |
68 |
| entries pointing at files that no longer exist |
5 |
Examples of stale entries: AboutScreen.kt, AdvancedSettingsScreen.kt, EditScreen.kt, GeneralSettingsScreen.kt, PubkyRingAuthScreen.kt.
Why it matters
Agent-driven reviews and design checks use this file to turn a changed Compose screen into a flow name (and, next, into the matching frame on the Bitkit - Handoff vNN Figma page). A stale map sends them to the wrong place or nowhere.
Proposed change
- Regenerate the table from the current
*Screen.kt set, grouped by feature package, and drop entries whose file is gone.
- Add a third column with the Figma flow or frame name for each screen (the handoff page frames are named per screen, e.g.
Transfer to Spending Confirm).
- Add a check (script or unit test) that fails when a
*Screen.kt is added or removed without a map entry, so the file cannot drift again.
- Mention the map and the Figma column in
AGENTS.md next to the existing Figma rule.
Context
docs/screens-map.md(RN ↔ Android screens mapping) was last touched on 2026-03-06 and no longer reflects the Compose tree.Measured at head
d888261(PR #1200):*Screen.ktfiles inapp/src/main/javadocs/screens-map.mdExamples of stale entries:
AboutScreen.kt,AdvancedSettingsScreen.kt,EditScreen.kt,GeneralSettingsScreen.kt,PubkyRingAuthScreen.kt.Why it matters
Agent-driven reviews and design checks use this file to turn a changed Compose screen into a flow name (and, next, into the matching frame on the
Bitkit - Handoff vNNFigma page). A stale map sends them to the wrong place or nowhere.Proposed change
*Screen.ktset, grouped by feature package, and drop entries whose file is gone.Transfer to Spending Confirm).*Screen.ktis added or removed without a map entry, so the file cannot drift again.AGENTS.mdnext to the existing Figma rule.