FlagHunt 🎯

Alpha changelog — every patch note

09/07/2026 — the duel, watched properly

🎬 A FILM OF A WHOLE MATCH, before anything was changed. scratchpad/clashfilm.mjs plays a bot duel and takes a screenshot every ~220ms from the lobby to the result card — 320 frames, each tagged with the cover text, the strip, the verdict, which controls are up, the camera eye recovered from the view matrix and how many GL renders landed in the tick — then lays them out as contact sheets. "The camera glitches" is not a number, and reading every frame of a match is the only honest way to say what the mode actually does. The rest of this entry is what the frames said.
🏌️ THE SWING WAS NEVER SEEN. The animator sets the phase to "flying" before the golfer's club goes back, and the flight camera's address/tower blend read the phase — so on the swing's FIRST frame the eye jumped from 4.0 up / 9.5 back to 8.5 / 12, and the figure at the ball dropped off the bottom of the frame. A spectator got an empty tee for the whole backswing and downswing (~750ms), then a ball already in the air: a tee shot with no swing. Both the approach and the drive cameras now hold the address framing while avatarInSwing, which is continuous with the ease that follows (it starts at ball.t = 0), so there is no cut anywhere. Nothing moves in a mode without a golfer — there the ball appears at t = 0 on the frame the phase changes, and the blend was already 0.
👤 THE GOLFER IN A DUEL IS THE OPPONENT'S, NEVER YOURS. Your own shot is the par-3 shot as it has always been played, and a figure over the ball only stood on the one line you are reading at address. The golfer exists for the half of the match you watch, so avatarLive() in clash is true exactly while the stage lock or the replay flag is — their setup pan, their swing, their flight. Career keeps its golfer on your own shots: there, the golfer IS you. avatarclash.mjs now asserts zero golfer frames while the cover is down.
🎥 THREE CUTS ON THE REPLAY, EACH NOW A DISSOLVE OR A HOLD. (1) The putt scene appeared with a hard cut from the landing tower; their own screen melts into the green (dipToPutt), and so does the watcher's now. (2) After their flight, the next draw() had no ball to read the descent dolly off and snapped the camera back to the tee — landView is set at rest exactly as the striker's screen sets it, drawn on the NEXT frame (a second render in the animator's last tick is the flicker this path is measured clean of), with their aim kept until the beat ends because the reveal camera looks back down the line the shot was played on. (3) A rebuilt hole for their replay ran newHole's cinematic — a 3-second orbit the cover made unskippable, with a Skip button flashing over the opponent's tee as the tell — and cut into it with the previous hole's verdict still on screen. A rebuild now goes straight to address under a dissolve, takes the last verdict down, and the fly-in is kept for one case only: the first look at a hole that is YOURS to play.
🧾 VERDICTS END WHEN THEIR BEAT ENDS. "3.9 ft" from the tee shot sat over the ball for the entire putt, and "misses the green" was the first thing painted over the next hole. Each replay stage takes its own verdict down; the green's stays up into the dissolve because the putt is the same story. The tee verdict also says what it is now — "Ivy Callahan: on the green, 6.1 ft 🎯" mirrors the striker's own "On the green: 6 ft" — where it used to read "Ivy Callahan — 3.9 ft".
📏 THE STRIP CLIPPED ITS OWN LEAVE BUTTON. One nowrap flex row: "⚔ vs Russ Drewitt ◌ Russ Drewitt is playing… · your 4,151 to beat 30s Leave" measured ~490px against a 377px phone, and the overflow was simply cut — the clock and Leave were off-screen for the whole of an opponent's turn, and the name was said twice. It is two rows now (name, holes, clock, Leave; then whose ball and the number to beat), the name is said once, the turn text reads "Your ball" / "Their ball", and nothing that matters can shrink. Ellipsizing on one row was tried and read "vs Ivy C… · your 1,6…", which is worse than either fault.
🙊 NO SPOILERS. The score band and the strip's dots read the doc, and the doc already carries their points for the hole on stage — a bot's shot is priced before it is watched, and a human's putt posts with the card their tee shot is replayed ahead of — so the band read "RUSS DREWITT 7,504" and the dot went red over a setup whose ball had not left the club. A hole of theirs now counts on this screen only once every shot of it has been WATCHED; the figure and the dot land with the verdict, which is the reveal. The band also priced d.holeNo ("Hole 2 · has PW" over hole 1's tee) and now prices the hole on stage.
🚫 NOTHING TO PRESS WHILE WATCHING. Every control under the cover was inert already (the cover swallows the tap) but still looked live: my club wheel and both dials on their think-beat, HOLE VIEW and DRAG TO AIM on their setup, a dimmed PLAY button under the score, the putt power bar and the heat toggle on their green. All hidden under body.clash-watching now; the read strip on their putt stays because it is the green's truth, not a control. The cover's pill — which sat on the Loft slider and repeated the strip — is a broadcast bug at the top of the stage ("● IVY CALLAHAN'S TEE SHOT…") naming the STAGE while the strip names the TURN.
⏳ "POSTING YOUR HOLE…" COULD SIT THERE UNTIL THE OPPONENT'S CLOCK RAN OUT. Tap Continue on your card before the post's response has landed and the match loop parks under that cover waiting for the doc to show your hole carded — and nothing woke it. The response that DID carry your hole only redrew the strip, and the poll the park started asks the server for anything newer than the version it now holds, to which the answer is no. The instrumented avatarclash journal shows it plainly: "Posting your hole…" from 23.9s to 92.7s, the bot never invented a shot because the watcher was never entered, and the server ruled the bot out on its clock — three matches in a row "won" 2–0 with the opponent scoring 0, 0. A doc landing on a parked match now re-enters the loop (never over the card or a running replay, which have their own re-entry). It was reached by a fast tap, which is how a real player on a slow connection would reach it too.
📐 THE DIAGONAL SHRINKS FOR A WIDE MISS. The 22-degree spectator swing is budgeted for a ball that flies roughly down its line — the landing area already sits near -11 degrees of a 12.6-degree half-frame — and a 9-yard miss on the far side was measured AT the edge (the ball's ndc.x reached 1.0 on hole 2 of a clashwatch run, where a 2-yard one sat at 0.3). The azimuth now scales with the posted lateral: full inside 4 yd, half at 9, a floor of 35%. Read once off the shot like the side is; a wild miss does not need cinematic framing, it needs to stay on screen.
🧪 avatarclash.mjs 8/8, re-keyed to the new rule: zero golfer frames while the cover is down, 215 while watching, the watched club travelling 1.77 yd from the floor of its arc, and the swing inside the frame sideways for 20 of its 21 frames (worst 0.37 of the horizontal half-frame); it also gained a cover/strip journal and a rejection listener, which is what found the parked-post stall. looksync.mjs 10/10 ("the host's own screen never draws the host"; the guest's screen wears the host's $60,000 shirt for 59/59 frames). clashrun 0 bugs, clashduel 0 bugs (two real clients, verdicts agree). clashwatch 27/27 after six runs of random bot shots: the diagonal, the pan, the band and the no-controls rule all hold, a replayed flight renders exactly once per frame, and the ball's worst sideways position in one was 0.49 of the half-frame. Three of the harness's "failures" on the way were its own, and each is now attributed by what is actually on stage: the tick a caption changes in was booked to the stage before it (so the putt's dissolve counted against the flight); the camera frame from that tick was one scene's ball seen through the other scene's camera (a dead-straight shot "reached" ndc.x 1.45); and address samples were filed by the dot count, which names the hole the match is on rather than the hole on stage (a late replay of hole 1 compared against hole 2's terrain read as 0.9 yd of eye-height drift). Filmed again after: the swing is on screen from address through impact, the reveal holds, the green dissolves in, the band reads 0 for a hole still being watched and updates with the putt's verdict, and the strip carries Leave through every turn.

09/07/2026 — the daily reward track goes back behind the gate

💵 SIX OF THE SEVEN RUNGS WERE PRICED IN A CURRENCY BEHIND A LOCKED DOOR. The check-in ladder pays career cash on days one to six, and career is behind the beta gate — so a public player was shown "$2K, $4K, $7K, $12K, $18K, $25K", a button reading "Claim $2,000" and a confirmation answering "Banked $2,000", for money they cannot spend, cannot see (there is no bank screen without a golfer) and have no way to reach. The one rung that worked for them was the day-seven cosmetic, which the code already admitted in its own comment: "the half of this that works for a player who has never opened career".
🔇 HIDING ONLY THE FIGURES WAS THE FIRST ANSWER, AND IT WAS THE WRONG SIZE. It left the weaker half of the feature on screen: a card that raises itself on boot, once a day, to hand over a dot on a progress track and a button reading "Check in". A feature whose reward has to be redacted to be shown is not ready to be shown. So the whole track is shut on a public link — no card, no claim, no 🎁 on the streak chip — and it opens complete on the day career does.
🚪 ONE PREDICATE, NOT A SET OF DISPLAY BRANCHES. checkinAvailable was already the single question the boot card, the claim and the streak chip's gift affordance each asked, so the gate went there and five separate copy branches (ladder cell, button, tooltip, note, verdict) went away with it. There is no second place a figure can leak from and no public-only wording to keep in step with the real thing.
💰 THE LEDGER IS UNTOUCHED. claimCheckin, pendingCash and payPendingCheckinCash all behave exactly as before, so a claim already made keeps its money and its cosmetic, and reopening resumes mid-week rather than resetting anyone to day one. Nothing migrates and nothing is forfeited.
❄️ STREAK INSURANCE STAYS OPEN, because it is not a reward. The monthly save protects a run the player already has, it pays out nothing and advertises nothing, and it is offered on the one day it is honest to offer it. Shutting it would take something away from a public player rather than stop showing them something they cannot have.
🎯 THE STREAK CHIP KEEPS THE STREAK. The number, the emoji and a guest's "· this browser only" are all still there — that line is the truth about where a guest's run lives, and it is the most persuasive thing on the screen. Only the claimable-gift half of the chip is gone. The guest sign-up card drops its check-in bullet and the check-in clause from its streak pitch for the same reason: the pitch cannot promise a reward the account does not get yet.
🧪 checkin.mjs is 46 checks (was 36), and the public cases assert ABSENCE rather than redaction — the card never opens at all, the chip carries no 🎁 and no claimable label, nothing is stamped in storage behind the player's back, and the sign-up list is read through getComputedStyle so a hidden bullet cannot pass as a shown one. Under the gate the ladder still walks day one to the day-seven cosmetic, still reads "Claim $2,000" and still banks $13,000 of held cash into a new golfer. The queue case moved to the public link on purpose: a ?beta= arrival deals no daily at all, so the only link where the welcome exists is the one where the check-in card does not, and the streak save is the decision card it has to wait behind.

09/05/2026 — the golfer is yours now

👤 SIX SLOTS, AND YOU CHOOSE ALL OF THEM: skin, hair, cap, shirt, trousers, shoes. Each is its own catalogue of { key, name, colour, price }, so adding a colourway is one line in one array — the renderer reads SLOTS and never entries, and nothing downstream has to be told a new garment exists. 8 skin tones, 7 hair colours (one of them shaved), 7 caps (one of them none), 10 shirts, 6 trousers, 5 shoes: 5,536 distinct outfits before anyone spends a penny.
🆓 THE BODY IS FREE AND ALWAYS WILL BE. Not one skin tone or hair colour carries a price, and the checks assert it rather than trusting it — you do not sell somebody their own face. The KIT is what the pro shop sells: 14 items from $12,000 to $60,000, on the same prize money as balls and trails, and every garment slot keeps a plain base colourway at zero so a player who never spends anything is still dressed rather than half-naked.
🎲 AN UNCHOSEN GOLFER IS DEALT ONE, which is what makes a tour pro look like somebody. Every slot reads a different slice of the name's hash — and the deal is restricted to the FREE entries, so a hash can never hand out something the shop sells. Measured across 40,000 names: 0 paid items dealt, 0 unknown keys, 0 golfers left capless, and never a cap the same colour as the shirt (the cap is what stops the head reading as a ball). Rebalancing which items are free was part of this: the first cut left only two free entries per garment, which quietly cut a dealt golfer's variety BELOW what it had been before the wardrobe existed — the opposite of the point.
👀 AND YOUR OPPONENT SEES WHAT YOU BUILT. Six keys, comma-joined into a 29-byte code, ride along with the shot that already crosses — so a spectator watches the golfer you made rather than one dealt from your name. A tour pro never sends one and neither does a client older than this, so the dealt look is the fallback rather than the rule, and a code this build cannot read is REFUSED whole rather than half-applied: 4,000 round trips clean, and nine kinds of malformed code all rejected rather than reaching the renderer as a colour with no channels in it. In a duel the two of you are still guaranteed to differ, and it is only ever the WATCHED golfer that moves, so your own choice is never overridden on your own screen.
🧢 TAKING THE CAP OFF TAKES IT OFF, and a shaved head draws no hair, rather than either drawing in a colour that means nothing. Hair sits just proud of the skull and slightly back, and is drawn UNDER the cap rather than instead of it — which is what lets it show at the back of a capped golfer and be the whole silhouette without one.
🏠 THE FACE IS CHOSEN WHERE THE GOLFER IS, the kit where the money is. Creating a golfer asks the two free questions that are about who they are, as two rows of 28px swatches in 44px rows; the other four live in a new Wardrobe tab in the clubhouse beside the pro shop. Six grids on the creation screen would have buried the archetype choice, which is the one that actually changes how the golfer plays. The look is stored under its own key rather than inside the career save, so a Clash player who has never opened career still has a face — the same shape the check-in ladder already uses for a cosmetic that has to work with no golfer.
🔒 AND THE SHOP'S RULES HOLD WHEN A REAL FINGER PRESSES THEM. An item you cannot afford is dimmed, shows its price, and buys nothing when pressed — no money moves, nothing is recorded, nothing is worn. Equipping something unowned does not wear it: the dealt garment stands, so a hand-edited save cannot dress a golfer in something never bought. Buying takes exactly the price, records the item, and wears it, measured through the real button: $20,000 to $5,000 for a $15,000 shirt, owned, worn, and on the golfer's back on the next tee.
🤝 AND IT IS VERIFIED THROUGH A REAL DUEL, not just as a round trip. looksync.mjs, 11/11, stands up two accounts, two browser contexts and a PvP match off the invite link. The host wears the $60,000 Blackout shirt; the guest watches their tee shot. Because a look dealt from a name is restricted to the FREE half of the catalogue, a paid garment on the watcher's screen cannot be a coincidence, a hash collision or a fallback — the wire is the only way it gets there. Measured across the replay's own captioned stages ("lining it up", "tee shot"): 80 of 80 frames had all four visible parts — shirt, cap, hair and skin — matching the six-key code the database says the host actually sent, while the guest's own golfer stayed in their own colours.
🧪 wardrobe.mjs, 26/26, runs the catalogues and the rules as pure functions with no browser — every entry's shape, the free-body invariant, 40,000 dealt looks, per-slot fallback, and the wire code's round trip and its refusals. wardrobeui.mjs, 20/20, does the same journey through the real screens and reads the result out of the vertex stream, where each part has a known vertex count (a shirt is 96 — torso, shoulders and both arms at 24 each; the head and hands are 1,008; a cap is 528). One probe lesson worth keeping: asking "which colour has 1,008 vertices" has more than one honest answer, because the two tee markers add up to exactly that and the ball at address is a 504-vertex sphere just like the hair — so it asks about the colour it chose, never the count alone.

09/03/2026 — somebody is hitting the ball

🏌️ A GOLFER STANDS OVER EVERY FULL SWING IN CAREER AND CLASH. Until now a watched shot was a ball leaving an empty patch of grass, which is a strange thing for a mode built around watching each other play. The figure is built from the primitives the scene already has — tapered prisms for the bones, spheres for the head and hands — so there is no asset pipeline and nothing new to load: about 1,900 vertices, in the same props buffer as the flag and the ball. Career and Clash only, both of which are behind the ?beta= gate. THE PAR-3 MODES DRAW NOBODY: they have shipped, and this does not touch them.
🦴 THE RIG IS ONE SHOULDER PIVOT AND ONE WRIST HINGE, both turning in the swing plane (the plane through the shoulders holding the shaft at address and the target line), plus a shoulder and hip turn that follows the arms. That is all. Read from 9.5 yards behind, a golf swing is the club going back and coming down; the rest is silhouette, and a rig with more joints is a rig with more ways to look wrong. It lives in shared scope beside flightApexYds for the same reason that does — the shot animators read its timing and the renderer reads its geometry, and a rig defined inside the GL module would hand the two of them separate copies to drift apart.
🎯 IMPACT IS THE FRAME THE BALL LEAVES, and it is exact by construction rather than by tuning. The shaft's LENGTH is not a constant: it is whatever reaches from the hands to the ball, so the clubhead is on the ball at address, the pose at impact IS the address pose, and the two agree to 7e-18 of a yard — a later change to the stance or the spine cannot quietly break it. Measured in the browser as well as on paper: the arc bottoms out at t+231ms, the ball is still at rest at t+234 and moving by t+311, one rendered frame later.
👋 THE CLUB GOES BACK WITH YOUR TAPS. Pick the club and the golfer is at address; lock the line and they take it away; the carry bar sweeps with the club at the top, waiting on you; release and the downswing plays, 190ms, and the ball goes at the bottom of it. That is the only beat this adds to a shot. The FIRST cut of it drove the backswing off the power bar itself, which read beautifully and quietly falsified the sentence liveSweepDraw is built on — "while a bar is sweeping the scene CANNOT change… aimSweep and powVal only ever position DOM elements — grep them: not one feeds the renderer". Buying that backswing costs a full scene redraw on every frame of every power bar, and the power bar's timing IS this game. A cosmetic does not get to make the core input jerkier on a slow phone, so the pose is a function of the PHASE, which changes on a tap and repaints exactly once.
👀 A REPLAY PLAYS THE BACKSWING TOO, because no bar was ever swept on the watcher's screen and a club that appears already at the top is a cut — the one thing a spectator's camera is not allowed to do. Your own shot swings from the top in 190ms; theirs runs the whole thing, 560ms back and 190 down, across the setup beat that already pans the camera to their line.
👕 AND YOU CAN TELL EACH OTHER APART. Shirt, trousers and cap are hashed off the golfer's name — your career golfer's, or the opponent's in a duel — from a palette of eight shirts and four trousers keyed off different slices of the hash, so two players who collide on one still differ on the other. NEVER SKIN: a colour picked for someone by hashing their name is a fine way to tell two golfers apart and a poor way to assign a person an appearance they did not choose, so hands and faces are one neutral tone until there is a picker to choose with.
📐 THE FIGURE IS 5'9" AND SITS WHERE A GOLFER SITS. From the address camera the head is 13.0 degrees below the view axis and the feet 22.8, against a 23-degree half-frame: the whole golfer occupies the bottom 23% of the frame and never crosses the axis the shot is framed on, so the flag stays clear. The stance puts them 5.2 degrees off the line against a 12.6-degree horizontal half-frame. The ground is sampled under their FEET, not under the ball — the same numbers on a flat tee and up to a foot apart on a slope, and it is the feet they are standing on.
🐛 THREE BUGS THE PROBE CAUGHT THAT A SCREENSHOT WOULD NOT HAVE. Half of all names hash above 2^31, where a signed >> goes negative, the modulo stays negative and the palette lookup hands back undefined — which reaches the renderer as a colour with no channels and throws on every frame. The downswing read the live pose to know where to start, but by the time an animator runs the phase has already left drivePower, so it read the address fallback, interpolated from address to address and moved nothing. And between the release and the ball leaving, neither of the scene's two reasons to draw a golfer holds — the phase has moved on and the flight has not started — so the swing rendered exactly one frame, the impact one, with everything before it missing.
🧪 avatar.mjs, 18/18, all of it read out of the vertex stream rather than off a picture: the club wears a steel colour nothing else in the scene has, so its 48 vertices can be found and measured frame by frame. The golfer at address, the takeaway and the top as separate poses, the club HOLDING through 90 frames of the sweeping bar (one distinct height — the invariant above, asserted), the strike, the approach scene as well as the tee (told apart by the tee markers, which only one of them plants), and free play drawing nobody. A standalone rig check runs the maths with no GPU at all: impact exact, the shaft rigid to 9e-16 through 400 samples of the swing, the clubhead crossing the ball exactly once and never digging. The career autopilot ran a full 18-hole event: 18 hole cards, no page errors, no console errors, nothing flagged.
🧪 avatarclash.mjs, 7/7, covers the case the feature exists for: a real duel against a tour pro, with the club tagged by whether the spectate cover is up. 137 frames of golfer while watching, 1.77 yards of clubhead travel starting at the floor of its arc and rising — the replay's extra backswing, measured — and the two of you in different shirts (found by the colour that dresses exactly 96 vertices: torso, shoulders and both arms). It also projects the golfer through the recovered view matrix, because being in the vertex buffer is not the same as being in frame.
📋 AND ONE NUMBER THAT IS NOT PERFECT, recorded rather than smoothed over. Sideways — the axis a spectator's 22-degree swing actually moves, and the tighter half-frame on a phone at 12.6 degrees — the golfer stays well inside, worst 0.355 of the way to the edge across a swing. VERTICALLY the club and the golfer's legs cross the bottom edge on part of the swing (worst 1.33 of the half-frame). That is the shipped par-3 framing rather than something this introduced: the ball itself sits 22.8 degrees below the axis against a 23-degree half-frame, thin on purpose, and a golfer standing at the ball stands at that same edge. The head and torso stay in frame throughout. Worth knowing before anyone changes the address camera.

09/03/2026 — an email on every account, and consent as its own question

📮 AN EMAIL IS NOW REQUIRED TO CREATE AN ACCOUNT, which the retention work below explicitly left undone. Username and password signups collected no address at all, so the only ones the backend held were whatever Google hands over on a social sign-in — meaning a player who lost a password or changed phone had no route back to their streak, their scores and their career, and there was no way to tell them anything either. The signup form asks for it beside the username and password, validates it client-side before a request leaves (one @, a dot in the domain, no spaces — permissive on purpose, since anything stricter turns real addresses away), and the server has the final say: required, format-checked, and unique across accounts by a case-folded index, with its own error so "already taken" says WHICH field it means. The log-in path asks for nothing new.
☑️ BEING WRITTEN TO IS A SEPARATE QUESTION, AND THE BOX STARTS EMPTY. The address is required because it is the only way back into an account; mail is a different thing to agree to, so it is its own tick, its own column (marketing_opt_in, default false) and its own timestamp. A pre-ticked box is not consent — it collects a number, not permission — and this yields fewer addresses that are worth more, because the only list the admin endpoint will hand over for a campaign is the one where somebody actually said yes. The security line under the form now says what the address is for in the same breath as the bcrypt promise, rather than leaving the player to guess.
🔁 AND THE PROFILE IS WHERE YOU TAKE IT BACK. An opt-in with no opt-out is not a consent control, it is a trap, so the profile carries the standing switch: whether an address is on file, and a checkbox that writes the answer in BOTH directions (measured: ticked at signup, unticked from the profile writes false and leaves the address alone — you unsubscribe, you do not lose the account — and ticking it again writes true). The address is never printed back, on that screen or by the endpoint that feeds it: a profile is a screen someone can read over your shoulder, and an endpoint that returns an address is an endpoint that can leak one. The client only needs to know WHETHER there is one, so that is all it is told.
🗓️ EVERY ACCOUNT MADE BEFORE TODAY IS ASKED ONCE, with the reason attached rather than as a bare form — "Your 6-day streak, your stats and your career live on this account, and it has no email on it" — because a request to hand over an address should name what it protects. It joins the boot-card queue built for the check-in ladder, so it can never stack on top of another card, and "Not now" is a real answer: it is asked once, and after that the profile row is the standing door. An account with no address gets that row as the ask instead of a consent box, with no once-a-day rule on it.
⏱️ THE ONE HARD PART WAS A RACE, and it is the kind that only ever fails in the direction that matters. Whether an account has an address is a question for the SERVER, boot is synchronous, and the client's default assumption is "none on file" — so an ask fired during boot is an ask aimed at a guess, and the guess is wrong precisely for the people who already gave one. The prompt now waits for the answer to land (and the profile row renders nothing at all until it has, rather than telling someone who gave an address that they did not). Measured by sampling every 40ms from before the first script runs: across a full load of an account with NO address, 0 of 34 frames had the ask up before the server answered, and across an account WITH one, it never appeared in any of 38 frames and the once-only key was never even set.
🗄️ THE COLUMNS ADD THEMSELVES, in the house style — CREATE/ALTER … IF NOT EXISTS on first touch — so there is no migration step to forget: email, email_lower with a partial unique index, marketing_opt_in and email_at. The register route sets the address in a SECOND statement after the account exists, so a schema hiccup can cost the email and never the signup a player just completed. A new endpoint carries the rest: GET returns only { hasEmail, optIn }, POST with an address attaches or replaces it, POST with just the flag changes consent alone (the unsubscribe path), 401 without a token and 409 for an address already on another account.
📋 AND THE ADMIN LIST TELLS THE TRUTH ABOUT ITS OWN COVERAGE. It unions both sources and labels each row — signup addresses with their consent answer, social addresses from linked_oauth with none, because nobody was asked anything while authenticating — dedupes by address (keeping the row that carries an answer), and takes ?optIn=1, ?format=csv and ?limit=N. The unfiltered list is for support and for counting; the note it returns says so, along with how many accounts have no address at all. Still behind ADMIN_USER_IDS, which is the one endpoint returning personal data in bulk.
🧪 email.mjs, 34/34, through the real client against the real database: the form's three refusals, the address and a FALSE consent landing on the row when the box is left alone, a true one when it is ticked, the log-in pane asking for nothing, the older-account prompt naming the streak and its write sticking through a reload, both sampled race measurements above, the profile row in both its states (including the unsubscribe round trip, an 18px box in a 44px label, and its text at 12.26:1 composited down through every ancestor), and the admin list still answering 403 to a caller who is not an admin. Two of its own artifacts, recorded because they cost real time: psql renders booleans as t/f when read bare but true/false when string-concatenated, and the profile is behind whatever boot card is up, so the queue has to be walked empty before it can be opened at all.

09/03/2026 — a reason to come back tomorrow, and a reason to sign in

🎁 A DAILY CHECK-IN LADDER, seven rungs, one claim a day, ACCOUNT ONLY. $2,000 rising to $25,000 across six days, then the seventh pays a COSMETIC — the next ball or trail the player does not own, cheapest first, so the week after hands out something different rather than the same prize forever. Claiming on consecutive days walks the ladder up; miss a day and the week starts again. Nothing is gated behind an account: every mode stays open to a guest exactly as before. The ladder is simply the thing an account is FOR.
⚪ THE PRIZE WORKS FOR A PLAYER WHO HAS NEVER OPENED CAREER, which is the half that matters for converting anyone. Cosmetics have always lived inside the career save, so refreshGear now falls back to the check-in's own store — balls and trails are drawn by the shared renderer, so an unlocked one shows up on the daily, in free play and on the range. The cash has the mirror problem and the mirror fix: with no golfer to pay, it is HELD and banked the moment one is created (measured: $13,000 of held rewards landing in a new golfer's bank), because a reward that silently evaporates is worse than no reward.
🔥 THE STREAK IS ON SCREEN AT LAST. It has always been measured — a daily streak with the full play history behind it — and it lived buried in the profile. It is now a chip in the daily bar, and a GUEST's carries the truth: "4 days · this browser only". That is not a scare tactic. A guest's streak, stats, aces and career are in one browser's localStorage, and one clear wipes the lot. Saying so plainly is the most persuasive thing this game has, and the chip is also the standing door to the reward.
❄️ STREAK INSURANCE: one save a month for an account, offered on the one day it is honest to offer it — the run is exactly one day cold and would otherwise read zero. Using it records yesterday as covered so every streak reader sees an unbroken run, marks the day as frozen rather than scored (it posts a 0 the account's merge can never let lower a real score), and stamps the month so it cannot be spent twice. Missing one day is the single biggest churn moment in any daily game.
🗣️ THE SIGN-UP NUDGE LEADS WITH THE NUMBER. It used to fire after any round with a generic feature list. Once a guest has a run of two or more it opens with "4-day streak 🔥" and says where that run is stored; with no streak yet it keeps the old rhythm of the first three rounds then every third, because a player who has said "maybe later" three times has been heard.
🃏 ONE CARD AT A TIME, IN ORDER, which two bugs this change created made necessary. Boot can have several things to say — the round just finished, a streak a day from dying, today's reward, a release note, and the daily's own welcome. The daily card was raised directly and landed ON TOP of the check-in card, hiding the one screen with a reward behind it; and because bootPopups is called from three places, the second pass would find the first card "already seen" and stack the next one over it. It is a queue now: each card returns true when it takes the screen, dismissing any of them advances it, and nothing goes up while something is already up. The reward and the streak save come first, because they are decisions; the daily's welcome is only "now play", so it waits.
🙅 AND DECLINING IS A REAL ANSWER. Both new cards ask once a session: the queue re-runs on every dismissal, so a card that stays "available" until claimed would raise itself again the instant it was closed — an offer that cannot be declined. Closed, they stay closed; the chip is how you come back to the reward.
🧪 checkin.mjs, 36/36: the guest case, day 1 through the day-7 prize, a mid-week continuation, a lapsed week restarting at day 1, the claim's writes, the reward not re-offering the same day, the held cash being banked at golfer creation, every branch of the freeze (offered, spent, guest, three days cold), and the queue order both ways round. Regressions rerun: newday 17/17, blitzrun 103/103, carry 24/24.
📮 NOT IN THIS CHANGE, and worth saying plainly: no email is captured anywhere yet. Username and password signups collect none, and the only addresses the backend holds are the ones Google hands over on a social sign-in (linked_oauth.email). An opt-in "add an email so a lost device does not cost you the run" belongs with this system and needs a consent flag of its own before a single message is ever sent to it.

09/03/2026 — Mental is wired: pressure, and the nerve that answers it

🫀 MENTAL WAS THE ONE RATING WIRED TO NOTHING. Every use of it sat behind if (R.pressure), and R.pressure was initialised false and assigned by no code path in the file, so a point in it changed no shot — the store had stopped selling it and the help sheet admitted it was inert. What was missing was never the effect. It was the SITUATION, and the game already computes exactly the situation that matters and already shows it to the player on every hole card: live, cut-aware standings with their own position in them. Pressure is read off that.
✖️ THREE FACTORS, MULTIPLIED, so any one of them at zero means no pressure at all. STAKES: what the round decides (Sunday 1.0, Saturday 0.55, Friday 0.5 — the cut outranks moving day, Thursday 0.15). URGENCY: nothing for the first four holes, ramping to full on the 9th. DOUBT: how close the line you are playing against is — the nearest rival's score on the weekend, the cut line itself before it — gone by six shots either way. Measured across a swept leaderboard on Sunday's 9th: 100% level with the rival, 33% four clear, 0% by eight; and across Friday's cut line: 0% eight inside, 17% at -2, 42% on the number, 0% seven past it. It is memoised per hole because careerStandings builds the whole 144-player field and the bar timings that read it are called every frame.
⚖️ COMPOSURE IS TWO-SIDED, which is the point. The old wiring only ever punished — even a 99 Mental had its bars run 8% quicker — which made the rating a tax rather than something worth buying. The crossover now sits at Mental 80: below it the moment gets to you, above it you play better down the stretch than you do on Thursday. Each side is scaled by its own span so the whole 50-99 range is expressive instead of everything under 56 clamping to the same "rattled". Measured on the approach aim bar in the identical situation: 2,067 ms calm, 1,367 ms at Mental 50 (34% quicker) and 2,433 ms at Mental 99 (18% slower) — a 78% spread between the two ends of one rating.
🚫 THE HIDDEN HOOK IS GONE. Pressure used to take a flat 12% off a putt's make probability. That is a penalty a player can neither see nor beat, which is the one thing a rating this legible should never have: it now lives only on the bars (approach, drive, chip and putt, all four, so the two halves of one swing cannot disagree about whether the moment is tense) and on the putt's roll noise, around its ordinary 0.18 baseline. cappedSweep still owns the floor, so pressure can never push a bar past the hardest the game gets.
🎯 AND IT SAYS WHY. A pressure pill sits above the stage whenever the figure clears 12%: a heart whose beat rate IS the intensity (1.15s down to 0.5s, dropped entirely under reduced motion), a bar filled to the live figure, and a line naming the line being played against and how you are handling it — "Sunday · Locked in", "The cut · Rattled". A player whose bars just got quicker is owed the reason; the standing complaint against the old Luck wiring is that nothing it did could be attributed to it.
🧊 A NEW ARCHETYPE, THE CLOSER: "Ice down the stretch, lost in trouble." Mental 78 against a flat 50 in Recovery, the same shape as the Bomber's 78 Power against its 50 Accuracy. Its identity only exists because pressure ships — this golfer is worse than the field on Thursday and better than it coming down the stretch — and the 50 is a real trade now that the trees are ruled by Recovery: nerveless over a five-footer to win, helpless in the timber.
🧪 pressure.mjs, 20/20: both sweeps above, the urgency and stakes cases (Sunday's 2nd hole and round 1's 9th are both 0%), the millisecond bar timings at both ends of Mental, the pill's wording and state classes, its text contrast at 16.4:1, and no pill anywhere in the par-3 modes. One finding it caught that a source read would not have: the first cut of this hooked approachTraverseTime, which career only ever calls with a hardcoded neutral rating — the approach's bars actually run off approachSweepTime via approachBarSpeed, so the hook moved nothing and all three measured periods came back identical to the millisecond. The career autopilot was rerun for the putt and approach timings.

09/03/2026 — the trees are trees now, and the tee swings like the approach

🌲 THE PUNCH-OUT MINIGAME IS GONE. A ball in the timber used to be sent to a trouble popup (Risk It / Play It Safe), its own two-bar swing on painted trunk-and-gap zones, a trunk clatter that could leave you jailed shot after shot, and an unplayable-drop escape hatch that existed because it could. All of it is deleted — 288 lines — and a ball in the trees now plays an ORDINARY approach: same club wheel, same dials, same two bars as every other full swing, at any distance (a tree lie inside the short-game yardage takes the full swing rather than the chip, because the chip has no timber in it).
🪵 THE TREES DO THEIR WORK AS GEOMETRY. The shot's own line is walked from the ball against the DRAWN course — the same way OB and water are ruled — and wherever the ground under it is timber it asks whether the ball is over the crowns yet. Yards spent inside the trees and under the canopy are the ones that can find wood; more of them than you can thread and the ball clips a trunk and keeps a QUARTER of its carry, then lands and is ruled like any other shot (including into more trees). Deterministic on purpose: the player can see the timber and can aim out of it, so the answer belongs to the line they chose and not to a hidden roll.
🎯 WHICH MAKES AIM THE ANSWER, the way it is for a real golfer in the woods. Measured in the client on the Pachaug Forest course, 150 yards out, Recovery 55: a ball 40 yards off the centerline (just outside the drawn tree line) has 0 yards of timber on its line and flies its full 132; at 55, 70 and 85 yards offline the line is blocked for 12 to 14 yards against a 5.6-yard gap allowance, and all three clip and fly 33 to 36. LOFT is the other way out, for the same real reason — the same ball at Recovery 99 clips when flighted low and flies its full 131 when flighted high, because the high one is over the crowns in 8 yards instead of 12.
📐 THE CANOPY IS 11 YARDS and the arc is the one the game already draws: flightApexYds and CLUB_LAUNCH moved out of the renderer into shared scope so the ruling and the picture read the same trajectory (height at carry fraction t is sin(PI x t) x apex, which is exactly what animateApproach animates). The gap a player can thread is 5 yards at the floor of Recovery, 13 at the top, with Luck a quarter of the say — sized against the arc, which clears an 11-yard canopy after about 16 yards of travel, so firing straight down the hole from in the woods finds wood at any rating and the skill is how shallow an angle you need instead.
🍂 TWO THINGS THAT ONLY MATTERED ONCE THE TREES WERE PLAYABLE. A tree lie had no playLie, so lieCarryMult fell through to the CLEAN FAIRWAY multiplier and a ball among trunks and roots played at 100% — it rolls the rough band now. And the readout under it said "Fringe", because shortLieLabel had no case for a lie you were never meant to play from. An approach that finishes in the timber also stays in the timber rather than being handed back as rough: that conversion existed because the trees were a jail an approach could not be routed into, and there is no jail any more.
⛳ THE TEE SWINGS LIKE THE APPROACH. "Hit the drive" was a green slab in its own row; it is now the same blue-and-white button as the approach's, at the same left edge, the same height, the same radius, type and padding as the "Lock line" that replaces it one tap later — measured as pixel geometry across the phases (x 18, 66 tall, on both). Its row matches the controls row's 10px gap and 1fr + 33% split, so the Scout box beside it keeps its place too. And the drive's AIM step now shows BOTH bars, as the approach's does: it used to hide the carry meter until the line was locked, so a bar appeared between the two halves of one swing and pushed every control below it down the screen mid-shot.
🧪 A new probe, trees.mjs, seeds a career round with the ball in the timber and plays it: 16/16 — no trouble popup, the ordinary approach offered, nothing named Risk It or Punch out left in the live controls, the lie reading as the trees, the depth sweep and the loft pair above, and every clipped ball flying a quarter of its carry rather than being dropped where it lay. It also measures the tee's button geometry against the approach's. Two of its own bugs are worth recording: scanning document.body.textContent matched the inline script and this changelog (so "Punch out" was always "found"), and page.addInitScript accumulates, so one case resumed the round a previous case had left behind — it takes a fresh context per case now. The career autopilot was rerun for the shared approach path.

09/02/2026 — watching looks like watching, and a new day opens on the daily

🎥 AN OPPONENT'S TEE SHOT IS WATCHED FROM OFF THE LINE. Their replay used the player's own camera — dead behind the ball, straight up the hole — so watching was indistinguishable from playing. The eye now swings 22 degrees round the ball while the look axis follows 55% of the way, which puts the ball on one side of the frame and their landing area on the other: the hole runs diagonally and the shot crosses it. 22 is the most the geometry allows: the ball's angle off the axis is about SPEC_AZ x look / (look + back), leaving it at 9.3 degrees and the landing at -11.4 against a 12.6-degree horizontal half-frame (atan(tan(0.4) x 9/16), the tighter of the two axes on a phone). It eases in on the same beat as the aim pan — one 0-to-1 progress driving both, so the stage still gets exactly one draw per frame — and fades out on the descent dolly's schedule, handing the landing to the tower framing that already existed. The camera sits on the side the ball moves AWAY from (read once off the posted shot's lateral, before it flies; a dart at the pin alternates by hole), because a miss toward the lens is the one case that pushes the ball to the far edge.
📐 IT IS A PURE ORBIT, so the vertical framing is untouched: rotating about the ball preserves the eye-to-ball and eye-to-target distances, and the 4.0-up / 9.5-back address is the par-3 one to the yard. Measured in-browser off the recovered view matrix, my own address camera against theirs on the SAME hole: radius identical to 0.001 yd, eye height to 0.000. Their azimuth eases 0 to 22 while mine stays at 0.0.
📊 THE MATCH SCORE TAKES THE DIALS' BAND while their shot is on the stage. The Shape/Loft sliders and the club wheel were the striker's setup, and on a replay they were wrong twice over: still live to the touch (wheel and sliders keep their handlers, so a watcher could drag someone else's setup) and useless to read, since a spectator does nothing with another player's loft. The band now carries both point totals, the holes tally and the hole number, with the club they pulled as plain text. Inert by construction, and its life is exactly the cover's, so it can never be left behind when the ball comes back to you.
🎯 THE NUMBER TO BEAT NOW SURVIVES THE TWO CASES IT MISSED. My own carded hole is kept locally as I post it (clashHoleCarded), because the doc's copy only lands on the next poll and the stage lock holds polling off for the whole of their replay — a hole I had just won showed no target at all while they played against it. And the strip prices the REPLAYED hole, not the doc's current one: an unwatched shot can play back after the turn has come to me, and the figures were being read off a hole nobody had played yet.
🌅 A NEW DAY OPENS ON DAILY DARTS. Free Play was the right landing for a link that resumes nothing, but a returning player's first visit of the day had to go and find the switcher to reach the one mode that expires. Boot now deals today's darts and raises its card over the live round — the Blitz's arrival pattern, where closing the card by any route leaves you on the first tee. Every claim on the arrival still wins: a resumed round of any kind, a challenge link, a duel invite, the Blitz's test link. Signed in, it waits on the account's daily record before dealing, so a daily played on a phone this morning is not dealt again on a laptop this evening; the deferred open re-checks that nothing has started and gives up after 12 seconds, so a slow network cannot yank a player out of a round. NOT on a first-ever visit: the daily is one attempt a day and is not spent learning which end of the club to hold.
🧪 clashwatch is 27 checks now, including the camera measurements above and the ball's own position read out of the vertex stream (the props buffer uploads 11 floats a vertex and the in-flight ball wears a colour nothing else does), projected to normalised device coordinates so BOTH axes are checked against their own half-frames — the horizontal, which this change moves, worst 0.51 of the way to the edge across every replayed flight. The band's five text styles are contrast-measured through every ancestor background: 8.11:1 for the small text, 16.11:1 for the figures. A new probe, newday.mjs, boots the public page in seven states (fresh day, a Free Play round in progress, the daily already played, a first-ever visit, a career round saved, a daily mid-round, the tester link) and checks which mode each one lands in: 17/17. clashrun and clashduel rerun green.
📋 Noted, not changed: a par-3 flight leaves the TOP of the frame at its apex — measured at 1.0 to 2.3 times the half-frame — and it does so identically on the player's own shots and on a replay. That is the shipped shot framing, not something this change introduced, so it stays as it is.

09/02/2026 — the clash, watched properly

🎯 THE SCORE TO BEAT IS ON THE STRIP. When the other side has already carded the hole, its points are the whole point of the shot you are about to play, so they ride beside whose ball it is: "Your ball · 4,151 to beat" — and, while they play against yours, "Kramer Lyle's ball · your 2,073 to beat". Read straight off the match doc, so both screens agree.
🙈 NO AIM CUES ON A REPLAY. The approach's dashed cue and the green's dashed line are the striker's READ of the shot, and on the spectator's screen they gave the line away before the ball went — and drew over the flight's setup beat. Both builders now stand down while a replay owns the stage (clashBotBusy). The club and the dials stay: those are theirs to look at.
🎥 THE BOT'S CAMERA LOOKS WHERE ITS BALL GOES. A striker's flight develops toward the point they aimed at and their camera yaw IS that aim, so the ball climbs up the middle of their screen — and a human's replay carries that aim. The bot's aim was a random few degrees unrelated to its flight, so its shot looked like it came from off centre however faithfully the camera panned to it. Its aim is now the angle that produces its lateral (the inverse of lateralAim = tan(aim) · span), and its fixed flight aim is the same value, as a human's is at the strike.
⚖️ THE BOT'S HIT-OR-MISS IS RULED BY THE GREEN'S REAL SHAPE, at the spot the ball is drawn coming to rest. It was decided by the INTENT that generated the shot: a "green" rest up to 37 ft from the pin sat off a narrow or oddly-shaped green — the spectator watched the ball finish on the fringe while the verdict said it hit — and a "miss" 13 yards wide landed on a wide one and was called a miss. greenNormAt reads the rest point through the same normalised-radius test the real resolve (landRadial) and the mesh use, so the picture, the ruling and the words come from one place.
🧪 clashrun asserts the "to beat" figure on the strip equals the opponent's carded points from the server doc whenever I play second; clashwatch asserts every bot tee shot's posted aim equals the angle of its own lateral (ad = la = atan2(aimLat, landFwd) to within 0.1 degrees) and pins both cue builders to the replay lock in source. clashduel rerun.

09/02/2026 — nothing carries out of the Blitz

🛑 CONTINUE ON THE BLITZ SUMMARY DEALT HOLE 4 OF A NINE-HOLE RUN, with the Blitz's three scores still on the card and its total still running — a player could carry a 3-hole Blitz into Free Play and keep going. The summary drops blitzActive as it banks the round, so by the time Continue reached the round boundary roundHoles() read nine, holeIdx was 3, and the tail went holeIdx++. The summary now marks itself as a finished Blitz's, and Continue takes a path of its own: the finished run is cleared (its three holes are already in the Blitz's ledger) and NOTHING of it survives.
↩️ …AND THE PLAYER GOES BACK TO WHAT THEY LEFT. Starting the Blitz records where the player was — career, the daily, a free round — and parks the round they leave; Continue on the summary hands it back: the clubhouse with its Resume button, the daily at the hole it stood on, the free round at its hole (a new park, since free play used to be dealt over by the Blitz's resetRun with nothing to come back to). Nothing to go back to means a fresh Free Play. The button says which: "Back to career", "Back to the daily", "Back to your round", or "Free play". The origin is judged off what STORAGE holds rather than the in-memory flags — from the range, dailyActive is already off while the daily the range parked is still in RUN_KEY — and is stored, so a reload mid-Blitz does not forget it.
⚔️ LEAVING A DUEL GOES BACK TO WHERE THE PLAYER CAME FROM. exitClash called restoreRun with career allowed, which prefers the career key whenever one exists, so a player who entered from Free Play with an old tour event saved was dropped into the clubhouse. The duel now remembers whether it was entered from career, and resumes RUN_KEY — free play, the daily, or the Blitz saved on entry — otherwise.
🧪 scratchpad/carry.mjs plays three full Blitzes: from Free Play two holes in (Continue resumes the SAME round at hole 3, same seed), from the daily one hole in (the daily resumes at hole 2), and from a career tee (the clubhouse, with Resume) — asserting in each that the run in storage is not a Blitz and holds the pre-Blitz hole count, never that plus three. blitzrun asserts that with nothing parked, Continue deals a fresh Free Play (zero holes, hole 1, no clock); clashrun asserts leaving a duel does not land in the clubhouse when the player came from a par-3 round.

09/02/2026 — the birdie ladder counts birdies, not holes

🪜 500 FOR YOUR FIRST BIRDIE, 1,000 FOR YOUR SECOND, 2,000 FOR YOUR THIRD — in the Blitz and the Clash. The ladder was indexed by HOLE: a first birdie on the third green paid 2,000 and a third one on the first paid 500, which rewarded where you happened to hole it rather than the run of holing them. It now indexes the birdies already made this round (or this match), so a player who has holed nothing is still playing for 500 on the last green and a player on a run is playing for 2,000. An ace is a birdie and climbs the ladder like one.
⚔️ THE CLASH RUNS THE SAME LADDER. It paid a flat 1,000 for any made putt; it now climbs 500 / 1,000 / 2,000 off each side's OWN birdies so far in the match, priced identically on both screens from the shared match doc (a holed putt, or a tee shot that went in). The bot climbs it off its own birdies too, and its replayed verdict says the real figure instead of a hard-coded +1000. A hole-out in the Clash is paid as the made putt, as it already was in the Blitz.
🗣️ The Blitz trait line says which rung you are on — "birdie putt +500 · 1st birdie" — and the Aurora's clash line, which existed only to explain the flat 1,000, now says the ladder value.
🚪 THE DUEL DOOR HAD THE BLITZ LEAK TOO, and there it was a scoring bug. enterClash cleared dailyActive but not blitzActive, and tallyFantasyHole picks the proximity curve (7,500 ceiling against 2,500), the ace value and the multiplier boost off that flag — so a player who entered a duel from a live Blitz, which the master link deals on arrival, scored every hole on the Blitz economy while the opponent was priced on the normal one. clashduel caught it as the host's trait bar reading the Blitz ladder while the guest read the world. The flag now comes off at the door with the clock; the Blitz waits in storage and comes back when the match ends.
💣 …AND A STOPPED CLOCK HAS NO SHOT ON IT. blitzStopTicking cleared the ticker but left blitzShotStart standing, so the next start — the hop back from a duel or from Free Play — ticked once, saw a "shot" begun minutes earlier, and carded the Blitz hole OUT OF TIME on the spot, a shot the player never got to play. It surfaced as a lifetime-stats write across a duel (one missed green, on the Blitz's world) once the duel door stopped leaking. The shot in progress is now dropped when the clock stops, which is how a reload already treats it; the round total is kept.
⏱️ A RESUMED BLITZ GETS ITS CLOCK BACK. Only a fresh deal and a park hand-back started the shot-clock ticker; restoreRun resuming a live Blitz — a reload mid-round, the return from a duel — did not, so the pill was gone and the sixty seconds were not enforced. restoreRun starts it itself now, wherever the round comes back from.
🧪 blitzrun's ladder checks are re-keyed: every announced value equals the rung for the birdies made before that hole, and every paid bonus the same; a source check pins the bonus to a birdie COUNT rather than holeIdx, since a round that misses every green cannot exercise the arithmetic. scratchpad/ladder.mjs seeds a live Blitz with two birdies banked and reads hole 3's line (+2,000 · 3rd birdie), then the same with none (+500 · 1st — where the by-hole rule said 2,000). blitzrun also asserts the clock pill is back after its mid-round reload, and clashrun asserts no Blitz clock or ladder line inside a duel. clashrun, clashduel and clashwatch rerun for the bot's and the humans' pricing.

09/02/2026 — nine career bugs that were one leaked flag

🏆 A BLITZ FLAG WAS LEAKING INTO CAREER. Entering career from a live Blitz (or daily) never cleared blitzActive, and that flag is read everywhere the career shares: roundHoles() answered 3, so a career round ENDED after three holes, roundNum advanced, careerAbsHole() jumped to the back nine (hole 10 straight after hole 3), the simulated field ran on to "thru 28" against a player on hole 4, and the Blitz shot clock kept ticking over the clubhouse and the tee. The autopilot reported it as nine separate bugs — three hole-order, six round-number — and every one of them was this. Live on main since the master link began dealing a Blitz on arrival, which is also why the identical nine showed up on the pre-change baseline.
💀 IT COULD ALSO WIPE A ROUND. restoreRun's career branch reads roundHoles() to decide whether a saved round is FINISHED, so with the flag leaked a career round three holes in was judged complete and cleared on resume.
🅿️ PARKED, NOT DROPPED. Both career doors (enterCareer, startCareerRound) now run parkLiveShortRounds: a live daily or Blitz is saved while its flag still stands and moved to its park slot — the same order setGameMode uses — then the flags come off and the clock stops. Dropping the flag alone would have let a Blitz → Career → Blitz hop re-deal the day's three holes, which is the unlimited retry the parking exists to close; instead the switch back hands the same round back at the same hole. The restore branch clears the flag itself as well, so it is safe on its own.
🔇 THE 76 CONSOLE ERRORS WERE THE SANDBOX, NOT THE GAME. Every one was the browser's "Failed to load resource" for grandslamchallenge.app, which the test container's proxy refuses outright; the game already swallows each of those syncs (fire-and-forget with a catch) and shows the player nothing. Tallied by path they were 69 × /api/par3/aces and 9 × /api/par3/leaderboard. The autopilot now answers the API locally by default (the way the clash suites do), with CAREER_NET=real to let the calls out, and names what was asked and what failed, so a console line in that suite means something again.
⏳ ONE SMALL CLIENT CHANGE FELL OUT OF THAT TALLY. The 69 were the ace tracker's flush: a tee-shot report queues and posts, and when the post fails the queue is kept for the next report — which meant a dead network drew one doomed POST per tee shot for as long as the round lasted. A failed flush now holds off for a minute; the queue is intact and still goes out on the next report after the hold, on the "online" event (which clears the hold — the network is back), and on launch. Nothing was ever lost; it was just noisy about it.
🧪 careerrun checks the leak DIRECTLY at the first tee (no clock pill, HUD reads Round 1 of 4) so a regression is named for what it is rather than diagnosed from hole-order flags twenty minutes in. scratchpad/hop.mjs plays one Blitz hole, steps into career, checks the clubhouse and the tee, steps back and asserts the SAME round resumes at the same hole with no fresh welcome card. fixcheck 14/14, blitzrun 94/94, and the full career autopilot: 18 holes to the cut, 0 bugs, 0 console errors, 0 page errors — with its mid-hole reload probe now cutting only when the player holds the ball (it twice reloaded onto a hole that had just finished and called a banked hole lost); cut on a decision at hole 17, shot 2, 213 yd, it resumed at hole 17, shot 2, 213 yd.

09/02/2026 — watching a duel: the replay is a broadcast, not a glitch

🎥 THE OPPONENT'S FLIGHT WAS BEING DRAWN BY THREE THINGS AT ONCE. Their tee shot replayed with the stage still in approachChoice — the phase the watcher's own screen sits in while picking a club — so everything that repaints an idle decision screen kept running under the animator: loopBody's ~30fps idle redraw, the weather loop's still-scene repaint, the dashed aim cue and the club wheel. Each idle frame draws the ADDRESS ball at the tee and wipes the in-air streak, so between the animator's frames the ball kept snapping back to the tee. Measured on a bot match through the real client: 2-3 scene renders a frame on 46 of 58 flight frames, and 66 of 111 on the putt. The replay now enters "flying" (and the putt "rolling") before it animates, exactly as resolveApproach and resolvePutt do for the striker, and every one of those repainters stands down the way they do for them. After: one render per frame on every flight, 0 double frames.
📐 THE CAMERA PANS TO THEIR LINE INSTEAD OF CUTTING. Their aim and camera arrived as one state and the view teleported there, which read as the shot coming from nowhere. clashPanTo eases aimDeg from wherever the watcher's camera is to the angle they held at the strike, redrawing every frame over 700ms, then holds so the club and dials can be read, then the ball goes. The green does the same before a putt, swinging to the rotation they read from over 650ms. Measured: 15-16 distinct camera positions through the setup beat where there was one.
🤖 A BOT NOW ROTATES THE GREEN TOO. Its tee shot already carried a small invented aim so the camera had somewhere to swing; its putt posted no pan at all, so against a pro the green never moved. A human's putt posts the pan they really dragged to; the bot's invents a modest one the same way.
⏭️ NO SKIP BUTTONS ON SOMEONE ELSE'S SHOT. The flight's Skip-cinematic and the putt's Skip control were shown on the watcher's screen, sitting over the "…'s tee shot" pill. Both are the striker's. Those buttons are also what ARM their flags (showSkip sets cineSkip = false), so a replay that no longer shows them clears the flags itself — otherwise a Skip the watcher pressed on their own last shot fast-forwards the opponent's to its final frame and they never see the ball fly. That one was measured before it shipped: a 2s replay with a single drawn frame.
🔇 TWO IDLE REPAINTERS STAND DOWN WHILE A REPLAY OWNS THE STAGE. The pan beats run under approachChoice/puttRead by design (the dials are theirs to read), so the flight/rolling fix does not cover them — loopBody's idle redraw and the weather loop's were still landing between the pan's own frames, two renders on half the frames of every pan. Both are gated on clashBotBusy, the existing "a replay is on stage" lock.
🧪 scratchpad/clashwatch.mjs plays a bot match against the local backend and MEASURES the replay from inside the page: renders per animation frame (a gl.clear hook, with the calling function tallied so a second draw source is named, not guessed), distinct camera positions per beat (the view matrix's right vector AND translation — the right vector alone is constant through a dead-straight shot and read as "never moved"), the Skip buttons' visibility, and a continuous journal of the cover pill independent of the driver. Judged against the bot's real posted aims from the server doc, so a hole aimed within 0.3 degrees of straight is not asked to pan. Alongside it: clashrun (a full bot match audited against the server, 0 bugs), clashduel (two humans each replaying the other's four shots, 0 bugs) — both repointed at the mode switcher, since they still pressed the retired #modeClash button — blitzrun 94/94 and puttui 19/19, which share the two animators that gained the replay gates.

09/02/2026 — the blitz clock stays in the blitz

⏱️ THE SHOT CLOCK NO LONGER RUNS ON THE PRACTICE GREEN. enterRange cleared dailyActive and tutorialMode but never blitzActive — only setGameMode did that — so stepping into the range from a live Blitz left you flagged as being in one, with the sixty-second clock ticking on a green that scores nothing. Measured before the fix: the pill up and counting 52 down to 48 across four seconds, and a rehearsal putt could be timed out on it. blitzActive now comes off beside dailyActive and blitzStopTicking goes with it.
🎓 THE TUTORIAL HAD THE SAME LEAK, from the same three lines, and is fixed in the same pass. startBlitz's own resume branch names the two doors together ("from the range or the tutorial"), so fixing one and leaving the other would have left the identical bug one door over.
🔐 SAFE TO CLEAR because the round is banked one line earlier, while its flags are still live, and every way back reads the flag off STORAGE rather than off the variable — startBlitz's range branch and setGameMode both go through restoreRun. The suite confirms it: the daily still parks when the Blitz takes over, the Blitz still parks in its own slot on the way back, and a reload still resumes a three-hole round at the right hole.
🧯 The range arm of puttPreviewOffered stays, and is now belt and braces rather than load bearing. The range is genuinely never a mode the no-preview rule is about, so it should not depend on another function having tidied a flag up — which is the assumption that failed the first time.
🧪 The known-issue note in puttui is now an assertion: the clock is gone on the practice green AND the round total is not still accumulating behind a hidden pill. 19/19, and blitzrun 97/97 with the parking and resume paths that this touches.

09/01/2026 — the putt read: one button in the short modes

🗣️ THE READ BUTTON SAYS "HIT THE PUTT" IN EVERY MODE, where it said "Continue". Continue is what a dialog says; this is the control that commits you to the stroke, and every other button in the game already names the shot it plays — Hit the drive, Play the approach, Play the chip.
🚫 NO PREVIEW IN THE BLITZ OR THE DUEL. Both are short-form and timed — sixty seconds a shot in one, someone waiting on you in the other — and a rehearsal of the read is a slow, deliberate tool in modes whose whole proposition is that the read IS the decision. The button is GONE rather than greyed: a disabled control still occupies the row and still poses a question. .btn.play is flex:1 against the preview's flex:0 0 auto, so removing it hands the whole row to Hit the putt with no width rule of its own — measured at 357px of a 357px row, against 163px when it shares.
🔒 NOT OFFERED MEANS NOT AVAILABLE. previewPutt refuses on its own rather than relying on a hidden button, and both drag handlers that re-enable the control ask the same question first. A hidden-but-live control is the kind of thing that comes back through a path nobody remembered to hide, so the suite proves it: it un-hides the button in a live Blitz, re-enables it, clicks it, and asserts nothing happens.
🐛 THE RANGE HAD TO BE EXEMPTED, AND FINDING OUT WHY TURNED UP SOMETHING ELSE. enterRange clears dailyActive and tutorialMode but NOT blitzActive — only setGameMode does that — so a player who steps into the practice range from a live Blitz is still flagged as being in one. A rule reading blitzActive alone therefore stripped the preview from the practice green, which is the one place in the game that exists to rehearse. The range is checked first and always wins: nothing out here is timed or scored, whatever flag is left standing behind it.
⚠️ KNOWN, PRE-EXISTING, NOT FIXED HERE: that same leaked flag leaves the BLITZ SHOT CLOCK RUNNING on the practice green. Measured stepping into the range from a live Blitz: the pill is up and counting, 52 down to 48 across four seconds, on a green that scores nothing — and a practice putt can be timed out. Present on main, where enterRange mentions neither blitzActive nor blitzStopTicking, so it is not a consequence of this change. The fix is clearing the flag in enterRange the way setGameMode already does, which is a change to shipped par-3 flow and is being asked about rather than smuggled in here. puttui reports it on every run.
🧪 scratchpad/puttui.mjs stands on a real green in each mode instead of reading the branch. Reaching one is the hard part: a missed green in the Blitz cards 0 with no putt at all, so it walks the day offsets until a green is actually hit. 17/17, plus blitzrun at 94/94 and the career autopilot for the setPhase change.

09/01/2026 — the clock no longer runs behind the welcome card

⏸️ THE ROUND WAS BEING TIMED WHILE THE CARD EXPLAINING THE TIMER WAS STILL UP. startBlitz deals the round before the welcome card is shown, which is deliberate — the scene is built and the hole is ready the instant the card closes, and that is the whole promise of a one-minute mode. But newHole runs setPhase, and setPhase starts the shot clock, so a player reading the card was already being charged. Measured on a fresh guest: 6 seconds of round time gone and the 60-second shot clock down to 54 before they had seen the hole, on a card whose last line is "your total time over the three holes acts as a tiebreaker". Worse for a first-time visitor, who gets the Welcome to FlagHunt card on top of it and has two things to read before the ball is theirs.
🔒 IT IS A HOLD, NOT A PAUSE, and the distinction is the whole design. The hold is engaged once, when the round is dealt, and released once, when the welcome flow ends — closing the card by its ×, by Play or by the scrim all land on the same release. There is deliberately no way to re-engage it mid-round: a clock that any modal could stop would make "open help, read the green, close help" a free timeout, which is a worse bug than the one being fixed.
🧵 THE RELEASE IS WIRED AT THE CHOKE POINT rather than at each caller. blitzStartTicking is the single place that means "a blitz round is live", so it clears a stale hold on the way past and startBlitz re-engages one immediately after — which means every OTHER route in (a parked round handed back, a reload resuming mid-round) is correct without knowing the hold exists, and so is the next one somebody writes. The paths through openBlitzWelcome that show no card at all — already played today, resuming, refused — release explicitly, because nothing else would.
🧪 The suite sits on the card for five seconds and asserts BOTH clocks are still where they started (the round total at 0:00, the shot clock reading "—" rather than 60 counting down), then closes it and asserts both start — the round total climbing and the shot clock counting down from a full 60. Holding and stopping look identical for five seconds, so checking only the first half would pass on a clock that never runs at all. bzshot confirms the same on the guest path, through both cards. 94/94.

09/01/2026 — the Blitz result reads as one thing

⏱️ THE ELAPSED TIME SITS BESIDE THE SCORE ON THE BOARD, "4,242 • 1:01", instead of on its own line underneath it. It is the tiebreaker on this board, so it belongs next to the number it breaks ties on; stacked below at 11px and 0.62 opacity it read as a footnote about the round rather than as part of the result. The row is unchanged otherwise — the score column simply carries both halves now.
🐛 THE RE-VIEW SHARE WAS DROPPING THE CLOCK, and only the re-view. blitzShareText takes the elapsed time as its fifth argument; the round-end card passed it and the PLAYED TODAY card did not, so copying your result any time after the seconds right after finishing gave a line with no time in it. info.lastMs was already in scope — the ⏱ line directly above the call reads the same value. The shared shareTextFor takes three arguments and ignores the extras, so the one call site that serves both modes is safe.
🔗 The share text now uses the same bullet the board row does, so the two surfaces describe a result identically: "41,250 pts • 1:28".
🗣️ THE WELCOME CARD LEADS WITH WHAT THE MODE IS, not with its mechanics. It opens by placing the Blitz against a mode the player already knows — a shortened Daily Darts for a few spare minutes — then names the three ways it differs (miss the green and it is a fail, higher proximity scores and multipliers, more for birdies), then the clock and the tiebreaker. The old copy opened on "Three holes, same for everyone today" and printed the birdie ladder's exact figures, which is a rules table for a mode nobody had played yet.
🧪 blitzrun stops scraping the share template and reads what a player would actually paste: the context grants clipboard permission, the suite presses Copy on BOTH paths and reads the clipboard back, and asserts the re-view line is byte-identical to the one the round-end card gave. That is the check the old test could not make — the template was always correct, the CALL was the bug, and a source scrape cannot see a missing argument. A source check backs it by requiring every call site to pass a time; validated by removing the argument again and watching it go false. The copy assertion moved off the ladder's literal figures, which the new text describes rather than enumerates, onto the three promises the card now makes — the figures are still verified against the shipped constants and against recomputed card arithmetic. 90/90.
📸 scratchpad/bzshot.mjs renders the welcome card as a fresh guest meets it: empty storage, no account, nothing pre-dismissed, and both clocks sampled at every step.

09/01/2026 — one door, and the retired links say so

🔑 ?blitz=, ?clash=, ?career= and ?nav= ARE RETIRED. ?beta=<passcode> is the only link that opens anything. One door is easier to rotate, easier to hand out and easier to reason about than four with different reaches, and the per-mode doors had already outlived their last real job: they existed so that a locked row could still be SEEN, and the public menu is that view now.
📣 A RETIRED LINK SAYS SO rather than failing silently. Whoever held one is the least likely person to work out why the game suddenly looks ordinary — they would see the plain menu with three Soon rows and reasonably conclude the modes had been pulled. The notice reads "This link is unavailable · the test link you used has been retired · if you had access before, ask Kev for a new link". Matched loosely, with or without a value, so a mangled link still gets the message instead of silence; suppressed when ?beta= is also present, where the visitor is already inside; and the param is left in the URL, because clearing it would make a reload look like a different (working) link and lose the explanation.
🤝 INVITE LINKS MOVE WITH THE GATE: a duel invite is ?beta=<passcode>&duel=<code> now. Invites already in circulation carry ?clash= and will hit the notice instead of joining. That is unavoidable when the param goes, and it is the same cut that rotating CLASH_PASS always made.
🧹 NOTHING AUTO-STARTS ON ARRIVAL, so the *_LINK / *_OPEN split that ?blitz= and ?career= needed collapses back to one flag per door. Every mode is entered the same way now, through the switcher, which also means the first-visit welcome is no longer skipped by a career link.
🧪 Every harness enters through the one live link. blitzrun and careerrun walk in through the switcher, since the links they used to ride are gone, and blitzrun additionally asserts that the retired link raises the notice, that it still unlocks nothing, and that a retired param alongside ?beta= does NOT nag. 63/63.

09/01/2026 — career joins the switcher

🏛️ THE CLUBHOUSE GETS THE CHIP, in the slot the golfer's name held. Career was the one mode you could switch INTO and not out of once the flat row went away, because its clubhouse is a full-screen overlay that hides the top bar. Two chips, one menu — and this is NOT the duplicated mode list that came out of the ☰ card: one NAV_MODES, one renderModeMenu, one open/close, and one function writes both triggers in the same pass. The panel anchors under whichever chip opened it; the clubhouse copy sits about 45px lower, so a hardcoded anchor put the panel over the header it belongs to. The header grid was equal thirds, which clipped the chip to "CAREER M…" — the pills only ever need their content width, so that column is auto now and the slack goes to the chip. The name is not lost: the line under it reads "Kevin · Bomber · Rookie".
🔑 THE MASTER LINK LANDS ON FREE PLAY. restoreRun checks the career key first, so a tester with a career round saved was dropped straight back into the tour every single time they opened the one link they had been given — the switcher was right there and they never saw it. ?career= still resumes into the tour, which is what that link is for, and nothing is lost either way: the round stays under its own key and the Career row hands it back through the clubhouse's Resume button.
🔓 THE CAREER HOLD IS GONE, AND IT SHOULD NEVER HAVE EXISTED. Yesterday's build locked every other row mid-career-round, on the stated belief that a career round lives in gsc.run.v1 like everything else and would be dealt over. It does not. saveRun writes career to CAREER_RUN_KEY and everything else to RUN_KEY, resetRun touches neither, and restoreRun's own comment has read "survives a hop to another mode" the whole time. The hold was blocking a switch to prevent a data loss that cannot happen. Career is a toggle like every other mode, and the suite proves it by playing a shot, switching to Free Play, switching back, and diffing the career key byte-for-byte across the round trip.
🐛 …AND THAT SEARCH TURNED UP A REAL ONE. restoreRun prefers the career key, so it hijacked callers that specifically wanted a par-3 round back: tapping Free Play on the way out of the range with a career round saved dropped you into career instead. It was unreachable while career sat behind its own per-mode door, and became reachable the moment one link started opening every door. restoreRun(false) opts out for the range return and both parked-daily resumes.
🧭 The clubhouse now counts as career for the chip. gameMode only flips to "full" when the round starts, so a chip reading it alone said "Free Play" while rendered inside the career clubhouse.
🧪 navrun.mjs is 182 checks, twenty-one of them new. The old mid-round HOLD section was deleted rather than adapted — it asserted a rule built on the wrong premise. One new check needed rewriting rather than the code: it booted the master link expecting Free Play in a context where an earlier section had left a live blitz, and a same-day round in progress SHOULD resume on any link. The career autopilot was rerun for the restoreRun change.

09/01/2026 — the menu, trimmed

🔢 THE ORDER IS WHAT YOU CAN DO, THEN WHAT IS COMING. Practice Range moves up under Daily Darts, so the three shut doors are one contiguous block at the bottom instead of Career sitting above an open mode. Same order on the beta link — a tester and a player should be looking at the same list in the same places, or the tester is not testing the shipped thing.
✂️ A SHUT DOOR SELLS NOTHING. The unreleased rows drop their descriptions on the public link: there is no point pitching a mode nobody can open, and the row reads cleaner as name plus SOON. The panel is about 130px shorter for it. The descriptions come back on ?beta=, where the modes are not gated, which falls out of the one rule rather than needing a second branch. The ACCESSIBLE name keeps the description either way, because dropping it from the visual is a density decision and not a reason to tell a screen-reader user less about what a mode is.
👀 PRESSING A SHUT DOOR SAYS "Coming soon 👀", in red. The long "it is in testing now and arrives here when it is ready" went with the descriptions. Red rather than the gold this menu already uses for "there is something here for you" — a closed door is the opposite of that — and #ff8a70 rather than the house red --flag (#e0654a), which is the right colour but measures 3.82:1 on this panel and fails body text; this one measures 5.68:1 and the suite asserts it.
🏷️ THE "NOW" AND "NEW" BADGES ARE GONE. The filled row already says where you are more loudly than a word beside it could, and "New" on Daily Darts was labelling the permanent condition of a mode that is new every single day — it never came off, so it had stopped meaning anything. aria-checked still carries "this is the current one", which is the one reader the highlight does not reach. The played tick stays: that one changes during the day.
🍔 THE ☰ MENU IS NOT NAVIGATION ANY MORE. It held a second copy of the mode list, which is a second thing to keep in step with the first and a second place for the two to disagree — and they already had: Blitz was hidden on that card while the switcher showed it as Soon, and the card's own Free Play was guarded to daily/blitz/range so it did nothing at all from career. The chip is the navigation. The card keeps what it was always best at: Welcome to FlagHunt, what the game is, your account, the tutorial and how to play.

09/01/2026 — the switcher ships; the three new modes read "Soon"

🚪 THE SWITCHER IS NO LONGER GATED. It is the navigation on every link, and the three unreleased modes appear in it as locked "Soon" rows rather than being hidden. The point is that production IS the shipped menu with three doors shut — not a cut-down build that has to be kept in step with the real one — so the locked-row design that was built for testers is now the thing players see. The ?nav= passcode went with it: the public link is the locked-row view, so the one thing that gate existed to make visible no longer needs a key. ?beta=<passcode> still opens all three.
🗣️ THE COPY IS THE PLAYER'S, not the tester's. A shut door said "Opens with the Blitz test link", which is meaningless to someone who has never seen a test link and quietly advertises that one exists. All three now say "Coming soon", the same words the landing card has always used for Career. The SOON badge carries it with no tap needed — a badge nobody has to press is the difference between a list you can read and a list you have to poke — and pressing the row still adds the fuller line, so it is not a control that looks live and does nothing.
⚖️ THE GATE OUTRANKS THE HOLD when a row is both. Mid-career-round, every other row locks with "Finish or restart the career round first" — but saying that about a mode that is not released yet implies finishing the round would let you in. An unreleased row says Soon whatever else is going on, and the 🔒 glyph is now reserved for a mode that exists and is merely blocked right now.
🃏 THE LANDING CARD AND THE MENU NOW AGREE. Blitz was hidden outright from the landing when its door was shut, on the very screen where Career has always said "Coming soon" instead; with the menu showing all three as Soon, that would have been two surfaces disagreeing about the same mode. It is a locked "Coming soon" row there too.
🧪 navrun.mjs is 166 checks, with twenty new ones on the public view alone: the chip ships to everyone, the flat row is gone, the three rows are locked and badged Soon, no locked row mentions a test link or a passcode, every row including the locked ones is hittable, pressing one explains rather than switches, an open row still routes, and the landing card agrees. A bare ?beta and a wrong passcode are checked too, but "unlocks nothing" now means the rows stay locked rather than the menu being absent.

09/01/2026 — the mode switcher

🧭 SIX MODES DO NOT FIT ACROSS A PHONE. The flat row was already down to 7px type at the narrowest breakpoint with five buttons and the icon cluster; a sixth would have landed on top of the icons. So behind ?nav=<passcode> the row collapses to ONE chip naming the mode you are in, and the modes move into a panel with room for a name, a line saying what the mode is, and an honest lock state. With the gate shut nothing changes: the flat row is byte-for-byte what shipped, which is what the first four checks in the suite assert.
🔑 ONE LINK FOR EVERYTHING UNRELEASED: ?beta=<passcode> is now the master key, and the only link that needs handing out — the mode switcher, the Blitz, the Duel and Career all answer to it. The narrower per-mode doors still work, kept for one reason that is not nostalgia: the switcher's whole design is showing a locked mode AS locked, and the master key unlocks everything, so ?nav= alone is the only thing left that can put the menu up with three rows locked, which is the state the suite asserts.
🚪 A DOOR BEING OPEN IS NOT A LINK AUTO-STARTING ITS MODE, and the two had to be split the moment one key opened several. ?blitz= deals the three holes on arrival and ?career= walks straight into the tour, so a single key meaning both would boot into both at once — measured, that is the blitz shot clock ticking over the golfer-creation card, which is exactly the state a combined test URL produced while this was being built. The *_LINK flags mean "this mode's own link was used" and only those auto-start; the *_OPEN flags govern availability. Arriving on ?beta= lands on Free Play with the switcher up, which is the point of having a switcher: the tester picks. The first-visit landing follows the same rule, skipped because career's own link already put you somewhere rather than merely because career's door is open.
🔒 A LOCKED ROW IS NOT A DEAD TAP. It stays in the list, dimmed and dashed with a lock badge, and activating it opens a line saying what opens the door — tapping again folds it away, and a second locked row replaces the first rather than stacking. It is deliberately NOT aria-disabled: the row genuinely responds, and marking it disabled lies in both directions, hiding a working control from assistive tech and refusing automation. Playwright would not click it, which is how that was caught. The lock is carried instead by the badge, the dashed dimmed row, aria-checked, and an accessible name that says "locked" and why — so a screen reader gets the whole answer without activating anything.
🎛️ THREE STATES, KEPT SEPARATE, because they are three different questions the flat row's single "active" class conflated: where you ARE (the Now badge and aria-checked), whether the door is OPEN (the lock), and whether today still has something WAITING (the New badge on an unplayed daily or blitz, plus a gold ring on the chip). A finished daily shows a tick instead.
⌨️ FULLY KEYBOARD-DRIVEN. role=menu with menuitemradio rows and a roving tabindex, so the menu is one tab stop and Tab leaves it rather than walking six rows. Arrows rove and wrap, Home/End jump the ends, Escape closes and returns focus to the chip, and typeahead matches any WORD of the name — "1v1 Duel" begins with a digit, so first-letter-only matching left it the one mode no key on the keyboard could reach while "d" quietly went to Daily Darts.
🐛 SPACE WOULD HAVE HIT A SHOT WHILE YOU PICKED A MODE. Space is the game's universal "lock the bar" key on a window listener, and the rows are real buttons, so Space on a focused row both fired the row's click AND swung the club — worse, its preventDefault swallowed the row's click first, so the visible outcome was a shot the player never asked to hit and no mode change. The listener now stands down while the menu is open, and only while it is open. Confirmed by removing the guard and watching the control fingerprint go from "Play the approach" to "Lock line".
🐛 LEAVING A LIVE BLITZ FOR FREE PLAY DID NOTHING, and predates this menu. setGameMode's "already here" guard spelled out !dailyActive but never !blitzActive, and the blitz runs with gameMode "fantasy" and its own flag — so the guard returned early AFTER the block above had already parked the round. The blitz stayed on screen with blitzActive still true while a parked copy of it sat in storage, which is why tapping Free Play during a blitz read as a button that does nothing. Caught by the new suite, not by reading.
🏆 THE SWITCHER IS NOT A ONE-WAY DOOR. Career clears the flat row for its own chrome, and hiding the chip there too meant you could switch INTO career and have nothing to switch back with (the ☰ landing's Free Play is guarded to daily/blitz/range and does nothing from career). The chip is one control and fits beside career's icons at 393px and at 320px, so it stays up. A career round in progress lives in gsc.run.v1, the same slot every other mode deals into, and there is no career park — so rather than lose it quietly, the other rows lock mid-round with "Finish or restart the career round first." Restart round is already one tap away, and the suite plays a shot to make the hold engage, then takes that exact route back out and checks the career record came through byte-identical.
♿ CONTRAST MEASURED, NOT ARGUED. Locked rows were first dimmed with a blanket opacity on the row, which multiplies into the child that is already muted: the .r-sub line at 0.66 × 0.6 landed near 2.6:1, on the one line that explains what the mode is. Locked rows now carry their own colour values and the blanket opacity is gone. The suite composites each text colour down through every ancestor background — including the element's own opacity, the exact compounding that broke it — and asserts 4.5:1: name 11.61 open / 6.82 locked, sub 5.99 / 5.24, heading 6.33, status line 5.25 (it was 4.30 at 0.5 alpha and moved to 0.58), chip 12.59.
📐 52px rows (the flat row's 26px buttons are what this replaces), a panel clamped to the space under the chip and anchored off the chip's live rect rather than a fixed x, since the row can be scrolled sideways on a narrow phone. Below 340px the visible mode name drops and the chip becomes icon plus caret — the aria-label keeps the name, so the accessible name never shrinks with the type. Two shared motion tokens rather than a duration per transition, and the staggered row reveal plus every transition collapse under prefers-reduced-motion.
🧪 scratchpad/navrun.mjs, 134 checks: the gate, the flat row's non-regression, open/close by chip, scrim, × and Escape, elementFromPoint hit-testing every row (the clash lobby shipped visible-but-untappable, so "visible" is not the assertion), 44px targets, the five modes in the order asked for, locked-row behaviour, keyboard and typeahead, the Space guard, routing into and out of every mode with the park rules intact, the career hold, measured contrast, 320px and landscape, and reduced motion.

08/31/2026 — Daily Blitz, its own scoring economy

🔗 THE LINK IS THE MODE. Arriving on ?blitz=<passcode> deals today's three holes and raises a welcome card OVER the live round, so closing it by any route is teeing off — the Daily's card asks you to tap Play before it deals, which is one tap too many for a mode whose whole promise is that arriving is playing. Same podium as the Daily's, filtered to mode "blitz", plus a rules line stating the escalating putt up front (a player cannot play to a ladder nothing ever names). Only a genuinely FRESH round gets the card: a round already in progress, a parked one, or one already played today goes straight through startBlitz to a resume or the result. Re-tapping while already in it does not redeal, which on a once-a-day mode would be a retry.
📈 ITS OWN SCORING ECONOMY, since three holes leave no room to grind a bad one back. Proximity is anchored rather than tuned by magic constants: 7,500 at a foot or closer, falling to nothing by 50 ft, with the fall solved from those two points so moving an anchor moves the curve and the constants can never drift out of agreement with the comment describing them. The nine-hole curve tops out at 2.5 ft, but the blitz anchor is ONE, so the flat top moved there with it — a ceiling left at 2.5 would have capped the 1 ft anchor below its own stated value and quietly paid 5,743 for it. The result is far larger AND genuinely stricter: a tap-in is worth 4.27x a 20-footer here against 2.50x in the nine-hole modes (1 ft pays 7500 against 2500, 10 ft 3086 against 1500, 20 ft 1757 against 1000, 50 ft nothing against 339). An ACE is 15,000, twice a tap-in. Creativity and difficulty run 50% hotter with the BONUS above 1 scaled, so a flat ×1.00 stays ×1.00 and a ×1.46 hole becomes ×1.69 — the same idiom creativity already used to scale itself DOWN. Combo is deliberately left alone: three holes can already build it to ~×1.5 and boosting it too would stack three amplifiers on one round. The tier thresholds read the BOOSTED numbers so "elite" and "great" mean the same thing relative to what a hole can pay here, rather than making the blitz's combo harder to build while its scores were larger.
🪜 THE BIRDIE PUTT CLIMBS: +500, +1,000, +2,000 by hole, so the round builds to its last stroke instead of being three equal ones. Supersedes the Aurora's 750 in this mode, the way the clash's flat 1000 does, and the trait strip carries the live number every hole. An ACE takes the ladder too — it skips putting, so on the 5000 alone a hole-in-one on the final hole was worth barely more than a stone-dead tee shot plus the 2000 putt, with the best shot in the game scoring level with the second best. A hole-out IS the made putt, so it is paid as one: on a ×1.46 hole that is 28,730 against 16,055 for a tap-in plus the putt, which is the gap that ought to be there.
🏅 DIALED IN (5,000 on one hole) is no longer earnable in the blitz. 3500 proximity plus a 2000 putt clears it before any multiplier on the final hole, which would turn a real nine-hole feat into an automatic. Same reasoning as No Peeking, and the same fix.
✅ blitzrun.mjs is 45/45: the welcome card and the round already dealt behind it, the ladder announced on every hole, and each card's own arithmetic recomputed from the numbers it prints — proximity, putt bonus and both multipliers back to the printed total — which validates the curve, the boost and the ladder together without needing to know the hole's base difficulty. Proximity is separately checked against the blitz curve rather than the nine-hole one (32 ft paid 859, the blitz curve says 856, the nine-hole curve would have said 661). Because the course is seeded by DATE, a day whose three holes beat the driver (it does not compensate for wind) can never reach the scored-hole path at all — so the suite gained a whole-day clock offset to play another day's course, and the shipped anchor constants are asserted from source as well, which is deterministic on any day.

08/31/2026 — Daily Blitz, built but gated

🔐 GATED behind ?blitz=<passcode> (or #blitz=), the third door in the same pattern as career and the clash: a bare ?blitz unlocks nothing, and rotating BLITZ_PASS cuts every old link off at once. The gate constant is declared at the TOP of the file rather than beside the other two at the bottom, because refreshDailyBar and restoreRun both read it and the career gate has to guard its own use with a typeof test for exactly that reason. A round already in progress when the gate closes is moved to the blitz park rather than resumed or discarded — no player is stranded in a three-hole round with no way to see the mode, and the round comes straight back if they get the link. The player-facing release notes and the one-shot announcement were pulled with it (a "what's new" entry for a hidden mode gives the door away), and PATCH_NOTE_ID went back to null, which v1.0.9's had been due for anyway.
⚡ DAILY BLITZ: a second daily at three holes, on its own shared course (seed namespaces gsc-blitz|, gsc-blitz-themes|, gsc-blitz-diffbands|, so the Blitz is never just the Daily's first three worlds), its own record under gsc.blitz.v1 and its own streak. A missed green cards 0 — recoveryPlan gains !blitzActive alongside the clash guard — so three holes is three tee shots and three putts.
🔑 ONE LEVER: roundHoles() stopped being () => 9 and became mode-aware, which is what carries the short round through the scorecard grid, the summary boundary, the resume clamp and the "round already finished" test without touching any of them individually. blitzActive is deliberately DISJOINT from dailyActive rather than a flag on top of it: sharing the flag would have put a Blitz round one typo away from being banked as a Daily Darts completion, which would eat a player's real daily and their streak with it.
🐛 A LATENT BUG IN THE PARK, found by making roundHoles() variable. liveDailyBlob measured a parked run against roundHoles() — the count for whatever is on screen NOW, not for the blob being measured. With two round lengths in play that reads a parked three-hole blitz as forever unfinished and a parked nine-hole daily as finished at hole 3, throwing six holes away. It now reads blobHoles(b) off the blob itself. Park/unpark is shared by both dailies through parkRunAs / parkedRunFrom / resumeParkedRun with a predicate, and each daily has its own park key, so an unfinished Daily and an unfinished Blitz coexist and hop without either eating the other.
🏆 SCORE INTEGRITY, three places. splitByMode was "daily, or everything else", which put Blitz rows — three holes, so about a third of the points — straight onto the Free Play board where they can only look like terrible nine-hole rounds; it is now an explicit three-way match on rowMode. The lifetime round tally (rounds / scoreSum / bestScore, which the profile's AVERAGE is computed from) skips a Blitz, since averaging three-hole rounds with nine-hole ones makes that number describe nothing; per-HOLE stats still count, being comparable. And NO PEEKING now needs a full nine like the four achievements beside it — going three holes without a preview is barely a decision, and a Blitz earned the badge on its first outing (caught in a harness screenshot, not in review).
🌐 Backend: blitz is a real leaderboard mode rather than collapsing to "free". Blitz rounds rank against the day's other Blitz rounds, and the free-play weekly pool explicitly excludes them, so adding the mode cannot move anyone's existing "top X%".
✅ scratchpad/blitzrun.mjs, 29/29 with zero page and console errors: three holes and a summary at three, the 3-column card, no chip ever offered (asserted off the play button's own labels, since the game is IIFE-scoped and window.phase is not reachable — the honest probes are the DOM's), the record landing under the blitz key with gsc.daily.v1 byte-identical afterwards, the round tally not moving while per-hole stats do, re-tapping showing the result rather than a replay, both dailies parking and resuming independently, and a mid-round reload coming back at the right hole and still 3 holes long.

09/01/2026 — Daily Blitz is timed

⏱ SIXTY SECONDS A SHOT, and the shot times ADD UP into the round's elapsed total. The clock measures the one thing the player controls: time spent OVER A SHOT. It runs while the shot is theirs (club and aim through the power bar, then the read through the stroke) and stops the instant the ball is struck, so the flight, the reveal and the scorecard are free — and a phone call between holes cannot cost someone the board. Wall-clock from first tee to last putt would have charged them for all of it. Banked in the run blob, so a refresh cannot hand out a free fast time. Run out and the hole is worth nothing, the same answer this mode already gives a missed green — which is why sixty seconds is generous rather than tight: the clock is there to stop a round being abandoned mid-shot, not to rush the read.
🏆 THE TIME IS ON THE BOARD, AND IT BREAKS TIES. Equal scores are separated by whoever went round quicker, in the local board's comparator and in the server's ordering (score DESC, ms ASC NULLS LAST) alike. The column is nullable rather than 0-defaulted: every other mode is untimed, and a 0 there would sort to the top of a timed board forever instead of reading as "not measured". The value is bounded and only accepted for the blitz, so a figure outside a plausible round is treated as a typo or a tamper rather than becoming a permanent number one.
📊 THE BOARD GAINED A BLITZ SECTION, without which none of the above had anywhere to appear: three-hole scores were being computed, banked and ordered correctly and then rendered nowhere, because the UI only ever had Daily Darts and Free Play. Gated with the mode — a board should not advertise a door the player cannot open. The elapsed time sits under the score on every row, and the running total shows on every hole card too, so the tiebreaker is never a surprise at the end.
✅ blitzrun.mjs is 56/56, and the two hardest parts are exercised for real rather than reasoned about: the clock is asserted off the pill's own countdown (60 down, and a total that only ever grows), and the EXPIRY is watched by leaving a shot alone for a full minute of wall clock — it fires at ~56s, cards the hole at nothing, keeps the elapsed time on the card and lets the round carry on. The tiebreak renders two tied rows through the real board and asserts 1:01 ranks above 1:35. That test failed for three runs on a harness fault, not a product one: it seeded rows under a made-up player name, and "My Scores" correctly drops rows belonging to someone else on the device, so the board looked empty for the wrong reason.

09/01/2026 — Tour Clash: the replay is exact, and it waits its turn

🎥 THE CAMERA GOES WHERE THEY LEFT IT. Dragging the stage sets aimDeg, and lockedAim is the shot's fixed camera aim — neither was on the wire, so a shot aimed 20 degrees off the pin line replayed from a dead-straight view. Both now ride with the shot as the ONE state they held at the strike, and the watcher's view snaps there in a single reposition before the ball goes. Not a stream: at 5-10 messages a second per player that is nothing on a socket and roughly 6,000 function invocations and 6,000 Neon reads per match on a polling transport, since the "unchanged" reply saves bandwidth but not the database read. The green carries puttPan and puttZoom for the same reason. Verified with a REAL pointer drag in the harness rather than by writing the variable: -20.28 degrees captured, posted and applied.
📐 THE DISTANCE IS THEIRS, NOT A RECONSTRUCTION. The watcher recomputed proximity from the rest position and the hole length, which is a different calculation from the one that scored the hole. The striker's own measured figure now travels with the shot (`p`), so the number on the watcher's screen is the number on the striker's card — asserted across every green hit in a match, within a foot of display rounding.
🐛 A REPLAY COULD DESTROY THE WATCHER'S OWN SHOT. Driving replays off unwatched shots meant one could start while the watcher was mid-hole — rebuilding the hole underneath them, losing the struck tee shot, and letting the clock card them 0 while their screen still showed the score they thought they had. Caught in a live two-client match: a card read 7,088 against a server 0. A replay now yields to a shot in progress and plays when that hole is carded. The other half of the same failure was the clock itself, fixed server-side: watching is not thinking time, so the hand-over deadline now buys back an allowance per shot the arriving player must sit through.
🎬 The setup beat is shorter and calmer ("NAME is lining it up…", 700ms): one reposition of club, dials and camera, then the shot. The point is fidelity, not a performance.

09/01/2026 — Tour Clash: watch them set up, and watch the putt roll

🏌️ THE SETUP RIDES WITH THE SHOT. A tee replay now carries the three dials that produced it — club, shape, loft — and the watcher's screen puts them on the wheel and the sliders, holds a beat ("NAME is over the ball…"), and only then swings. showApproachClubs rebuilds the wheel AND the sliders from the live values, so the whole setup is one repaint. The spectator's own dials are snapshotted and handed back afterwards, so their next shot starts from their own choices. Three small fields on the wire and no extra requests: the alternative — streaming the dials as they move — needs 5-10 messages a second per player, which is nothing on a socket and roughly 6,000 function invocations and 6,000 Neon reads per match on a polling transport.
⛳ THE PUTT ROLLS. It was a verdict flash; it is now re-animated through animatePutt on a green dressed for replay, so the break, the pace and the lip theatre are the ones that happened. The payload gained the aim (`a`), which the animator reads from a global — without it every replayed putt rolled dead straight. Deliberately NOT goToPutt: that function RULES a putt as it arrives, and a distance inside the gimme calls scoreFantasyPutt, which would have scored the WATCHER's hole off the opponent's shot. clashPuttScene does the scene half only. The bot's putts are now shaped like real ones (reach, latMiss, holeLat, anim) so they roll too.
🐛 The strip read "Your ball" over a shot the opponent was visibly standing over: it followed the CLOCK, and the unwatched-shot model means a replay can run after the turn has already come back. It follows the replay now. The Play and Preview buttons also sat at full strength under the transparent cover, looking ready while being inert — dimmed while watching, with the club wheel and the read panels left bright, since those are the information the reveal exists to show.

09/01/2026 — Tour Clash fixes (from live two-player testing)

🌍 THE TWO PLAYERS WERE ON DIFFERENT HOLES. The server salts each hole's GEOMETRY, and that part was right — but themeForHole and diffBandFor had no clash branch and fell through to runSalt, a PER-DEVICE random. So one player was dealt Frostreach at 141 yds while the other got Elysium at 110, on the same "hole 1", with different wind, elevation and firmness. Both now seed from the MATCH ID, the one salt both clients are guaranteed to hold identically from the moment they are paired. Reproduced in the duel harness by removing the fix and watching the two screens disagree.
👀 A MISSED GREEN WAS NEVER SEEN. The replay was gated on it still being the opponent's turn, but a miss posts its shot and its scorecard in the SAME server update — so the turn had already flipped by the time the shot reached the wire, and the watcher skipped it entirely. A hole played faster than one poll interval vanished the same way. The replay is now driven by WHAT THEY HAVE POSTED THAT THIS SCREEN HAS NOT SHOWN, tracked per side and hole, with the stage lock holding the scene so a replay can finish even after the hole has settled. clashEnsureHole takes an explicit hole for exactly that reason.
🏆 …AND THE SHOT THAT DECIDED THE MATCH. The final hole settles the instant the second player cards, and clashSync returned on state === "done" BEFORE the unwatched check, so the winning shot went straight past into the result card. It now plays first and the verdict follows — but only for a match that ended in play, since after a concede or a clock ruling there is nothing to admire.
📏 "115 FT" ON A SHOT THAT MISSED. The spectate verdict read onGreen, which is where the ball LANDED, not where it finished — a ball can pitch on and run 38 yards off. The tee replay now carries g (0 missed, 1 finished on the green, 2 holed out), set from the outcome the striker actually had, and an ace finally announces itself as one instead of being reported as a missed green.
🔬 The duel harness now compares the two screens' HOLE FACE (number, yardage, elevation, firmness, world trait) and counts replays EXACTLY: every shot on the server must have produced a verdict naming its player on the other screen. The verdict log moved from an in-segment rAF sampler to a MutationObserver installed at page load — the sampler was blind between segments, which is precisely when a replay verdict fires, so it undercounted and could not support an exact assertion. That exactness is what caught the deciding-shot gap, which a floor-based check had waved through.

09/01/2026 — Tour Clash fix

🐛 THE INVITE PANE WAS UNTAPPABLE. Copy link, Share, "Play a tour pro instead" and the close button were all present, correctly labelled and completely dead: the lobby inherits .gfx-modal's z-index of 320, while the spectate cover is a full-screen inset:0 element at 940 that is raised the ENTIRE time an invite is open. The cover sat on top of the modal and swallowed every tap. Only the match strip (960) stayed above it, which is why Cancel worked and nothing else did, and why it read as "the buttons do not work" rather than "the pane is behind something". The cover has to keep covering — the board behind an open invite is a stale hole nobody should be able to play — so the lobby is what moves, to 980. The duel harness now hit-tests those controls with elementFromPoint and then really clicks Copy: textContent could never have caught this, since the markup was right the whole time. Confirmed by removing the fix and watching the new check fail with blockedBy "clashCover".

08/31/2026 — Tour Clash, live but gated

🤝 PLAYER VERSUS PLAYER on an invite link. A match is now one of two KINDS over one protocol. "bot" is the original single-device duel (the player's client synthesises the tour pro and posts it as side p2). "duel" is two humans: the host opens a match in state "open" with the p2 seat empty and no shot clock, shares ?clash=<passcode>&duel=<code> (the match id IS the invite code), and a second account takes the seat through /api/par3/clash/join, which starts the clock. From the join on the two sides are symmetric — each client posts only its OWN shots and replays the other's off the poll. The bot's single-device trick is what made this safe to ship: the wire format had already been exercised end to end before two people met on it. The one asymmetry left is guarded — the side:"p2" override now requires kind === "bot", because p2 == null is ALSO true of an unanswered invite, so testing emptiness alone would have let a host post shots for the opponent about to arrive. An invite carries a 30-minute TTL, lapses through the same lazy clock that rules the shot clock (no cron), and cancelling one credits nobody rather than awarding a phantom win. Joining while already in a match is refused so nobody gets abandoned without a verdict; joining is idempotent for a player who already holds a seat, so a double tap or a reload on the link is harmless.
🐛 A DUEL COULD NOT BE REJOINED FROM THE GUEST'S SEAT. saveMatch's ON CONFLICT list updated doc/state/version but not p2, and a duel fills that seat on an UPDATE (the row is inserted with p2 NULL and joinMatch sets it later) — so the indexed column stayed NULL forever while the doc's own JSON knew better. loadLiveMatchFor reads the COLUMN, so the guest's queue could not find their own match and dealt them a fresh bot match instead. Found by the API suite asserting the rejoin from the p2 side, not by reading the code. A partial index on p2 came with the fix.
🔐 The gate is now a PASSCODE, not a flag: ?clash=<passcode> (or #clash=), matching career's pattern, with a bare ?clash unlocking nothing. Rotating CLASH_PASS cuts off every old link at once INCLUDING invites already in circulation, since an invite link carries the passcode and a guest who cannot open the mode cannot join a match inside it. The &duel= code is stripped from the URL once a join succeeds (keeping ?clash= so a refresh stays unlocked) — but not before, so a reload or a detour through sign-up can still use it.
🎬 ONE WATCH PATH for both kinds of opponent. clashWatchOpp replaced the bot-only replay: a bot's shots are synthesised and posted first, a human's are waited for on the poll (clashAwaitDoc), and from the replay down the two are identical. Every await re-checks that the opponent's turn on THIS hole is still live, so a shot clock ruling mid-replay cannot let a stale continuation draw over the next hole. A lobby fronts the mode (a tour pro / an invite / a code box that accepts a pasted link as well as a bare code), the waiting room shows the link with copy and share, and the strip reads "Invite open · Waiting for your friend" with Cancel instead of a two-tap Concede while nobody has joined.
✅ Verified by two harnesses, both committed. clashapi.mjs is 47/47 over real HTTP, the new half covering invite/join, both players' names, neither side being able to post for the other (the bot override included), a duel played through to a verdict with the loser's client agreeing, a lapsed invite, cancelling an unanswered one, and the guest's rejoin. clashduel.mjs drives TWO independent browser contexts through one duel concurrently: the host invites, the guest opens the link, both play their own balls on the live bars and watch the other's replays, and it asserts the verdicts agree, every card matches the server's per-hole record, each side's shots are attributed to that side, and each client's own verdict log contains the OPPONENT's name (proof the replay actually ran on their screen, not just that the data arrived). First run: 15/15, zero page errors, and it happened to go to sudden death.
⚔️ TOUR CLASH, behind the passcode: a live 3-hole duel over the clash API (par3_clash_matches, one versioned JSONB doc per match; queue / shot / state / concede). Three shared seeded holes ("gsc-clash|<server salt>|h<n>", dealt one at a time so neither side can scout ahead), the higher score takes the hole, first to 2 wins, sudden death when level capped at +3 then total points then a genuine draw. Match rules override par-3 scoring in exactly two places: a missed green cards 0 on the spot (recoveryPlan gains !clashCtx, so every hole is at most tee + birdie putt) and the made putt pays a flat +1000 (superseding the Aurora's 750 — the trait line says so in-match). The SERVER owns turns, the 30s shot clock and the verdict, ruled lazily on every read/write, so an abandoned match closes itself with no cron. Replays are the animators' own parameter objects: my tee shot is captured verbatim at animateApproach and posted at the strike when a putt follows (re-arming the putt's clock), otherwise with the hole's points from the card; the opponent's shots re-animate through the same animateApproach on the same seeded hole. v1 deals bot matches — the bot's shots are synthesized client-side, posted as side p2 through the real protocol, and replayed like any remote player's, so the whole wire format is exercised before humans meet. Clash is throwaway like the range and the tutorial: saveRun gains the clashCtx gate, bumpStats/bumpRuns/earnAch/postAceTracker/recordTeeGreen and the longest-putt write are all clash-gated, and leaving restores the parked round (free play, daily, or career under its own key) exactly where it stood. Verified end to end by a headless client playing full matches on the live bars against a local backend — 2 matches, honors alternating, points on every card equal to the server's per-hole record, replays under the 4KB budget, parked round's salt identical across both matches, lifetime stats byte-identical, zero page or console errors — on top of the API suite's 24/24 (sudden death, the cap, the points tiebreak, the draw, clock expiry by SQL rewind, rejoin, refusals, stranger 403s).

v1.0.9 (08/27/2026)

⚡ FRAME COST, in four parts. (1) The tee's sweeping bar redrew the entire scene on every tick of the sweep loop: liveSweepDraw now guards on a sceneDirty flag that only a real scene change sets, since aimSweep and powVal never feed the renderer, and it strides when a draw costs more than 6ms (13 draws/s to 0 while a bar sweeps; 7fps to a locked 60). (2) setPhase marks the scene dirty, so a phase change still gets exactly one paint. (3) The flight drew on every animation frame, which a 120Hz phone cannot service in 8.3ms and which produced a 17/25/33/42ms oscillation: pacedFlightDraw holds a 15ms floor, just under 16.7 so a 60Hz tick is never skipped. (4) The apex and landing spikes were GC, not geometry: buildProps and the ball trail each allocated a fresh array and a fresh Float32Array per frame. Both now take from a scratch pool that grows and reuses, with the upload subarrayed to the live length. Diagnosed by spike POSITION variance across runs rather than by frame count, which is what distinguishes collection from a rebuild. buildPropsDrive has the same shape and is deliberately untouched until the career autopilot is back.
⛳ THE PUTT READ carries its own numbers. A strip under the trait bar holds Break, Slope and To hole; the overlay panel that used to sit on the green is faded for the read and returns for puttAim and puttSwing. Every figure the panel held is elsewhere on the read: Distance is To hole, Break and Slope are their own cells, and Pace is the power bar's own readout, which is asserted equal rather than assumed. Slope shows the arrow WITHOUT the Up/Down word, because three cells leave 98px at 360px and the widest values measure 84 ("◀ L 4.0 ft", break and grade both clamped to ±4), 78 and 76, against 139 for "🔻 Down 4.0 ft". Filling the read's band also fixed the row below it: Continue / Preview sat 85.5px above where Lock aim appears, because the read carries no Shape/Loft sliders and one bar where the aim step carries two meters. pp-read spends that difference either side of the power bar, 46 above and 17 below (uneven because #meters keeps its 14px margin with both meters hidden and the button row adds 15, so centring the track needs margin-top = 29 + margin-bottom). Residual 0.3px, measured identically in par 3 and in career.
🎚️ The power track goes 27.5px to 30.25px, a straight 10%, and the pace value gains a white outline and a dark ground at 15px. Its height is matched to the track (15 + 12 padding + 3 border = 29 against 30.25) so the ROW stays as tall as the bar and the band spacing keeps a fixed thing to sit against. Width 76px, from a Range measurement of the text node: widest real value "120 yd" at 49.7px of ink in 57px of inner width. scrollWidth was useless here, returning the same 74px for every string including a 20-character control.
🐛 LAYOUT TUNED IN PLAY, NOT IN A FORCED STATE. A probe that only toggles the two display sets reports the button row 33px closer to aligned than the game does, because it reproduces neither #meters' surviving margin nor the restart button that shows on the read alone. The first pass was tuned against that number and shipped 34.5px low. The forced probe now measures cell widths only.
🐛 The overlay panel FLASHED on entering a read: draw() made it visible and set the fade as two separate style writes with a layout read between them, so it painted at full opacity for a moment before the class arrived. The fade is now set before the panel is shown, and the check samples opacity AT the instant the read appears rather than after a settle, so a flash fails rather than being waited out.
⚙️ SETTINGS TIP, once per player, keyed on gsc.settip.v1 and shown only to someone who has finished a round: a new player gets it when their first round completes (2700ms after the card, behind the guest nudge at 1700), an existing player on their next open, from bootPopups. It declines while another pop-up holds the screen and keeps its flag when it does, so it arrives next open instead of being burnt. The gear outranks the modal's dim already (z 240 against 50), so it stays visible and takes a gold ring rather than any z-index work; the CTA synthesises a click on #gfxBtn because three listeners are bound to it and only a real click runs all three. gsc.settip.v1 joins MIRROR_SKIP with the other seen-flags.
📢 The one-shot announcement is ARMED for this release (PATCH_NOTE_ID "v109-2026-08-27"), and the patch-note pop-up now dismisses into the settings tip rather than leaving it for the next session, since both are due at the same moment for a returning player. The update path itself is unchanged: offerUpdate raises the banner and nothing else, and the only reload is the player tapping Update.
📱 CAPACITOR shells for iOS and Android, inert on the web behind NATIVE_APP. Google sign in through the system browser with a PKCE deep link back on io.flaghunt.app://, so the one-time code is exchanged and the token never rides the URL; progress mirrored into native Preferences against web-data eviction; account deletion in the app, with the local copy wiped alongside the server row because every synced counter is monotonic and a survivor would re-upload the deleted totals; share sheet, haptics and a local Daily reminder. Play release prep: signing config, versionCode derived from VERSION, and a privacy policy at /privacy.html. Account deletion is deliberately app-only for now; the web points at the email route.

v1.0.8 (08/08/2026)

🔒 THE GIR CHEESE, CLOSED. The green was ruled inside tallyFantasyHole, which only runs once a hole is FINISHED, so a player who missed a green and then restarted the round instead of holing out never had the miss counted and could carry a GIR streak indefinitely by abandoning every bad hole; the round card sat a hole behind the ball for the same reason. recordTeeGreen now rules it the moment the tee shot comes to rest, at the single point in resolveApproach where the outcome is known and before the hole branches into an ace, a putt, a recovery chip or a dead miss. holesPlayedRound, girCount and the girRun/bestGirRun update moved with it, the card repaints on the spot and the run is written to storage immediately, so neither a restart nor a refresh walks it back. Once per hole via holeGirCounted, because a refresh mid-hole replays the committed shot back through resolveApproach and would otherwise rule the same tee shot twice; the flag rides the saved run for exactly that reason and clears on a fresh hole and on resetRun. Sims and tutorial holes excluded. Verified by attempting the exploit with timed bar taps on a hole left in progress with a shot still owed and the scorecard not yet up: the card already read 1/4, girRun was already recorded, restarting neither rewound the run nor inflated the record, and a reload did not re-rule the tee shot.
🔒 STRICT ABANDONMENT for the birdie run. A birdie cannot be ruled at the tee the way a green can, because a chip-in off a missed green is still a birdie, so the hole is ARMED when the tee shot rests (birdieArmed) and settled exactly once: by bumpRuns if it plays out, or by settleAbandonedBirdie if it does not. Abandonment is caught at the two moments it is certain — resetRun, which every restart, mode switch, daily start and challenge accept routes through, and the next tee shot, which settles any hole still armed before arming its own. Deliberately NOT settled at boot: a mid-hole refresh RESUMES the hole rather than abandoning it, so settling there would break a run the player never lost, and that is the case tested hardest. Confirmed on a live hole: armed at rest, run untouched while the hole is alive, restarting drops it to 0 and disarms while keeping the record, and a refresh instead leaves the run intact and the hole still armed.
🎨 ALL THE SHAPES: ace, birdie putt, par, bogey, chip-in birdie and a splash in one round. holeShape classifies a hole as EXACTLY ONE of the six, so they must come off six different holes and a splash does not also pay out as the bogey it effectively is. Fantasy holes never play out, so par and bogey are outcomes rather than stroke counts: a putt reached via a chip carries recovery:true (index.html:6000 against :8337), making it a PAR putt, so holing it is the par and missing it is a bogey; a green in regulation makes it a BIRDIE putt, so holing it is the birdie and missing it is a par, a tap-in from 3. Bogey therefore has three ways in — the missed par putt plus the two [X] holes (a chip that failed to save, and a miss with no recovery offered). The marker sits beside bumpRuns, ABOVE the missed-green early return, and that placement is the whole ballgame: a splash and a bogey are both missed-green holes, so the first version, written next to the other per-hole badge checks below that return, could never see two of the six shapes it was counting — caught by the test, not by reading it. Progress is per round, cleared at every round boundary and by resetRun, and persisted with the saved run. Verified against all ten argument shapes the real tallyFantasyHole call sites pass, then in-game: five shapes do not earn it, the sixth does, a new round clears the collection while keeping the badge, progress survives a reload, and it renders on the profile wall.
👑 CONSISTENCY KING at 36 consecutive greens, four flawless nines back to back, against Dart Thrower's 15. No cls, so it takes the default gold chip; computed colour, border and background asserted identical to Dart Thrower's. The two GIR tiers are cumulative like every other title here, so at 36 a player wears both.
🔮 LEGENDARY PULSES: legendPulse, a 2.4s ease-in-out loop taking the glow from 7px at 0.32 alpha to a 20px core with a 34px halo and carrying the border and text with it. It is the only chip on the row that moves, which is what makes it read as the trophy among them. prefers-reduced-motion drops the animation and leaves the purple and a steady glow, since an infinite decorative loop is exactly what that query is for. The two extremes were shot by freezing getAnimations().currentTime at 0 and 1200ms, and the computed shadow and border genuinely differ between them.
✂️ The made-putt streak was withdrawn (see v1.0.7 below), the box became "Consecutive Streaks" with cells reading Birdies / GIR, and both strips now share their three rows through subgrid so label, value and record line up however many lines a label wraps to — measured identical at 360, 390 and 430 px across the streak cells and the round card's. Nothing was deleted for the withdrawal: puttRun / bestPuttRun are inert and best_putt_run keeps what it banked, so it survives if it is ever wanted back.

v1.0.7 (08/08/2026)

✂️ WITHDRAWN SAME DAY: the made-putt run. The streak strip and the profile now carry two runs, birdies-or-better and greens, and the "Never Misses" title (12 putts in a row) went with the counter it read. bumpRuns drops to (girOk, birdieOk), bestPuttRun leaves STAT_FIELDS, and the strip runs two cells wide. Nothing is deleted on either side: the stored keys puttRun / bestPuttRun are inert once nothing reads them, and best_putt_run keeps whatever it banked, since dropping a live column is irreversible and buys nothing. A client that stops sending the field makes readIncoming see 0, and GREATEST(existing, 0) holds the stored value, so old records survive untouched if it is ever wanted back. The entries below describe the shape it shipped in earlier today.
🔥 CONSECUTIVE RUNS: birdies, greens hit and putts holed, each tracked as a LIFETIME run rather than a per-round one. They live in the stats store instead of the round state, so a round boundary, a mode switch or a fresh session cannot clear them and a record can climb past the nine holes of a single round; the existing per-round `puttStreak` is untouched, since it feeds the combo economy and the five-in-a-row badge, which are shipped par-3 mechanics. bumpRuns is called once per hole from tallyFantasyHole, placed ABOVE the missed-green early return so both outcomes pass through one call and a miss actually breaks the run, BELOW the tutorialMode return so a lesson hole never counts, and BEFORE updateRoundCard, which paints the strip off these counters (the other order left it a hole behind). The definitions are inherited rather than invented: a green counts on `!missed && !recovery`, the same test girCount uses, so a chip-in save is not a green; a putt counts on `puttMade && !chipIn`; and a birdie counts by isBirdieHole, so an ace, a putt holed off a green found in regulation, and a chip-in that rescued a missed green all qualify while a putt holed after a recovery does not. Verified by driving the real tallyFantasyHole through a controlled nine and asserting all three runs after every hole (ace: birdie and green but no putt; chip-in: birdie but no green; scramble: putt but neither), then the records, the live strip and the profile tiles: 39 assertions, all passing. A second pass covered persistence and sync (27 more): a new round via resetRun clears nothing, a reload keeps both the live runs and the records with the strip repainting from storage rather than the markup defaults, and mergeStats adopts a higher record from the account, keeps the local one when the server's is lower, and leaves the live runs alone.
☁️ SYNC: bestBirdieRun / bestGirRun / bestPuttRun join STAT_FIELDS and merge by max like every other counter. The live runs (birdieRun / girRun / puttRun) are deliberately NOT in that list: a run in progress has to be able to fall back to zero, which a max-merge can never express, so they stay device-local. The consequence is accepted and stated rather than worked around: four greens on a phone and four on a laptop do not add up to eight, because the alternative is a non-monotonic column and last-write-wins, which fights the whole design of par3_stats. pushStats sends the entire blob and the server ignores keys it has no column for, so nothing has to be stripped client-side. Backend (grand-slam-challenge-pga): best_birdie_run, best_gir_run and best_putt_run added to ensureStatsTable's ALTER list so the schema still self-migrates and Neon needs nothing by hand, plus the Par3StatsRow type, shapeStats, readIncoming, the upsert's column list / VALUES / GREATEST merge / RETURNING, the stats GET select and the public player profile select. Checked mechanically before deploying: INSERT arity 24 columns to 24 values, 20 GREATEST pairs all self-consistent, and RETURNING and both SELECT lists matching the 22-field row type exactly. Confirmed live after deploy by the public player endpoint returning bestBirdieRun, which proves the migration ran (that route calls ensureStatsTable then selects the new columns, so a value rather than an error is the proof).
🖥️ THE STREAK STRIP sits under the round card: three cells on .card-grid's own three columns so it lines up with the card above, each showing the live run with "Best N" beneath. A run that has caught its own record goes red (.v.hot), since that is the moment worth noticing. Shown for par-3 scoring only, because bumpRuns is driven from tallyFantasyHole and so in career (which keeps its own ledger) and on the range (which never scores a hole) the counters cannot move, and a frozen counter reads as a broken one. mergeStats repaints the strip so a record adopted from the account on another device reaches it and not just the profile page. The profile tiles show the record alone.
🔮 LEGENDARY: a title at 72 consecutive birdies, which is eight flawless nines back to back with every hole birdied. It reads bestBirdieRun, a record rather than a live figure, so unlike Top Dog and Ace Afficionado it never lapses once earned. Its own .title-chip.legendary carries purple border and text plus a glow the other chips do not have, since the existing variants only recolour. Verified absent at a best run of 71 and present at 72, with computed text and border both purple and the glow rendering.
🔤 The round card and streak values moved from weight 600 to 700, matching every other stat box in the game (.prof-stat .ps-v, .stat-tile .st-v); that pair was the only one left at 600. Measured first rather than assumed: all 24 elements inside both strips already computed to Sora, the same face as the rest of the game, since --font-serif, --font-sans and --font-mono all resolve to it, the @font-face is embedded as a data URI and the face measures distinctly from the system fallback (253.7px against 200.0px for the same string at 600 40px), so nothing was falling back and the family was never the problem.

v1.0.6 (08/05/2026)

👀 Career mode work continues; no par-3 mechanics touched. Alongside it, three accuracy fixes where the text had drifted from the code. The career help sheet claimed an event is "72 holes over four 9-hole rounds" (four nines is 36, and CAREER_EVENT_HOLES computes exactly that), and it described "Six ratings" naming Distance/Accuracy/Approach/Short game/Putting/Luck while CAREER_RKEYS carries eight and the clubhouse trains all eight — Recovery and Mental were both missing, and "Distance" is labelled Power everywhere on screen. The ratings paragraph now names all eight by their clubhouse labels and says what each does: Recovery's real jobs (it blends into approachEffSkill the further the lie strays from short grass, at weight 0.3 rough / 0.5 native / 0.55 bunker / 0.7 trees, and it sizes the tree-punch window and calms its bars) and, honestly, that Mental is inert — every use of it sits behind `if (R.pressure)` and R.pressure is initialised false and never assigned anywhere in the file, so training it currently changes no shot.
✂️ The CUT was labelled "36-hole" throughout, inherited from real tours, but CAREER_CUT_HOLES is CAREER_CUT_AFTER × 9 = 18. Two of those labels were player-facing: the Weekend Golfer achievement read "Make a 36-hole cut on tour" (now "Make the cut on tour", which stays true if the round length ever moves) and the missed-cut card's first tile read "36 holes" over a score that is 18 holes' worth. The tile now reads 18 holes, and the comments at the four sites that repeated the figure are corrected, with the one at CAREER_CUT_AFTER noting where the label came from so it does not get "fixed" back. The event total genuinely is 36 holes, so careerField's comment was already right and is left alone.
⛳ The PIN is seated against the green's real outline. pinFromFront was drawn against the NOMINAL depth — round(5 + rand x (depth - 10)) on a plain rectangle — but a green is a shape, and along the pin's own line the surface only reaches greenMultAt() of that nominal half-depth, a figure running 0.55 to 1.38. A front pin on a shape that pulls in at the front is therefore cut far closer to the edge than its yardage claims. The worlds that GROW the green compounded it because they grow it AFTER the draw (Ocean and Skyworld +5 yd of depth, Elysium +4): the centre walks backwards while the pin stays put, so it ends up nearer the front edge in the shape's own terms than generation ever intended. Island greens showed it worst, since the land stops at the collar (gN < 1.19) and there is no rough apron to give the eye any margin. Measured over 300k generated greens per world, pin-to-edge distance along the pin's own radial: worst -0.72 / -1.40 / -2.22 yd for base / Elysium / Ocean-Sky (negative = the cup is off the putting surface, on the fringe), with 0.4% / 0.3% / 0.3% of pins inside 3 yd of their own edge and 0.003% / 0.006% / 0.006% past it. The rendering was not at fault and was checked first: the reveal in fantasy goes through GL.render, not drawGreenTopScene, and the mesh's greenCZ, pinZ and its `nd < m` green test all agree with greenMultAt. seatPinInsideGreen() now measures the surface's reach toward the front and the back along the pin's line and clamps pinFromFront to keep PIN_EDGE_MIN (4 yd) of green on either side, falling back to dead centre on a green too shallow to hold the margin at both ends. It runs LAST in newHoleImpl — after every theme bump and after the range's resize — because that is the only point greenDepth is final, and it is called on the par-3 path and the career par-4/5 path alike. After the change the worst pin-to-edge is exactly 4.00 yd in all three worlds with zero violations over 900k greens, and only ~1% of pins move at all (max shift 6.2 yd); re-measured against the live generator in Chromium over 405 real holes, 45 of them Ocean, worst 4.00 yd and no page errors. Gated by PIN_INSET_FROM so a daily already in play keeps its pins. COURSE_VER is deliberately NOT bumped: 99% of career holes are unchanged and the ~1% that shift are deterministic, so they stay consistent across rounds, and a bump would drop every in-progress tournament. Known minor consequence: Ocean's isle clearance is computed from gcz before the seat, so a pin shift can bring an island to 34 yd of the green rather than 40 — still well clear of the surface.
🏆 The global per-player run cap is per PERIOD instead of one flat number. LB_PER_USER was 10 for every scope; it is now { all: 5, weekly: 1, daily: 1 }, read through lbPerUser(scope) which falls back to 5 on an unrecognised scope, and boardRows takes the scope as a fourth argument so all three call sites (the full page's paginated list and the pop-up's two mode sections) cap by the period actually on screen. The periods measure different things: Today and This Week are "who is playing best right now" over a field only a day or a week deep, where one player holding several top slots buries everyone else, so those show one run each; All-Time is a hall of records where a repeat performer belongs, but ten rows of one name is still a wall, so it shows five. Today and This Week were already deduped to one run per player server-side, so those two entries agree with the server rather than change it — but the rule now lives client-side for all three periods, so the board is capped by what the client states no matter what comes back. The cap still runs AFTER splitByMode, so a player's Daily runs cannot crowd them out of Free Play, and "My Scores" stays uncapped in every period since it is where the hidden runs are read. capPerUser keeps the first n rows per name, which is the player's BEST n only because the board arrives sorted best-first from the server and the client never re-sorts it — the same assumption the ranking itself rests on, now written down at the function. Verified by lifting capPerUser/splitByMode/boardRows/lbPerUser out of the file and running them over a synthetic best-first board of 3 players × 8 runs × both modes: 27 checks, all passing — row counts (3/3/15), max per player (1/1/5), the kept scores being exactly each player's best n for the mode, one mode per section, and My Scores returning all 24 in every period.
🐛 The version tag opened an EMPTY modal. Two elements carried id="patchModal" — the dormant one-shot announcement shell and the "What's new" release-notes list — and both also carried id="patchClose". getElementById returns the first match in document order, which is the announcement, so the tag raised a shell whose #patchBody is only ever filled by maybePatchNote(); that returns early while PATCH_NOTE_ID is null (its dormant default), leaving the body blank and a "Try it in the range" CTA under it. The release notes were unreachable from the UI. The announcement is now patchPop/patchPopClose, so patchModal/patchClose resolve to the list the version tag names, and the two close buttons no longer share an id. Both blocks were already class-styled (.patch-card), so nothing in the CSS keys off either id.

v1.0.5 (07/26/2026)

🥅 Break retuned around a stated curve instead of an emergent one. The ceiling was distFt/15, which pinned a 5-footer to 0.33 ft and never let a 30-footer past 2 — measured over 900 reads, the old averages ran 0.22 / 0.92 / 1.27 / 1.90 ft at 5 / 20 / 30 / 50. The ceiling is now CONTINUOUS with no flat band anywhere — d/10 out to 30 ft (0.5 at 5, 1.0 at 10, 2.0 at 20, 3.0 at 30) then easing to the 4 ft ceiling by 50 — with a breakAvgFt target tracking under it at 0.30 / 0.60 / 1.25 / 2.5 / 4.0 for 5 / 10 / 20 / 30 / 50. A flat band meant a 5-footer and a 10-footer could draw the same worst-case read, which is what made short putts feel arbitrary. Generation divides the geometry (|perpComp| x greenLeanMag) by its measured mean of 0.246 to get a unit-mean factor, then multiplies by the target — so the average is the number the curve states rather than whatever a stack of multipliers produced. A breakTrim factor rising 1.00 to 1.90 with length makes up for the ceiling clipping the distribution, which it does harder the longer the putt; a flat factor overshot short putts and undershot long ones. Measured averages: 0.17 / 0.31 / 0.46 / 0.63 at 3 / 5 / 8 / 10 ft, 0.97 at 15, 1.26 at 20, 2.44 at 30, 3.38 at 50 and 3.56 at 60, with the observed maxima landing exactly on the cap curve at every distance sampled (0.3 / 0.5 / 0.8 / 1.0 / 1.5 / 2.0 / 2.5 / 3.0 / 3.5 / 4.0). The 50+ average sits near 3.5 rather than 4.0 because 75% of those reads are already pressed against the ceiling — a true 4.0 mean would require every long putt to read exactly 4 ft, which is no read at all. IMPACT IS UNCHANGED: the lateral used to be maxDeg x (break / cap), so widening the ceiling would have quietly made every existing read bend less; it now reads maxDeg / capV1 per foot, verified identical to the old formula across 18 distance-and-break pairs. Career keeps the old ceiling and its own generation, and dailies posted before BREAK_TUNE_DAILY_FROM keep the old read so a live board is never re-graded.
⛰️ Green contour now drives the approach's ground move in BOTH directions. The old term multiplied rollout only when it was positive, so a checking ball felt no slope whatsoever — the ground behind the flag could be pitched straight back at the hole and the spin-back would not change. One signed factor (dFwd x mag, saturating at ±0.32) is now computed at the pitch mark before anything else and feeds three places: the receptiveness FLOOR on medium/firm greens bends with it (x0.34 to x1.66), so the minimum release shrinks where the ground gives the ball somewhere to go; the shaping multiplier is applied along the direction of travel via Math.sign(rollout), which leaves a forward release exactly as it was while letting a back-feeding slope deepen a check; and an additive gravity creep of up to ±4.5 yd walks a stopped ball down the tilt, which is the only term that can carry a firm green's run back past its own pitch mark. The outer clamp widens to -9.5 yd because the soft-green zip is capped at 7.5 BEFORE the contour lands, and at the old bound a lob wedge into a soft green read identically on a slope feeding home and on a flat one. Measured net ground move, back-feeding / flat / falling-away: LW firm -3.1 / +4.9 / +15.5 ft, LW medium -3.5 / +3.1 / +11.4, PW soft -19.1 / -10.7 / -3.0, 7i firm +0.2 / +6.6 / +15.5, 5W firm +1.0 / +7.9 / +15.5 — monotonic in all twelve club-and-firmness combinations.
☢️ Ace detection accepted only balls that RAN forward into the cup. The predicate required landPastFt < ACE_CARRY_PAST_FT (1.5 ft), which no spin-back hole-out can satisfy — it has to carry past the flag to zip back into the hole — so a ball that sucked back in was scored as an ordinary tap-in instead of an ace. The carry test is now waived when the ball finished BEHIND where it landed, with the full backward reach allowed (the ground move floors at -4.2 yd, so 12.6 ft is as far as anything can come back). The line and dying-pace tests are untouched and still have to pass on their own: crossesCup, lateral within 0.6 ft at the moment it passes the cup, and resting within 2.5 ft of it. Checked against a replica of the predicate over nine outcomes — spin-backs landing 6, 10 and 12 ft past now score the ace, while a spin-back that is offline at the cup, one that stops 4 ft short, a ball that carries past and runs ON, and one that lands 30 ft past and only creeps back are all still correctly denied.
📐 The SLOPE row never reads "Level". puttGrade is stored to 0.1 ft but the readout needed |grade| > 0.3 before it named a direction OR printed a number, so 0.1, 0.2 and 0.3 ft of real climb all displayed as flat: over 160 generated putts, 57 of them (36%) fell in that band. It now prints the direction of whatever grade it has with the magnitude floored at 0.1 ft, and a grade that rounds to 0.0 is called 0.1 UPHILL rather than level — the true value is inside ±0.05 either way and being told to hit it firm costs nothing, while "level" on a putt creeping uphill leaves it short. Display only: puttGrade itself, and every use of it in resolvePutt, is untouched.
🏝️ Ocean and Skyworld carry a base difficulty of 1.3x through diffBaseFor(), and difficultyMult returns base + (3.0 - base) x composite rather than 1 + 2.0 x composite. Rescaling instead of adding a flat +0.3 with a hard cap keeps the ceiling at 3.0 with no dead zone at the hard end, where the last 15% of distance and wind would otherwise stop counting for anything. The band fit inverts the same curve, so needC and the band-floor clamp both read the world's own base. Holding the generated holes fixed and re-mapping only the multiplier, the change is worth +0.14 on an average ocean hole (2.03 -> 2.17) and +0.20 on Skyworld (1.71 -> 1.91), or +0.34 on the sum of a nine-hole round's multipliers. Verified 0 of 300 holes out of their difficulty band afterwards.
🌊 Ocean and Skyworld clear hole.par3.water at theme time. The generic par-3 pond is rolled before the theme lands, and on these two worlds it never reaches the island: measured over 32 ocean and 28 Skyworld holes, 15 of each carried a zone and NONE fell inside gN < 1.19. It could therefore never be built in 3D — the sample() ocean branch returns sea for everything off the island — while drawGreenPreview still drew it, putting a water-hazard blob on a diagram whose entire surround is already water. Both already cleared greenBunkers on the same reasoning; this finishes the job. Dropping it also frees the hazard budget it was consuming in the difficulty fit, which the fit now spends on yardage instead.
🎯 Range putting practice. A rangePutt flag re-rolls hole.greenLeanMag/Ang from the par-3 distribution (33% severe 0.48-0.80, then 60/40 moderate 0.28-0.50 / gentle 0.16-0.30), clears _undRolled so goToPutt re-rolls the contour, sets puttDist to 5-25 ft and stands the ball at a random angle on the clock face at 0.75-1.10x that radius, so the break is not always the same side of the line. A hole-out credits the putt's own length and a miss reports long/short off `reach - puttDist`, the finishing side off `latMiss`, and the straight-line leave off `remain`; either outcome then deals a fresh green. There are no comebackers: the drill is reps at fresh reads, and tapping leftovers in would pad putts-made with gimmes. Nothing is scored, saved or posted, matching the rest of the range. The tally rides the round card that was already on screen (Putts made, Length of Putts Made) rather than a second readout, and the GIR cell — meaningless on a practice green — retitles to the longest putt holed.
⛳ The made-putt drop is a rigid-body solve, not a curve. cupDropPath integrates the ball at 240 Hz through four contact regimes: free flight under g = 32.2 ft/s²; the rim, modelled as the true sphere-meets-circle surface y = CUP_DEPTH + sqrt(BALL_R² - (CUP_R - r)²), whose inward slope supplies a real tangential acceleration g·sinθ·cosθ (resolving the contact alone zeroes the fall every step and the ball loiters on the paint — that WAS the hover); the shaft wall at r = CUP_R - BALL_R with restitution 0.32 and tangential scrub 0.78; and a dished floor with restitution 0.28 and a spring to the axis. Entry velocity is the last roll segment's direction at v = sqrt(2·a·d) off the overrun (a = 2.2 ft/s²), scaled by 1 - 0.72·(r/CUP_R)² because a ball crossing the edge at pace lips out rather than dropping — without that cap a wide fast entry swung the liner for 300 ms before falling. The last 30% eases to dead centre on the floor so every putt finishes where a real one does. Measured over five entry cases: first motion 25-146 ms, below the lip 108-250 ms, on the floor 192-338 ms, ends at r = 0.0000 and sink = 1.0000 in every one, and the ball is never drawn below the green while outside the cup radius.
🎥 There is NO camera move during the drop at all: the ball falls on the camera the putt was played from, and puttDrop now only marks that a drop is running for renderPutt and the watchdog. All the camera work is in the settle, which orbits onto the cup on a make and behind the resting ball (framing the ball-to-cup midpoint) on a miss. Measured across a whole settle, 49% of the frame changes on a miss. It needs no head start because the ball spends its first ~165 ms toppling on the rim before it is low enough for the near edge to hide it. The focal length is left alone: tightening the FOV to 0.64 during the drop snapped back to 0.82 in a single frame when the camera released, and that snap plus the settle move was the end of a putt reading as two hard zooms. Filmed at the tee-to-cup transition, a 0.24 ft off-centre entry reads: 0 ms on the lip, 105 ms committed and falling, 208 ms nearly down, 320 ms resting on the floor, then 421 ms of the ball sitting in the hole before the settle takes over. The in-shaft dimming floor lifts 0.34 -> 0.52 so the ball at the bottom stays readable.
🎨 World art, 16 items from the environment review. Volcano: decorative lava pools pushed from 58 to 72 yd lateral, clear of the corridor; a second cinder cone (30 yd base radius, 38 tall) placed opposite the hero at pinZ+46..68 — a different depth, not just a different x. Ocean: the tee pad is an ellipse whose height lerps into baseH over its outer 37%, and the tee island now shelves through a sand apron to 1.1 yd below the sea surface out to 1.62× its radius, so there is no cliff left to read as a card edge; two isles of 4-6.5 yd radius added at |x| 10-18 and 34%/56% of the hole's length. Tempest: squall wall at pinZ+62 (inside the fog ramp on purpose — past the near plane everything mixes 90% to fog and a fogged band reads LIGHTER than the sky, which is what killed the first two attempts at pinZ+118 and +165), four value bands 0.09→0.26 over 31 yd plus 11 rain shafts; crags 1.6/0.9 → 3.4/2.0 radius and 4.0/2.5 → 8.6/5.4 height. Starfall: uRim adds vec3(0.34,0.24,0.62) over vGd 0.995→1.15; one meteor in three relocated to |x| 13-22 at 42-72% of the hole. Elysium: SUN swings to (-0.72,0.26,-0.64) for par-3 renders only (the daily course keeps the neutral key), uWarm tints ×(1.15,1.02,0.83) with a view-angle rim term, sky ramp re-graded to a late-afternoon gradient, and the repeated colonnade prop is replaced by three ruin variants. Frostreach: 9-15 spindrift ridges combed along hole.wdir — wound so both faces point up, since this renderer has no two-sided lighting and a down-facing normal falls to flat ambient (the first pass drew black arrowheads on white snow), and kept low and wide (0.22-0.38 tall over a 1.5-2.6 yd half-width) for the same reason; shards clustered at 1.55× scale, 5 cones per site. Blossom: uPetal speckles the green from two hashes at 2.7 and 5.3 cycles/yd, near-white against the rose-pink surface (a pink petal on a pink green is invisible), weighted toward the collar; trees 22-34 → 15-23. Aurora: frozen tarn of 11-17 yd radius in translucent ice with nine snow-capped boulders on its rim, at 34-64% of the hole and 30-46 yd lateral; conifers 15-23 → 8-12.
🏌️ Wedge spin-back is measured against its OWN soft-green figure through WEDGE_SPIN_SURFACE (Soft 1.00 / Medium 0.50 / Firm 0.25) rather than the general firmness table, which gave 62% and 42%. PW/SW/LW now check on a firm green at a quarter of the soft impact: PW 0.975/0.488/0.244, SW 1.950/0.975/0.488, LW 2.925/1.463/0.731 for soft/medium/firm. Longer clubs keep firmSpin0 and still need a soft surface to spin at all.
🎯 Hero landmarks moved off the target line: Frostreach's castle from ±4.5 to 27-42 yd lateral, Elysium's temple from ±5 to 30-46, Blossom's pagoda to 24-42, and the torii that stood on the corridor short of the green is removed with its lanterns relocated to the temple approach. Tempest's rain shafts are gone — tapered curtains standing proud of the squall band read as dark cones pasted on the skyline rather than as weather.

v1.0.4 (07/25/2026)

🕳️ The cup is real geometry. buildPuttMesh now carves a genuine circular opening: grid cells falling wholly inside a disc sized off the CELL DIAGONAL (at least 3.2·CUP_R) are dropped and a 40×5 polar collar is laid in from the cup's exact radius out to that disc, so the inner edge is a true circle at CUP_R and the outer edge overlaps the surviving cells (lifted 0.004) with no seam. Sizing the disc off the grid matters: the mesh footprint grows with the putt, so beyond ~35 ft a cell is wider than a fixed disc, no cell is ever wholly inside it, and the cup was never carved at all — verified across 10 worlds × 8 putt lengths from 4 to 80 ft, every one cut. The shaft — wall shaded from lip to floor, plus a floor — is drawn through that opening with ordinary depth testing, and a STENCIL pass masks it to the opening so the interior can never spill onto the green at a grazing angle. The context now requests stencil and verifies STENCIL_BITS before relying on it, falling back to a plain depth-tested shaft otherwise. This replaces two opaque discs laid on the surface, under which the ball simply slid out of sight.
⛳ Chip duration scales with the ground covered (carry + release) by square root, referenced at 18 yd, instead of a flat 1760 ms base. Off a fringe lie at stock loft: 3 yd 1408→732 ms, 6 yd →813, 10 yd →1049, 18 yd unchanged, 26 yd →1690.
🌱 The approach's ground clock had a flat 438 ms floor and then multiplied it by the soft-green and wedge settle factors, so a one-yard hop took 814 ms. The floor now scales with the run and those factors fade out on short ones: 1 yd 814→272 ms, 2 yd →375, 4 yd →663, 30 yd unchanged.

v1.0.3 (07/25/2026)

🎯 Wind's difficulty axis saturates at 14 mph on a concave curve (5 mph = 0.46, 10 mph = 0.78) instead of 32 mph linear; the greenside-hazard budget drops to 0.30, a figure the generator can actually place, and the band fit no longer insets off the top band's upper edge — so 3.0× is attainable. Verified over 3000 generated holes: max is exactly 3.00 and every hole still lands inside its slot's band.
🌱 Firmness rebalanced: base green run Soft 1.5→1.15 / Medium 4.5→6.0 / Firm 6.75, ground-bounce factor Soft 0.6→0.48 / Medium 1.0→1.18 / Firm 1.2→1.35, and spin-back corrected to a receptive-surface trait (Soft 1.3 / Medium 0.8 / Firm 0.55 — the old table had Firm checking hardest). Green landings on Medium/Firm floor at +1.4/+2.2 yd of release.
⛰️ Approach rollout scales with the green's contour along the roll line (±38%), and the landing's lateral kick now reads the full field rather than the hole's fixed lean. The heat map, the chip and the approach all share one green-anchored contour helper.
⚡ Made-putt drop rebuilt: the ball keeps its true size and descends 4.2 radii on a gravity curve (fully below the lip 48% through the sink), replacing a 40% shrink and a 1.6-radius dip that left it mostly above the surface when the draw cut out.
⚡ The hover is gone at its source. rollAlong's quadratic ease-out has zero velocity at t=1, so every putt decelerated to a dead stop on the lip before the drop began; a holed roll now uses a gentler exponent and is travelling 6.6x faster through its final frames (it has to be — a putt that stops short never falls in). The drop itself starts its fall on frame one instead of sliding sideways through a 14% dead lead-in, cutting the motionless frames from 3 to 1 at 60fps, and the ball pivots over the lip into the hole as it descends. The chip's hole-out sink was linear and now follows the same gravity curve.
🥅 Lip-in rim arcs spiral inward (radius x0.26 by the end, 14 samples) so the ball is over the cup's centre when it drops; lip-outs hold radius so they can still be spat out to the resting spot.
🎨 Heat-map alpha comes from the continuous normalized green radius (full to gN 0.96, ramping to 0 at 1.02) on a 0.5 yd lattice. The lattice is now sized off greenMultAt's 1.38 ceiling rather than gHalfW/gDepth — a shaped green bulges past those radii, so the old bounding box clipped the wash into a smaller shape inside the drawn outline (measured 1.35 on a sampled hole).
🔭 The overlay is built by one shared buildHeatMesh used by the tee/approach, greenside chip and top-down views, cached against the green's own signature so no view rebuilds a few thousand quads per frame. From the tee it is offered in Hole view only (the green is too distant to read from the shot view); the chip offers it on both of its screens.
🐛 Tapping the heat toggle in Hole view no longer snaps back to the shot — #stage's click handler treated the toggle's bubbled click as a stage tap, and now skips stage controls the same way the orbit handler already did. Leaving Hole view by any route (button, stage tap, phase change) clears the overlay, so it can't linger over a view that never offered it.
🥅 Break rebuilt around the aim it demands rather than a multiplier chain (the old form multiplied the read by putt length while the read already grew with length, double-counting distance). Anchored at 2° of hold at 6 ft rising to 9° at 60 ft on a max read, with a partial read taking a proportional slice. Measured on max reads: 2.00° / 2.78° / 3.81° / 5.11° / 7.06° / 9.00° at 6/12/20/30/45/60 ft. The 45 ft, 2.7 ft case drops from 13.3° to 6.35°. Pace is renormalized so stock pace is exactly the anchor. BREAK_K retired.
⛰️ Grade now feeds the break read: ×(1 − 0.08·puttGrade) clamped to 0.72–1.32, applied before the ceiling so the panel number is the number the ball obeys and the 4 ft maximum still holds. Uphill ×0.76 … downhill ×1.24 at full grade.
🌾 Rough landings drop their rolling segment entirely and play a hops-only bounce plan at exactly 25% of the clean green/collar height and distance, replacing a 25–50% per-landing roll plus a downhill trickle. Heights are measured against the full clean bounce-plus-roll length rather than sharing the hop scale, the first hop is always kept (a soft green's clean rebound falls under the cutoff and would otherwise leave a pure roll), and the on-screen bounce amplification is switched off so the muffle is not undone for readability. Verified at 0.250 on both axes across Soft/Medium/Firm.

v1.0.2 (07/24/2026)

🌬️ Wind bands retuned to 15% / 45% / 30% / 10% across 0–5, 5–10, 10–20 and 20–30 mph; the rolled wind now overrides the difficulty fit instead of being back-solved by it.
🎯 Distance, wind and greenside-hazard axes each saturate 10% sooner, so a hole reaches its multiplier with less wind and fewer yards. Cap stays 3.0×.
🥅 Putt break capped at 4 ft and scaled by distance (~4 ft at 60 ft, ~1.3 ft at 20 ft) on newly generated greens; existing Daily courses unchanged.
⛳ Slope heat map available during chip setup, and repainted as an interpolated wash across the whole green (no more tile mosaic).
🪁 Chip run-out now scales with the green's slope along the roll line (±38%), with the dashed release preview matching.
🎬 Chip animation tempo reads the loft slider: low runners up to 30% slower, high floaters up to 22% longer with a flatter apex, and the rollout easing tuned by loft.
⚡ Made-putt drop animation halved.

v1.0.1 (07/23/2026)

🎯 Difficulty multiplier reworked to 60% distance / 30% wind / 10% greenside hazards, hardest holes cap at 3.0×.
📅 Daily Challenge scores kept on the This Week / All-Time boards (per-mode cap) and surfaced under My Scores across devices.
📏 Average proximity now logs the tee shot's true distance on greens hit and a flat 100 ft on misses.
🏆 Profile high score backfills from your best leaderboard round.

v1.0.0 (07/22/2026): full public release!

🎯 Daily Darts welcome card — tapping Daily with no round going fades in the date and the live top-3 podium before dealing the nine.
📊 Profile: Birdie % and Average proximity (ft), tracked per hole and synced to your account.
🎨 Background colors in Settings — the default green plus dark red, blue, purple and gray, all tuned so text and lines keep their contrast.
🥅 Putting polish — the distance slider uses fixed bands by putt length (1–20 / 5–30 / 10–50 / 25–75 / 25–100), flat putts drop at stock pace with up to +1.5 ft free, pace execution is capped at ±5 ft, and Frostreach shows its icy overrun in the leave text (❄️ +0.6 ft).
⛳ Short game & lies — chips never squirt backwards, chip speed reads the lie (quicker from fairway/fringe, slower from rough), high chips keep a couple of bounces and a touch of rollout, and fringe landings muffle to 75–80% while rough muffles to 25–50%.
🚩 Red OB stakes line every career corridor 40 yards off the fairway, with the ruling moved to the stakes.
🌲 Tree escapes reworked — Risk It windows scale with Recovery, Luck and distance; Play It Safe spans 50–100% with distance-proportional advancement.
🖱️ Bars lock on finger-down, with a smoother sweep on older phones, a white stock-pace marker on the pace bar, and a true crossfade between scenes.
👋 The white dashed marker, centered labels, and dozens of alignment fixes across phones, iPads and laptops. Thanks for playing the alpha — welcome to 1.0.

v0.9.9 — your challenges, your pace

⚔️ Challenge boards are live — hit Custom challenges on your profile to see everyone who's played your links, best score per player, with a 🏆 on anyone who beat your number. You get 5 live at once and each link runs for 24 hours.
⏭ Skip any chip or putt — a Skip button now rides every short-game and putting animation in every mode. Tap it, ball's at the result.
⛳ Flops got twitchy — the further you bend a chip's loft either way, the hotter its bars sweep, up to 75% faster at the ends of the slider. Stock chips stay stock.
🎯 No more mystery misses from the rough — a loud lie badge (Rough · 65–75% lie), an amber tick on the carry bar marking the number that actually gets there with your club, and the stance called out when it bends your start line (◀ pulls left). Bounces in the rough are muffled now, not buried.
💨 Faster between shots — scene changes are a quick soft fade instead of a dip to black, drives hand off quicker, and the aim line on the mini-map finally points where you're actually aimed. Bigger swing button too.

v0.9.8 — hit the range

🏌️ Practice Range is open — tap Range up top (or Practice Range in the menu) and hit every club in the bag on a dead-flat field: a wide fairway down the middle, rough on the edges, and three outlined target greens at 90, 150 and 220 with floating yardage flags.
🎯 Pick your target — the switcher above Hole view cycles the three greens, auto-selects the right club, and swings the camera onto that flag. Hole view orbits whichever green you've picked.
⚪ Your balls stay where they land — the field fills up as you hit, every leave measured to the nearest flag. One tap on Reset range sweeps it clean.
🔁 The range never costs you a round — duck out mid-Daily or mid-Free-Play, hit a few, and come back to the exact hole and score you left.
⚛️ Real impact physics — landings now simulate restitution, turf friction and spin scrub against the actual terrain angle. Firm skids, soft sits, ice triple-skips, uphill kills the roll and downhill releases — all of it just physics. And the whole sim plays livelier now.
🥇 Red Rocks Classic now opens the tour season.

v0.9.7 — make it yours

👑 Player titles are here — earn them by how you play, lose them if you fall off. GIR Specialist, Elite Putter, Ice Veins, Worldwalker, Top Dog and more, right on your profile.
🥇 Top Dog goes to whoever holds the #1 all-time score — take it and it's yours until someone knocks you off.
📊 New stats on the profile page — longest putt holed, chips holed, water balls survived, recovery saves and long bombs, all synced to your account.
⏩ Way less waiting between holes — transitions are twice as fast, a splash cuts away even quicker, and an ace holds the moment longer with the popup to match.
🏆 Career mode got real fixes — approaches from the rough were freezing every bar in the game, and the drive's aim bar was going blank. Both dead. Bring on the tour.
🎯 Founding Member — if you were here before v1.0, you'll know it when you see the chip.

v0.9.6 — the landing update

⛳ Landings remodeled: a big leading bounce then shorter, decaying skips into the roll — taller, slower hops that read like a real ball, with drives on the same ground game.
🌱 Surfaces react honestly: soft greens bounce bigger and slower and grab 25% more spin-back; firm greens skid lower and quieter with less check; low punches stay flat and release.
⏱️ The ground clock is club- and flight-aware — wedges and low runners settle unhurried while long clubs stay brisk; chips play 25% quicker across the board.
💨 Wind grips tee and approach shots 10% harder at every flight and loft (chipping unaffected).
🥅 After a putt, both bars keep your exact tapped marks and pace band through the roll — no more reset carry box.
👤 The Player Profile is a full page now, its average score comes from your global-leaderboard rounds, and career badges are tucked away until the tour opens.

v0.9.5 — your player profile

👤 New Player Profile page — open it from the profile pop-up (next to Achievements): lifetime holes-in-one, birdies, GIR %, average score, best daily streak and high score across both par-3 modes.
☁️ Your profile now syncs to your account across every device — sign in and your totals follow you.
🏅 New hidden milestone badges for holes played and birdies (100 / 500 / 1,000 / 2,500) — they stay secret until you earn them.
🎯 Missing the center of the tee-shot bar is 25% more forgiving across the whole curve.
🌱 Soft greens are receptive again: a lofted wedge checks and spins back a few yards, scaled by club, loft and wind.
⛳ The greenside chip now starts right under the ball — no more flying in from off-screen — and lofted chips play 20% quicker.
❄️ Frostreach greens deepened to a glacial blue so the putt preview and slope read clearly on top.

v0.9.4 — the putting update

🥅 Rebalanced break: stock pace curls a touch under the read, a dying putt takes more, a firm strike holds its line — with a flatter pace curve behind it.
🔺 The slope readout shows 🔺 Uphill in orange / 🔻 Downhill in blue with the elevation in feet.
📏 Grade is linear and bites harder: 1 ft of uphill ≈ 1¼ ft more pace — a soft tap only rides part of the hill, with a ~1 ft minimum roll so downhill putts stay controllable.
⛰️ Greens can now tilt up to 3 ft of up/downhill and 3 ft of left/right break; putt bars sweep faster and the sweet spot shrinks with distance.
⛳ The recovery chip now shows your ball at its true resting spot — a fringe lie sits on the fringe, never teleported onto the green.
🎬 The hole orbit runs a beat longer, with the restart button and stale aim/carry boxes hidden during cinematics and reveals.

v0.9.3 — polish on the flair

🌋 The volcano looms half again as large, its lava anchored to the mountain — streams run crater-to-base into glowing pools (no more floating sky streaks).
☁️ Skyworld's cloud sea now rides ~20 ft below the islands and its diagram is pure white cloud; the pasted-on cloud puffs are gone.
🥅 Putting: the sweet spot shrinks with distance (15% at 5 ft → 2.5% at 40 ft) and both putt bars sweep 25% faster.
📊 After a swing, the meters keep your exact tapped marks and the club's true carry range through the flight.

v0.9.2 — worlds come alive

🌍 World flair — smoldering meteors on Starfall, seagulls over the Ocean, lava flows (and the odd diagonal river) on the Volcano, drifting clouds under Skyworld, storm-bent willows on Tempest, bigger blossoms with falling petals, olive groves and Greek colonnades in Elysium, glassy ice greens in Frostreach (always Firm).
🎯 Each world's bent rule now sits right under the game view.
⛳ Soft greens take a muffled bounce or two instead of plugging (a high ball into the wind still digs); ground bounces play ~15% calmer; your tapped aim/power marks stay up through the flight.
🥅 Putt pace inside the green band now plays EXACTLY the pace you set; the green view's incline reads true (was ~double); left/right break tops out at 2 ft.

v0.9.1 — meter retune

Club-scaled sweet spots (wedge 15% → driver 5%), a meaner miss curve capped at a true 75%, and putts with a 10% core that punish 25% harder.

v0.9 — the account update

The five big changes since v0.8

🔐 Accounts & Google sign-in — create a free account or continue with Google; your streak, scores and career sync across every device, protected by bcrypt and secure OAuth.
🎯 Daily Darts & sharing — the daily got its new name, shareable result cards linking FlagHunt.io, and custom challenge links with per-link leaderboards and one attempt each.
☢️ Hole-in-one tracker — a global "tee shots since the last ace" counter with a hall of fame, and perfectly flushed approaches now drop in for the ace.
⛳ Real rollout physics & green firmness — club-aware low flight, wind-shaped release, a true bounce-then-roll, and Firm/Medium/Soft greens (shown in the top bar; Blossom always soft, Tempest never firm).
🛡️ Rock-solid rounds — anti-save-scum, forced auto-updates on every deploy, and rounds that survive refreshes, phone calls and device switches.

v0.8.5 — challenge links & the ace tracker

Changes since v0.8.1

Custom challenge links

Post-round mini-leaderboard of everyone who's played that link, with a ⭐ next to whoever shared it.
Two separate buttons: Share result (your brag/lament + emoji recap + the site link) and Create custom challenge (the seeded link).
One attempt per link — reopening it shows the board instead of a replay.
Clear way back to Free Play from a challenge — no more getting stuck on someone's seed.

Hole-in-one tracker ☢️

New ⭐ button opens a tracker showing how many tee shots have been hit since the last ace anywhere…
…and a hall of fame logging every hole-in-one — player, world, the drought it broke, and the date.
A perfectly flushed approach that finishes over the cup now drops in for a hole-in-one.
Aces show a ☢️ on the scorecard and the hole-by-hole grid.

Shots & fixes

Lower-lofted shots and clubs run out more, with the rollout curving along the wind and your shot shape.
Anti-cheat: refreshing on the green (or mid-shot) no longer resets the hole.
New footer to send bug reports and feedback by email or Twitter/X.

Hole in one 🎯	+1.0
Elite approach + birdie	+0.75
Made birdie	+0.5
Elite approach, no birdie	+0.5
Great approach, no birdie	+0.25

Elite 🎯	6000+
Great ✅	4500 to 5999
Good	2500 to 4499
Decent	1000 to 2499
Mediocre	under 1000

Hole in one	5000
Inside 2.5 ft	2500
5 ft	2000
10 ft	1500
20 ft	1000
40 ft	500

⚠️ This link is unavailable

⚔️ Tour Clash

Profile

Daily scores

New update released

Welcome back 🎯

Protect your streak 📮

Your streak is one day cold ❄️

Nice round 🎯

Check out the settings menu!

Log in

Create account

Choose a username

How to play

The shot

Green firmness

Points

Combo multiplier

Proximity score

Shot rating

Recovery chip

The 9 hole types

Leaderboard

The tour

Your ratings

Trouble

Weather

The pro shop

Season stats

Golfer

Settings

⭐ Hole-in-one tracker

Welcome to the Daily Darts 🎯

Daily Blitz ⚡

⚔️ My challenges

Play custom challenge

⚔️ Challenge

What's new · v1.1.0

v1.1.0 (09/01/2026)

v1.0.9 (08/27/2026)

v1.0.8 (08/08/2026)

v1.0.7 (08/08/2026)

v1.0.6 (08/05/2026)

v1.0.5 (07/26/2026)

v1.0.4 (07/25/2026)

v1.0.3 (07/25/2026)

v1.0.2 (07/24/2026)

v1.0.1 (07/23/2026)

v1.0.0 (07/22/2026): full public release!

Alpha changelog — every patch note

09/07/2026 — the duel, watched properly

09/07/2026 — the daily reward track goes back behind the gate

09/05/2026 — the golfer is yours now

09/03/2026 — somebody is hitting the ball

09/03/2026 — an email on every account, and consent as its own question

09/03/2026 — a reason to come back tomorrow, and a reason to sign in

09/03/2026 — Mental is wired: pressure, and the nerve that answers it

09/03/2026 — the trees are trees now, and the tee swings like the approach

09/02/2026 — watching looks like watching, and a new day opens on the daily

09/02/2026 — the clash, watched properly

09/02/2026 — nothing carries out of the Blitz

09/02/2026 — the birdie ladder counts birdies, not holes

09/02/2026 — nine career bugs that were one leaked flag

09/02/2026 — watching a duel: the replay is a broadcast, not a glitch

09/02/2026 — the blitz clock stays in the blitz

09/01/2026 — the putt read: one button in the short modes

09/01/2026 — the clock no longer runs behind the welcome card

09/01/2026 — the Blitz result reads as one thing

09/01/2026 — one door, and the retired links say so

09/01/2026 — career joins the switcher

09/01/2026 — the menu, trimmed

09/01/2026 — the switcher ships; the three new modes read "Soon"

09/01/2026 — the mode switcher

08/31/2026 — Daily Blitz, its own scoring economy

08/31/2026 — Daily Blitz, built but gated

09/01/2026 — Daily Blitz is timed

09/01/2026 — Tour Clash: the replay is exact, and it waits its turn

09/01/2026 — Tour Clash: watch them set up, and watch the putt roll

09/01/2026 — Tour Clash fixes (from live two-player testing)