Spend and budget range sentences live in one module, and the API and MCP read them from there #5575

The three spend and budget range sentences now live in one new file, src/actions/spend_words.ts, as a constant called SPEND_WORDS: usdPerMonth, ceilings and inviteDays. The API (src/http/api.ts) and MCP (src/http/mcp.ts) read them from there. No wording changed, so the answers are byte-for-byte the same.

What moved where

• src/http/api.ts: the four refusals are replaced — the invite days, the model grant and role usdPerMonth, and the account ceiling. One import line is added.
• src/http/mcp.ts: the four matching refusals are replaced — model_grant, mint_invite, account_role and model_ceiling. Each edit stays on the literal's own line, plus one import line, so the other MCP work editing this file in parallel should not conflict.
• test/spend-words.test.ts (new): each of the four refusals is triggered through the API and through MCP. The test checks the exact answer against SPEND_WORDS. A last test searches every .ts file under src/ and fails if any file other than the module types out one of the sentences. That is the issue's grep -rn check, run on every push.

Left alone: src/contract/openapi.ts describes the same rules with its own words (for example "days is not a whole number from 1 to 30 (422)"). These are documentation for the refusals, not the answers themselves, and they are worded differently, so they stay where they are.

How to check it: bun test test/spend-words.test.ts passes (5 tests). bun x tsc --noEmit is clean. The tests that cover these doors (mcp, mcp-invites, account-budget, model-grant-pages, member-others) all pass unchanged, 57 tests. Running grep -rn "from 0.01 to 10000 dollars" src shows the sentences only in spend_words.ts, apart from the differently worded openapi.ts lines above.

🤖 Generated with Claude Code

Closes #5559

The three spend and budget range sentences now live in one new file, src/actions/spend_words.ts, as a constant called SPEND_WORDS: usdPerMonth, ceilings and inviteDays. The API (src/http/api.ts) and MCP (src/http/mcp.ts) read them from there. No wording changed, so the answers are byte-for-byte the same.

What moved where

• src/http/api.ts: the four refusals are replaced — the invite days, the model grant and role usdPerMonth, and the account ceiling. One import line is added.
• src/http/mcp.ts: the four matching refusals are replaced — model_grant, mint_invite, account_role and model_ceiling. Each edit stays on the literal's own line, plus one import line, so the other MCP work editing this file in parallel should not conflict.
• test/spend-words.test.ts (new): each of the four refusals is triggered through the API and through MCP. The test checks the exact answer against SPEND_WORDS. A last test searches every .ts file under src/ and fails if any file other than the module types out one of the sentences. That is the issue's grep -rn check, run on every push.

Left alone: src/contract/openapi.ts describes the same rules with its own words (for example "days is not a whole number from 1 to 30 (422)"). These are documentation for the refusals, not the answers themselves, and they are worded differently, so they stay where they are.

How to check it: bun test test/spend-words.test.ts passes (5 tests). bun x tsc --noEmit is clean. The tests that cover these doors (mcp, mcp-invites, account-budget, model-grant-pages, member-others) all pass unchanged, 57 tests. Running grep -rn "from 0.01 to 10000 dollars" src shows the sentences only in spend_words.ts, apart from the differently worded openapi.ts lines above.

🤖 Generated with Claude Code