A new issue's and pull's length limits live in one module, read by both forms #5605

The "too long" messages for a new issue's or pull's title and description now come from one new module, src/actions/thread_limits_words.ts. It exports TITLE_TOO_LONG ("That title is too long (256 characters at most).") and BODY_TOO_LONG ("That description is too long (64 KB at most)."). No module already held words like these, so it is new.

• Issue form: src/web/pages/issues.ts imports both constants and uses them in place of the typed sentences when an issue fails to open.
• Pull form: src/web/pages/pulls.ts uses them for the title_too_long and body_too_long entries in COMPOSE_ERRORS.

Only the import line and the sentence lines changed in each file, and no wording changed. grep -rn for each full sentence under src/ now finds only the new module.

Left alone on purpose: two similar messages aren't in the issue's list, so they stay where they are:

• thread.ts says "That description is too long." with no limit in it.
• reports.ts builds its title message from TITLE_MAX and adds "The report is still waiting."

Test: the new test/thread-limits-words.test.ts checks that each exported sentence is a non-empty string. It also reads both page files as text and fails if they stop importing the module or if either sentence is typed back in.

Checks run, all passing: the new test, bun x tsc --noEmit, bun scripts/design-lint.ts, and test/issues.test.ts, test/pulls.test.ts, test/new-pull-timing.test.ts, test/issue-timing.test.ts and test/edit-words.test.ts. No existing test was changed.

To try it, open a new issue or pull with a title over 256 characters: the form comes back with the same sentence as before.

🤖 Generated with Claude Code

Closes #5587

The "too long" messages for a new issue's or pull's title and description now come from one new module, src/actions/thread_limits_words.ts. It exports TITLE_TOO_LONG ("That title is too long (256 characters at most).") and BODY_TOO_LONG ("That description is too long (64 KB at most)."). No module already held words like these, so it is new.

• Issue form: src/web/pages/issues.ts imports both constants and uses them in place of the typed sentences when an issue fails to open.
• Pull form: src/web/pages/pulls.ts uses them for the title_too_long and body_too_long entries in COMPOSE_ERRORS.

Only the import line and the sentence lines changed in each file, and no wording changed. grep -rn for each full sentence under src/ now finds only the new module.

Left alone on purpose: two similar messages aren't in the issue's list, so they stay where they are:

• thread.ts says "That description is too long." with no limit in it.
• reports.ts builds its title message from TITLE_MAX and adds "The report is still waiting."

Test: the new test/thread-limits-words.test.ts checks that each exported sentence is a non-empty string. It also reads both page files as text and fails if they stop importing the module or if either sentence is typed back in.

Checks run, all passing: the new test, bun x tsc --noEmit, bun scripts/design-lint.ts, and test/issues.test.ts, test/pulls.test.ts, test/new-pull-timing.test.ts, test/issue-timing.test.ts and test/edit-words.test.ts. No existing test was changed.

To try it, open a new issue or pull with a title over 256 characters: the form comes back with the same sentence as before.

🤖 Generated with Claude Code

The length limits for a new issue and a new pull now live in one module, src/actions/thread_limits_words.ts, which exports TITLE_TOO_LONG and BODY_TOO_LONG. Both src/web/pages/issues.ts and src/web/pages/pulls.ts read their messages from it instead of each keeping its own copy, so the two forms can't drift apart. test/thread-limits-words.test.ts covers it, and behaviour is unchanged.

This branch now has main merged in. The one conflict was the import block of src/web/pages/issues.ts: main had added an import of COMMENT_EMPTY and COMMENT_NOT_POSTED from comment_words.ts, and this branch had added the thread_limits_words.ts import. Both are kept, because the page uses all four. After the merge the type check is clean, the limits and issue/comment tests pass (78 of 78), and the design lint is clean.

To try it, open "new issue" or "new pull" on any repository and submit a title or body over the limit: both forms show the same message.

🤖 Generated with Claude Code