source: .forge/design/harness/file-size-progress.md · generated — edit the markdown, not this file

Source files over the size limit — progress

The project holds every source file in the app repos to 800 code lines (.forge/design/harness/file-size-check.md D-1: lines that still hold something once comments and blank lines are removed; D-2 says which files count). This file tracks every file over that limit, the work that splits it, what is done, and what is left. Each split is planned and reviewed through /forge-deliver, with no change in behaviour: F45 splits three backend classes, and F46 (.forge/specs/F46-split-files-over-size-limit-spec.md, since 2026-11-14) splits the other eleven.

Keeping it current. Update a row in the change that merges its split, and add a file the day it is found over the limit. Once an app repo’s file-size test is on main (design D-3, D-4), the list inside that test is the record for its repo, and this file points at it instead of copying it.

How the counts were taken. Each count is from the commit named in the column heading, counted as D-1 defines a code line: Java with a tokenizer that knows string and character literals, text blocks and comments; TypeScript with the TypeScript 5.9 scanner (typescript-classic), skipping comment trivia, leading and trailing (the counter in forge-et-fe’s src/app/fileSize.test.ts). The same counters reproduce the design’s 2026-11-12 figures exactly for every file.

Summary — 2026-11-14

Files
Over the limit on main or in an open PR, as found on 2026-11-12 14
Brought under the limit on main 0
In an open PR that brings them under the limit 3 (F45, forge-et-be#418)
Not started 11
Found over the limit since 2026-11-12 none

forge-et-pwa has no file over the limit (largest well under 100 code lines).

The files

Counts: 2026-11-12 from forge-et-be bb9fe28e and forge-et-fe 26e4cd42 (design § Context); “now” from forge-et-be 11bc8e41 and forge-et-fe 0f99a28f (origin/main, 2026-11-14).

# Repo File 2026-11-12 Now on main Split by State on 2026-11-14
1 forge-et-be mailbox/GraphMailboxProvider.java 1,960 1,960 F45 In PR: forge-et-be#418 (draft) takes it to 238. Waits for F20-i WI-5.1, the laptop walk, to record its backend commit (the lead’s decision of 2026-11-12, F45 tracker notes); then the PR is marked ready and merges, and F45 wave 2 checks the Graph split against the real mailbox
2 forge-et-be mailbox/LocalMailboxProvider.java 1,212 1,212 F45 In PR: forge-et-be#418 takes it to 713. Same wait as row 1
3 forge-et-be lead/service/LeadService.java 886 886 F45 In PR: forge-et-be#418 takes it to 174. Same wait as row 1
4 forge-et-be mailbox/LocalLiveMailbox.java 889 889 F46 Not started: F45 merged on 2026-11-20 (forge-et-be#418), so it can start from F45’s helpers
5 forge-et-be mailbox/service/EmailSendService.java 1,064 1,064 F46 Not started: F45, which changed the same mailbox package, merged on 2026-11-20 (forge-et-be#418). Open forge-et-be#424 (BUG-418) takes it to 1,066
6 forge-et-fe features/email/compose/ComposeEmailDialog.tsx 1,751 1,748 F46 Not started; can start now: forge-et-fe#493 merged on 2026-11-13, and no open PR changes the file
7 forge-et-fe features/accounts/AccountFormPage.tsx 1,151 1,170 F46 Not started; can start now, as row 6. Grew by 19 with forge-et-fe#493
8 forge-et-fe features/leads/LeadFormDialog.tsx 1,058 1,058 F46 Not started; can start now, as row 6
9 forge-et-fe features/attachments/RecordAttachmentsPanel.tsx 1,018 1,016 F46 Not started: after the CRM-screen split, so the same reviewers see one pattern (the lead’s order of 2026-11-12)
10 forge-et-fe features/activities/FollowUpEditBody.tsx 961 955 F46 Not started: after the CRM-screen split, as row 9
11 forge-et-fe features/accounts/AccountListScreen.tsx 852 933 F46 Not started: after the CRM-screen split, as row 9. Grew by 81 with F32-d (forge-et-fe#522, which carried #509 and #513)
12 forge-et-fe features/notesAndTags/RecordNotesSection.tsx 903 911 F46 Not started: after the CRM-screen split, as row 9. Grew by 8 with forge-et-fe#493
13 forge-et-fe features/leads/LeadNotesSection.tsx 489 857 F46 Not started: after the CRM-screen split, as row 9. Went over the limit with forge-et-fe#493 (merged 2026-11-13)
14 forge-et-fe features/email/templates/TemplateEditorForm.tsx 805 804 F46 Not started: after the CRM-screen split, as row 9

Near the limit — 701 to 800 code lines on 2026-11-14

Not over the limit, so nothing is owed on them; the reviewers flag new code added to them (design D-7’s 100-line margin).

Repo File Code lines
forge-et-be mailbox/StubMailboxSeed.java 706
forge-et-fe features/accounts/ContactFormFields.tsx 796
forge-et-fe features/email/EmailRoute.tsx 783 (763 on 2026-11-12)
forge-et-fe features/pricing/WeeklyPricesTab.tsx 776
forge-et-fe features/sharing/SharingPanel.tsx 765
forge-et-fe features/customFields/CustomFieldsSettingsRoute.tsx 755
forge-et-fe features/pricing/NotInRoundDialog.tsx 741
forge-et-fe features/accounts/AccountContactsPanel.tsx 705

F45 leaves LocalMailboxProvider.java at 713 (row 2), inside this band.

Open PRs, 2026-11-14

Every open PR in the three app repos was counted at its head, for the source files it changes. Only two touch a file over the limit, and none takes a new file over it:

  • forge-et-be#418 (F45 wave 1) brings rows 1 to 3 under the limit.
  • forge-et-be#424 (BUG-418) grows row 5, EmailSendService.java, from 1,064 to 1,066 code lines. Under design D-5 a fix in a listed file offsets its own growth. Nothing refuses it today, because the forge-et-be check is not on main; if the check merges first, #424 merges main in and takes 2 code lines out of the file before it merges (D-9).

Done

No file is under the limit on main yet.

Generated from .forge/design/harness/file-size-progress.md by .claude/lib/render-docs-html.js. Markdown is canonical.