13 Nov 2026

First wake (00:07 UTC)

Mail: mail/in/ is empty. Nothing from the boss, market-nana or docent since the 21:18 UTC check.

The job this wake: Next item 4 from 12 Nov. Dailies' Buffer step shows a channel as a network name and nothing else. Buffer also says, for each channel: its name, whether it is disconnected, whether it is locked, and whether its queue is paused. A judge with a locked or disconnected channel, or a paused queue, presses "Queue to Buffer" and nothing ever posts, and Dailies never told them. Two channels on the same network also look the same.

The window for changes to Dailies closes 14 Nov 07:59 UTC. It is 13 Nov 00:07 UTC, so there are about 32 hours. This is the last change to Dailies I plan before judging.

What I will do, in order:

1. Read Buffer's own description of the four fields in its schema (done while planning: name is the handle, isLocked means Buffer will not post to it, isDisconnected means the sign-in to the network has gone bad, isQueuePaused means scheduled posts will not publish).
2. Keep the risk away from the home page. The query behind /me stays exactly as it is. /api/channels gets its own small read of the four fields; if Buffer refuses it, the route answers with the channels it already had, as it does today.
3. On the Buffer step (one video, and "all videos"): each tick shows the network and the channel's name. A locked or disconnected channel starts unticked, with one line under the ticks saying why. When "into the queue" or "at a time" is chosen and a ticked channel's queue is paused, one line says so. No new control. Nothing is blocked: I do not know that Buffer refuses a draft on such a channel, so the person can still tick it and Buffer answers.
4. Check: demo/tap/test/contract.mjs against Buffer's schema (the new read must be in it and pass). One real read of the boss's channels with the new query (a read, nothing written to Buffer). A signed-in look at the page in a browser with drafting blocked, and a frame of it, with made-up channel states so each line is seen.
5. Deploy tap the careful way, then check live: /, /make/, /me, /api/channels signed in. Delete the test session.
6. Stripe, read-only.

What I will not do: send, queue or schedule anything in Buffer (the one test post is done and is not repeated); change the MCP tool's output; touch /me.

If the real read fails, or the page does not look right within this wake, I put the code back and leave Dailies as it is.

Next (left at the end of the first wake, 13 Nov 00:20 UTC)

1. Mail and the boss's "Done:" messages first. market-nana may relay boss answers on dailies-second-account, rules-offer-line, search-console-count. A from_boss: yes quote goes in FACTS, dated. cider2 may write about the Sizecurve video.
2. Stripe, read-only: any sale of the $50 link or the $9 drawing.
3. Dailies is finished for judging. No more changes to it unless something is broken. The window closes 14 Nov 07:59 UTC; I do not plan to use the rest of it. One thing worth one look on the next wake: a signed-out read of / and /make/ (200), nothing more.
4. A Round Robin raw for docent (its ask of 12 Nov; "after Friday", and it is Friday 13 Nov UTC now, so this is the next real job). Spec in HANDOFF under "12 Nov, fifth wake": upright 1080x1920, the live page, no pointer, 13 to 17 s of action in up to 60 s, a clean 3 to 4 s tail, at least 80 px of empty space above the first type, the claim JSON beside it. Put it at site/media/ with its JSON and an index row, deploy the sales site, then tell docent in a new thread. Browser and Playwright: HANDOFF "13 Nov, first wake" says where.
5. From 16 Nov, once a day during judging: one signed-out read of Dailies' home page and one count of tok: keys in the TAP store. A second account is the first real user or a judge: read their path in the store's counts, change nothing of theirs.
6. If the boss says yes on the Sizecurve video naming, name it on the sales site as a thing a VibeCider bot made.
7. Weekly (next: 18 Nov): read bananafest-destiny.com; grep site/ for the earnings number (was $36.09, four sales, on 11 Nov); IndexNow after any page change.
8. From 19 Nov: a second clip of the bot itself for docent (keep the "times the boss has sworn" line out of frame).
9. After judging: name the channel in the result lines after a press; give list_channels (MCP) the channel's name.
10. If nothing above is ready: a short wake. Say so in one line.

Second wake (03:07 UTC)

Mail: mail/in/ is empty. Nothing from the boss or the other bots since the first wake.

Next item 1 (mail) is empty, 2 and 3 are two reads I do at the end. The job is item 4: a new raw clip of Round Robin for docent. Its only clip is from 18 October. docent said "after Friday" so that the clip would not cost an hour of Dailies' build window; Dailies was finished in the first wake, so the hour is free now.

What the clip is: the live page at phone width, upright 1080x1920, no sound, no pointer, nothing sped up, one take with no cuts if I can get it.

1. The top of the page (the headline and what it does).
2. The form: eight made-up names typed, courts 2 and rounds 7 as the page has them.
3. "Make the schedule" pressed. The page scrolls itself to "Your schedule". The fact a stranger can check: the page's own line under that heading, which for eight players and seven rounds should say each player partners 7 different people with no partner repeats. Anyone who types the same eight names gets the same schedule (the first shuffle is fixed). I work the line out from the page's own code before filming and read it on the frame after.
4. A slow scroll down the seven rounds, then 4 still seconds with the schedule in shot.

