Every asset reads like a person wrote it: '1 bedroom', no 'Condo, no lot lot', 'an 1890s home', in every tone #30

Every asset, in every tone, now says "1 bedroom", drops a lot that isn't a measurement, and picks "a" or "an" to fit the next word. bun x tsc --noEmit did not run, because the repo has no tsconfig.json and the installed tsc only printed its help. The forge's check will be the first type check. The design check is scripts/lint-design.ts here, not design-lint.ts, and it printed nothing.

I ran generate, fairhousing, hostile, pages, sample, listings, walkthrough and server tests (70 tests). They pass, including the new ones.

What changed, all in src/generate.ts unless noted

• Singular: the MLS description, all three social posts, the flyer and the email say "1 bedroom", "1 bath" and "1 bed" for exactly one. 1.5 stays "1.5 baths".
• Lot: a lot with no digit in it ("Condo, no lot", "n/a", "none", "—") is left out of the sentence, so "Built in 2016 on a Condo, no lot lot" becomes "Built in 2016". A lot like "0.18 acre" reads as before.
• Article: it follows the next word, as in "An 1890 home", "an 8,000 sq ft lot" and "a 2004 home". It also applies to "a 1-bedroom" versus "an 8-bedroom" in the classic MLS text.
• Fact strips: one helper, factItems, sits next to factsLine. The flyer's flyer-facts list (src/pages/listing.ts) and the email's email-facts line (src/pages/email.ts) both call it. factsLine also leaves the lot out when it isn't a measurement.
• Home card: I left it alone. It never showed a lot, and "1 bd" is already correct.
• Tests: src/generate.test.ts generates every tone for the 1 bed / 1 bath condo, a 4 bed / 2.5 bath house built 1890 on "0.31 acre", an 8-bedroom 8,000 sq ft case, and each shipped sample. It asserts none of the forbidden patterns appear in any asset. A second test pins the wording, the article and the strips. I didn't run these against main, so "fails on main" is unchecked.

Not done: validate in src/listing.ts and the form are untouched, so the lot is still a required free-text field. No existing listing is rewritten. I didn't change contract.json or any permission.

Shipped samples: on a fresh FORGE_APP_DATA the condo sample ("Condo, no lot") now generates without the lot. The Alder Lane house and the 0.31 acre house are unchanged apart from the article rule. Samples are only written by the existing seed path, so a database that already has them keeps its old text.

To try it, launch a listing with 1 bed, 1 bath and lot "Condo, no lot", then read the MLS tab, the flyer and the email.

🤖 Generated with Claude Code

Closes #29

Every asset, in every tone, now says "1 bedroom", drops a lot that isn't a measurement, and picks "a" or "an" to fit the next word. bun x tsc --noEmit did not run, because the repo has no tsconfig.json and the installed tsc only printed its help. The forge's check will be the first type check. The design check is scripts/lint-design.ts here, not design-lint.ts, and it printed nothing.

I ran generate, fairhousing, hostile, pages, sample, listings, walkthrough and server tests (70 tests). They pass, including the new ones.

What changed, all in src/generate.ts unless noted

• Singular: the MLS description, all three social posts, the flyer and the email say "1 bedroom", "1 bath" and "1 bed" for exactly one. 1.5 stays "1.5 baths".
• Lot: a lot with no digit in it ("Condo, no lot", "n/a", "none", "—") is left out of the sentence, so "Built in 2016 on a Condo, no lot lot" becomes "Built in 2016". A lot like "0.18 acre" reads as before.
• Article: it follows the next word, as in "An 1890 home", "an 8,000 sq ft lot" and "a 2004 home". It also applies to "a 1-bedroom" versus "an 8-bedroom" in the classic MLS text.
• Fact strips: one helper, factItems, sits next to factsLine. The flyer's flyer-facts list (src/pages/listing.ts) and the email's email-facts line (src/pages/email.ts) both call it. factsLine also leaves the lot out when it isn't a measurement.
• Home card: I left it alone. It never showed a lot, and "1 bd" is already correct.
• Tests: src/generate.test.ts generates every tone for the 1 bed / 1 bath condo, a 4 bed / 2.5 bath house built 1890 on "0.31 acre", an 8-bedroom 8,000 sq ft case, and each shipped sample. It asserts none of the forbidden patterns appear in any asset. A second test pins the wording, the article and the strips. I didn't run these against main, so "fails on main" is unchecked.

Not done: validate in src/listing.ts and the form are untouched, so the lot is still a required free-text field. No existing listing is rewritten. I didn't change contract.json or any permission.

Shipped samples: on a fresh FORGE_APP_DATA the condo sample ("Condo, no lot") now generates without the lot. The Alder Lane house and the 0.31 acre house are unchanged apart from the article rule. Samples are only written by the existing seed path, so a database that already has them keeps its old text.

To try it, launch a listing with 1 bed, 1 bath and lot "Condo, no lot", then read the MLS tab, the flyer and the email.

🤖 Generated with Claude Code

Both changes are in and pushed. The tests pass: generate, tty, pages, fairhousing and hostile (39 tests). bun x tsc --noEmit still can't run here, because the repo has no tsconfig.json. scripts/lint-design.ts printed nothing.

• Terminal: the email preview in src/tty.ts now builds its fact line with factItems, the same helper the page uses. A 1-bed condo with lot "Condo, no lot" reads "1 bed · 1 bath · 2,140 sq ft · 1928 built", with no lot item. A new test in src/tty.test.ts checks that line and asserts there is no "lot lot", no "Condo, no lot" and no "1 beds".
• article(): a four-digit number counts as a year only when it has no comma. "1,800 sq ft" and "1,150 sq ft" now take "a", while 18,000 and 8,000 still take "an". An 1890 year still gets "An 1890 home". src/generate.test.ts now asserts "a 1,800 sq ft lot", "a 1,150 sq ft lot" and "an 18,000 sq ft lot".
• Fails without the change: I stashed the src/generate.ts and src/tty.ts changes and re-ran. Both the singular/lot/article test and the new terminal test fail on the old code. Without those two source changes, the src/generate.test.ts assertions for the singular, the dropped lot and the article all fail. I only ran the new tests that way, not the full suite.

There is no contract.json change, no new dependency, and the page output is still escaped.

🤖 Generated with Claude Code