The spray pattern is a picture, not a promise: each automatic weapon's climb drawn from the table it is fired by #280

The page says the game has "fixed spray patterns you can learn" and then shows nobody what they are — draw each automatic weapon's pattern as a server-rendered SVG, from recoilOffset itself, so a player can learn the AK's climb before they meet it.

src/client/spray.ts and makePattern/recoilOffset in src/client/weapons.ts are pure functions of a weapon id and a shot number, and src/pages/weapons.ts already renders every damage cell by calling the simulation rather than typing a number. This is the same trick with a shape instead of a figure.

Done looks like

• [ ] A small module renders one weapon's pattern as an inline <svg>: the first magazine's shots as dots joined in order, in degrees, with the axes labelled and the scale stated — the pattern the gun actually has, read from recoilOffset, never a hand-drawn path.
• [ ] Every automatic weapon in WEAPONS gets one, next to its row; a weapon that is not automatic gets none and the page says why in one clause.
• [ ] Built once at module load like WEAPONS_SECTION is: no per-request work, no layout shift, and the whole section stays inside the page's byte budget test in src/server.test.ts (or the budget moves deliberately, with the measured number in the pull).
• [ ] No JavaScript and no image file: it is markup in the first paint, it is readable at 360px wide with no horizontal page scroll, and it carries a text alternative saying how high the pattern climbs and how far it drifts.
• [ ] Every value interpolated into the markup is escaped like every other cell on that page, and the page's CSP is unchanged — the style stays in the hashed block.
• [ ] A test asserts the drawn points are the ones recoilOffset returns for that weapon, so changing a pattern in weapons.ts moves the picture and cannot leave it lying.
• [ ] bun test green.

Files I expect to change

src/sheet.ts (the pattern as data, beside the damage rows), a new src/pages/spray.ts or a section of src/pages/weapons.ts, the reference page this table now lives on, and the .test.ts beside each.

Risks

• Where it lands. #272 gives the weapons table its own address; this should be drawn once, on that page, which is why it waits for it. If #272 is dropped, draw it in the #weapons section of / instead.
• Bytes. Nine inline SVGs is real markup on a page that is already 32,907 bytes raw and 9,683 gzipped against a stated ceiling. Path data rounded to a sensible precision, and a measured number in the pull.
• Honesty. RECOIL_SHARE means the bullet does not go exactly where the pattern points; the caption has to say which of the two the picture is.

Suggested: Torque — server-generated SVG, stated units and assumptions on the page, and a test that matches the drawing to a hand calculation.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.