${q.beyondSaving
+ // SPRINT14 — B's pool item. On a gardenBeyondSaving night the bed
+ // cannot reach the win line at any price (week.js's flag, A's S13
+ // ruling), so "paid on what's left of the bed at dawn" quotes a
+ // maximum nobody can earn and reads as a rigging problem the
+ // player could solve. The AMOUNT stays honest — settle() really
+ // does pay this proportionally, and zeroing it here would make the
+ // sheet lie in the other direction — but the CONDITION now says
+ // what kind of night this is, up front, where the brief already
+ // levels with you. The steel is still yours to save.
+ ? 'scales with the bed at dawn — and tonight the ice takes it whatever you rig'
+ : "paid on what's left of the bed at dawn"}
${w.won ? 'callout fee' : `callout fee — night lost (${Math.round(100 * w.fee / Math.max(1, w.fullFee))}%)`}+$${w.fee}
-
garden bonus — ${r.hp.toFixed(0)}% of the bed+$${w.bonus}
+
garden bonus — ${r.hp.toFixed(0)}% of the bed${
+ // SPRINT14 — B's pool item, the invoice half. On a beyond-saving
+ // night this row is always small, and next to "callout fee — night
+ // lost" it reads as the player's failure. It isn't: the bed was
+ // gone at the forecast (week.js gardenBeyondSaving). Naming that
+ // HERE, in the ledger, matters more than in the verdict prose —
+ // the ledger is the part players re-read, and an unexplained small
+ // number is the most persuasive lie on the card.
+ w.gardenBeyondSaving ? ', beyond saving from the start' : ''
+ }+$${w.bonus}
${cleanRow}
gear recovered+$${w.refund}
${collateralRows}
diff --git a/web/world/js/week.js b/web/world/js/week.js
index 67007da..4ef8000 100644
--- a/web/world/js/week.js
+++ b/web/world/js/week.js
@@ -303,6 +303,23 @@ export function createWeek(opts = {}) {
base: PAY.feeFor(gustPeakOf(def)),
garden: j.pay.garden ?? PAY.gardenBonusMax,
clean: j.pay.clean ?? PAY.noCollateralBonus,
+ /**
+ * SPRINT14 (B's pool item, offered S13 and accepted): the job sheet has
+ * to say when the garden bonus is money the night cannot pay.
+ *
+ * Deliberately a FLAG and not a zero. The comment in settle() below is
+ * the rule — quote and settle must read the same source or the sheet
+ * promises a number the invoice doesn't pay — and zeroing this would
+ * break it in the opposite direction: settle still pays the bonus
+ * proportionally (hp is low on a beyond-saving night, not zero), so a
+ * quoted $0 would be its own lie on paper. The NUMBER is honest. What
+ * was missing is its CONDITION, which on this night is "and the ice
+ * takes the bed whatever you rig". The job sheet's own idiom is that
+ * every amount carries its condition underneath; this is a night where
+ * the condition is the entire story and the schedule was the last place
+ * still not telling it.
+ */
+ beyondSaving: j.gardenBeyondSaving ?? false,
get total() { return this.base + this.garden + this.clean; },
};
},
@@ -371,6 +388,11 @@ export function createWeek(opts = {}) {
const s = { fee, fullFee, bonus, refund, clean, cleanMax, collateral, pay, spent,
bankBefore, bankAfter: bank, outcome, night: week.night, held,
grade: gradeFor(held), stormKey: week.stormKey, won: !!run.win,
+ // B's pool item: the invoice needs this to explain a small garden bonus
+ // as the night's design rather than the player's failure. Carried on the
+ // settlement so the HUD never has to reach back into week state.
+ gardenBeyondSaving: job.gardenBeyondSaving ?? false,
+ gardenMax,
client: job.client, addr: job.addr, site: job.site };
log.push(s);
return s;