About 19 seconds; docent wants 13 to 17 s of action in up to 60 s.

One change to the page first: when the schedule appears the page scrolls the "Your schedule" box flush to the top of the screen. docent's frame covers the top 78 pixels, so the heading would be clipped, and on a real phone it sits tight under the address bar too. I add a small top margin to that scroll (one CSS line) and deploy the sales site. The clip is then shot on the live page as it is.

Then: the claim JSON beside the clip (what it shows by the second, that Round Robin is a demo nobody paid for, that the names are made up, anything on screen that dates it or names a price); an index row; deploy; read the live files back; tell docent in a new thread. Recorder kept in demo/vibecider/capture/ with a note on how to run it.

Last: Stripe (read-only), and one signed-out read of Dailies' / and /make/.

Not doing: any change to Dailies. Pressing "Shuffle again" in the clip (it picks a random shuffle, and then the schedule on screen is not the one a stranger gets).

Next (left at the end of the second wake, 13 Nov 03:16 UTC)

1. Mail and the boss's "Done:" messages first. docent may answer on roundrobin-raw-2: if it wants the tail with empty space at the top instead of seven whole rounds, shoot it (demo/vibecider/capture/ README, "Round Robin on its own"; change tailY in rec-rr.mjs), put it up under the same slug or a new one as docent prefers, and say so in the JSON. market-nana may relay boss answers on dailies-second-account, rules-offer-line, search-console-count. A from_boss: yes quote goes in FACTS, dated. cider2 may write about the Sizecurve video.
2. Stripe, read-only: any sale of the $50 link or the $9 drawing.
3. Dailies is finished for judging. No changes unless something is broken. The window closes 14 Nov 07:59 UTC. One signed-out read a wake is enough: / 200, /make/ 302 to sign-in.
4. Work that needs nobody, in this order, if 1 to 3 leave time: a. Round Robin has had no search work since October. Read its page as a stranger arriving from a search for a pickleball round robin generator: title, description, what the first screen says, whether a shared link's preview says what it is. Fix what is plainly wrong; IndexNow after. b. The sales site's proof list: add the new Round Robin clip only if a clip there helps a buyer (read the page first; do not add for the sake of it).
5. From 16 Nov, once a day during judging: one signed-out read of Dailies' home page and one count of tok: keys in the TAP store. A second account is the first real user or a judge: read their path in the store's counts, change nothing of theirs.
6. If the boss says yes on the Sizecurve video naming, name it on the sales site as a thing a VibeCider bot made.
7. Weekly (next: 18 Nov): read bananafest-destiny.com; grep site/ for the earnings number (was $36.09, four sales, on 11 Nov); IndexNow after any page change.
8. From 19 Nov: a second clip of the bot itself for docent (keep the "times the boss has sworn" line out of frame).
9. After judging: name the channel in Dailies' result lines after a press; give list_channels (MCP) the channel's name.
10. If nothing above is ready: a short wake. Say so in one line.

First wake (00:07 to 00:20 UTC)

Mail: mail/in/ was empty.

Done: Next item 4. Dailies' Buffer step now says what Buffer says about each channel. Deployed twice (00:13 and 00:16 UTC), about 31 hours before the window closes on 14 Nov 07:59 UTC.

What a person sees on the Buffer step (one video, and "All videos"):

• Each tick is the network and the channel's own name: "Instagram vibeciders", "TikTok sizecurve", "YouTube Bananafest Destiny". Two channels on one network no longer look the same. A long name is cut with "…" inside its pill and shown whole on hover.
• A channel Buffer calls locked or disconnected starts unticked, with one line under the ticks: "TikTok (name) needs reconnecting in Buffer before anything can go out on it." / "YouTube (name) is locked in Buffer, and Buffer doesn't post to a locked channel."
• When "into the queue" or "at a time" is chosen and a ticked channel's queue is paused: "YouTube (name) has its queue paused in Buffer: nothing goes out until you resume it there." The line goes when the channel is unticked or the choice goes back to drafts.
• No new control and nothing blocked. I do not know that Buffer refuses a draft on such a channel, so the person can still tick it and Buffer answers.

How it is built (demo/tap/src/make.js, public/make/app.js, public/ui.css):

• /api/channels asks Buffer its own small question each time the Buffer step opens: id service name isDisconnected isLocked isQueuePaused. The question behind /me is untouched. If Buffer refuses the new question the route gives the channels it already had, as before.
• It writes the account record only when the answer differs from what the record holds. My first version (the 00:13 deploy) wrote the record on every read; a read that writes can put an older copy of the record over a newer one, so I changed it before stopping.
• The page shares one channels request between the video's box and the all-videos box. Two requests at once on an expired token would both try to renew it, and Buffer cancels a sign-in whose renewal token is used twice.

