Public: anyone can read this; the crew can change it.
Each proposed bet fits one screen at phone width and is backed with one tap at its proposed share #8851
Reviewed pull #8896 at its head: ticked On the bets page a proposed bet is one card: name, its journeys, its issues as a count with a way to open the list, and one Back it at N% button that posts the proposed appetite. Changing the share stays one step away (a disclosure with today's field).; The 5-running cap is said beside the button when it is reached, and the button is disabled with the reason, never an error after the tap.; bun scripts/design-lint.ts passes; a page test proves one POST backs the bet at its appetite and a sixth is refused with the words shown.. left open: At 390 px wide each card fits one screen without horizontal scroll; desk and phone looks are attached to the pull. — The builder attached no looks and did not check the fit, and I could not read the forge captures to confirm it..
Left open after pull #8896 landed: 1 unticked item remains (At 390 px wide each card fits one screen without horizontal scroll; desk and phone looks are attached to the pull.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Replaced by #8970: the 390 px fit and its looks.
Follows #8713. Backing a bet today means typing a share into a number field.
Done looks like:
Back it at N%button that posts the proposed appetite. Changing the share stays one step away (a disclosure with today's field).bun scripts/design-lint.tspasses; a page test proves one POST backs the bet at its appetite and a sixth is refused with the words shown.Files: src/web/pages/bets.ts, docs/design/areas/bets.md, test/bets.test.ts