Public: anyone can read this; the crew can change it.
Make a square picture for each listing's social posts: hero photo, price and a Just listed / Open house / Sold band in the agent's brand #53
Reviewed pull #66 at its head: ticked GET /listings/:id/card is a square page (layout kind: "print", the flyer's print bar and Print button) sized 1080×1080 CSS pixels: the hero photo filling the square, a band in the listing's brand colour with one headline — "Just listed", "Open house Sun, Mar 7, 1–3 pm" (the same wording as the flyer), "New price", "Under contract" or "Sold", in that order of precedence from the listing's status, price improvement and open house — then the price, beds · baths · square feet, the address, and the agent's name, brokerage and phone.; The words on it are facts and the agent's brand only, never asset text. It carries the "Draft — not approved" band until the listing's first social post is approved, exactly as the flyer does with the flyer asset.; Under the Social tab, a Square picture link opens it; a listing with no photo gets the brand colour as the background and the same layout, not a broken image.; Anyone who may read the listing may open it (asked through permit with the existing listing read cell; no cell changes); an unknown id is 404.; Server-rendered, no new JavaScript; every field escaped (add the page to src/hostile.test.ts); within src/speed.test.ts's budget; bun scripts/design-lint.ts passes with any new class named in docs/design/areas/.; Tests in a new src/card.test.ts: the headline for each case (active, open house, price lowered, under contract, sold), the draft band before and gone after approving the first post, 404 for an unknown id. The README's walkthrough gains one line for it..
Intent: a social post on Instagram or Facebook needs a picture, and the agent should leave the meeting with one for each listing, in their brand, without a design tool.
Done looks like:
Files I expect:
src/pages/card.ts(new),src/routes.ts,src/pages/listing.ts(the link),static/app.css,src/hostile.test.ts,src/speed.test.ts,src/card.test.ts(new),README.md.Risks: long addresses and seven-figure prices must not overflow the square — test with the hostile listing's longest address. Printing must give one page; saving as PDF or a screenshot is how the agent gets the picture, and the README says so plainly.
Fits: a builder's brief.