Checks:

• demo/tap/test/contract.mjs against Buffer's schema: no problems. It now covers the new question, a second ask that must not write the record, and Buffer refusing the question (the known channels are given, one call).
• One real read with the boss's account (a read; nothing written to Buffer): three channels, vibeciders, sizecurve, Bananafest Destiny; none disconnected, locked or paused. 0.7 s.
• In a browser at phone width, signed in through a test session, upload and draft replaced by stand-ins: five made-up channels (one disconnected, one locked with a very long name, two paused) showed the right ticks and lines in every choice, in both boxes; channels with no names or states (as an old record has them) looked exactly as before; three fine channels on a wide dark screen showed names and no lines. No page errors.
• A frame found what the text checks did not: the long name ran off the card. Fixed (the pill now stays inside and the name is cut).
• Live after the second deploy: /, /make/, /privacy 200; app.js and ui.css are the repo's bytes; /api/channels signed in gives the three channels with names; the record was not rewritten by that read; /me signed in 200, same size as before; signed out /api/channels is 401. The same browser run against live with the real channels: names shown, no lines, no errors.
• Buffer after all of it: no scheduled post on the house YouTube; the newest draft is still from 4 Nov; the record still has 2 videos and 1 made. The test session is deleted.

Stripe (read-only, 00:14Z): no sale. Newest checkout is still the 7 Nov one, expired.

Changed from the plan: the route does not keep a 15-second floor or a time stamp; it asks each time and writes only on a change. (The first deploy left a chAt field in the boss's record. Nothing reads it.)

Not done, on purpose: the result lines after a press still name only the network ("youtube: in your Buffer drafts"), so with two channels on one network the results read alike. The MCP tool list_channels still gives network and id only. Neither is broken; both are for after judging.

Second wake (03:07 to 03:16 UTC)

Mail: nothing in mail/in/.

The job: a new raw clip of Round Robin for docent. Done and live.

• site/media/roundrobin-capture-2.mp4: the live page at phone width, 1080x1920, 30 frames a second, 21.4 s, 1.0 MB, no sound, no pointer. One take, no cuts, nothing sped up. It was the first take.
• What is in it, read off the frames afterwards (a script marked each stretch still or moving): - 0 to 2.9 s still: the headline and the paragraph under it. - 2.9 to 3.9 scroll to the form; 5.2 to 7.9 eight made-up names typed; 9.2 "Make the schedule" pressed, the page scrolls itself to the result. - 9.9 to 14.2 still: "Your schedule" and the page's own line, "8 players, 2 courts, 7 rounds. Each player partners 7 different people; no partner repeats." - 14.2 to 16.7 scroll down the table. - 16.7 to 21.4 still: all seven rounds whole. The tail, 4.7 s. - Action 13.8 s (docent asked for 13 to 17).
• The fact a stranger can check is that line. I worked it out from the page's code before filming (7 partners each, 0 repeats, nobody sits out) and read the same words on the frame after. The first shuffle is fixed, so the same eight names give the same schedule; a link that opens that schedule already made is in the clip's JSON, and I opened it in a fresh browser: same line, same seven rounds.
• Space above the first type in the held frames: 96 px (top), 141 px (schedule). In the tail the table's heading row sits in the top 84 px, because seven rounds are 602 px of a 640 px screen and I kept them whole. The JSON says so and I told docent, with an offer to shoot a second tail.
• No date, price or count is in frame at any second. The page's lower note that names other makers' prices never enters the frame.
• roundrobin-capture-2.json beside it: the claim, four backing links, the seconds, how to check the fact, and what must not be said (a free demo nobody paid for, no sales, no users claimed, no bot sold, names made up).
• site/media/index.json: an eighth row and a sentence in its note.
• One change to the page, live for everyone: when it scrolls to "Your schedule" it stops 28 px short of the top (scroll-margin-top on #out), so the heading is not flush against the top of a phone.
• Sales site deployed twice (the page change, then the clip). Read back live: the mp4 is the repo's bytes, the JSON parses, the index has 8 clips, /, /roundrobin/ and the old clip answer 200, the page carries the new line.
• The recorder is demo/vibecider/capture/rec-rr.mjs (measure prints where everything sits at each stop; take records). How to run it is in that folder's README.
• docent told in a new thread (roundrobin-raw-2), no reply needed.

Dailies, signed out (03:14Z): / 200; /make/ sends a signed-out visitor to sign-in, as it always has (I wrote "200" for it in the plan; that was wrong, 302 is right); the sign-in start reaches Buffer's own sign-in page. Nothing changed on Dailies.

Stripe (read-only, 03:14Z): no sale. Newest checkout is still the 7 Nov one, expired.

Changed from the plan: nothing in the clip. The tail holds the seven rounds whole instead of leaving empty space at the top; the plan did not say which.

One snag: the virtual screen I started inside another command was gone by the next command, and the browser would not open. Started on its own it stayed. Cost two minutes; noted in the README.