Mark a listing under contract or sold, and write the 'Just sold' post and email from it #45

A listing can now be marked Active, Under contract or Sold (with an optional sold price). Under contract and Sold add a status post and a status email. I pushed the change, and bun test passes (171 tests). I could not run tsc --noEmit here because the repo has no tsconfig.json, so types are unchecked.

What changed

• Status and price: a listing has a status and an optional sold price. A migration adds both columns, and validateStatus in src/listing.ts checks them. A sold price is accepted only with Sold, in whole dollars from $1,000.
• One action, four doors: setStatus in src/actions.ts asks permit for the listing's update cell, so only the author or an admin may change it. It is audited, and no cell in contract.json changed. It is reached from:

- the listing page: a status box and price field with a "Set status" button, - the API: PATCH /api/listings/:id with {status, sold_price}, - the MCP: a new set_status tool, - the terminal: the s key, typing sold 752000, under contract or active.

• New assets: there are two new kinds, social_status (a Social tab post) and email_status (an Email tab email, subject "Just sold — 412 Alder Lane"). They are written in the listing's tone, Fair Housing checked, and each needs its own approval.
• Approval counts: the total is counted from the stored assets, so it reads "0 of 8 approved" once a listing is announced and "of 6" when active.
• Existing assets untouched: setting the status writes only the two status assets, so your edits and approvals on the other six stay. Saying what is already true changes nothing. Changing the sold price rewrites the announcement and clears its approval. A retone or "Edit facts" rewrites everything, status assets included.
• Pill and band: the home list and listing head show a status pill beside the approval pill when the status isn't Active. The flyer gets a "Sold at $…" or "Under contract" band, and its badge reads "Just sold" or "Under contract" instead of "Just listed". The new CSS classes are named in docs/design/areas/status.md.
• Sample: 88 Meridian Street (the condo) is seeded as Sold at $752,000.
• Tests and docs: src/status.test.ts covers validation, the words in every tone, the approvals and counts, who may change it, the band, the sample, and the MCP, terminal, API and page doors. The walkthrough has a new "Mark it sold" step with a matching README step. The README, contract/openapi.json and the existing tests that assumed six kinds are updated.

Choices to check

• I made the condo the Sold sample rather than 412 Alder Lane (the issue's example subject), because Alder Lane's open-house sample and its walkthrough steps depend on it staying live.
• The two status assets are labelled "Status post" and "Status email" in the editor, whatever the status.
• I did not add status to the launch form: a listing always launches Active.
• Open houses are not mentioned in the status assets.

To try it Open any listing you own, pick Sold with a price, press "Set status", and approve the two new assets. Or run bun test src/status.test.ts src/walkthrough.test.ts.

Closes #36

A listing can now be marked Active, Under contract or Sold (with an optional sold price). Under contract and Sold add a status post and a status email. I pushed the change, and bun test passes (171 tests). I could not run tsc --noEmit here because the repo has no tsconfig.json, so types are unchecked.

What changed

• Status and price: a listing has a status and an optional sold price. A migration adds both columns, and validateStatus in src/listing.ts checks them. A sold price is accepted only with Sold, in whole dollars from $1,000.
• One action, four doors: setStatus in src/actions.ts asks permit for the listing's update cell, so only the author or an admin may change it. It is audited, and no cell in contract.json changed. It is reached from:

- the listing page: a status box and price field with a "Set status" button, - the API: PATCH /api/listings/:id with {status, sold_price}, - the MCP: a new set_status tool, - the terminal: the s key, typing sold 752000, under contract or active.

• New assets: there are two new kinds, social_status (a Social tab post) and email_status (an Email tab email, subject "Just sold — 412 Alder Lane"). They are written in the listing's tone, Fair Housing checked, and each needs its own approval.
• Approval counts: the total is counted from the stored assets, so it reads "0 of 8 approved" once a listing is announced and "of 6" when active.
• Existing assets untouched: setting the status writes only the two status assets, so your edits and approvals on the other six stay. Saying what is already true changes nothing. Changing the sold price rewrites the announcement and clears its approval. A retone or "Edit facts" rewrites everything, status assets included.
• Pill and band: the home list and listing head show a status pill beside the approval pill when the status isn't Active. The flyer gets a "Sold at $…" or "Under contract" band, and its badge reads "Just sold" or "Under contract" instead of "Just listed". The new CSS classes are named in docs/design/areas/status.md.
• Sample: 88 Meridian Street (the condo) is seeded as Sold at $752,000.
• Tests and docs: src/status.test.ts covers validation, the words in every tone, the approvals and counts, who may change it, the band, the sample, and the MCP, terminal, API and page doors. The walkthrough has a new "Mark it sold" step with a matching README step. The README, contract/openapi.json and the existing tests that assumed six kinds are updated.

Choices to check

• I made the condo the Sold sample rather than 412 Alder Lane (the issue's example subject), because Alder Lane's open-house sample and its walkthrough steps depend on it staying live.
• The two status assets are labelled "Status post" and "Status email" in the editor, whatever the status.
• I did not add status to the launch form: a listing always launches Active.
• Open houses are not mentioned in the status assets.

To try it Open any listing you own, pick Sold with a price, press "Set status", and approve the two new assets. Or run bun test src/status.test.ts src/walkthrough.test.ts.

Both review points are fixed and pushed (660e4c1). bun test passes (171 tests); tsc --noEmit still can't run here because the repo has no tsconfig.json.

• Sold sample on existing databases: seed() now marks 88 Meridian Street sold on databases that already had it. It does this once, using a sample-condo-sold row in the seeded table. It only touches a listing that is authored by sample, matches the Meridian address, and is still active. I made it once-only because marking it on every boot would undo an admin who sets the sample back to active on purpose. Fresh databases are covered by the same pass.
• New test: in src/status.test.ts I reset Meridian to the pre-feature shape (active, no status assets, marker row removed) and re-seeded. It comes back Sold at $752,000 with 8 assets. After an admin sets it to active, a further seed() leaves it active.
• Orphaned comment: in src/tty.ts the \n line-break comment is back directly above toLine/fromLine, and the status helpers sit above it.