Cryptograss:Moods/magenta-interface/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
To-do: #155 went to main; #157 to production (via update-page on MediaWiki MCP Server) |
To-do: sprint notes built (#154) (via update-page on MediaWiki MCP Server) |
||
| Line 315: | Line 315: | ||
who: magent | who: magent | ||
kind: code | kind: code | ||
note: "Medium-term (Justin, 24 Oct 05:33Z): sometimes a message is just the perfect little snapshot of what to note. | note: "Medium-term (Justin, 24 Oct 05:33Z): sometimes a message is just the perfect little snapshot of what to note. Settled with re, 25 Oct: the sprint is what Magenta:Current sprint names; notes on Magenta:Sprints/<sprint>/<person>; a note keeps words and link. Built in magenta#154." | ||
link: https://github.com/cryptograss/magenta/pull/154 | |||
- task: "Waiting: an agent can choose to wait for another asked the same thing, as a state shown in the Mood, ending in the other's answer or a quiet spell; mutual waits broken by who was named first; then who's waiting, shown" | - task: "Waiting: an agent can choose to wait for another asked the same thing, as a state shown in the Mood, ending in the other's answer or a quiet spell; mutual waits broken by who was named first; then who's waiting, shown" | ||
who: magent | who: magent | ||
Revision as of 02:36, 25 October 2026
What the people in #magenta-interface have to do. magenta shows this list beside the Mood (memory-lane services/todo.py). Edit the YAML below: - task: ..., with who, kind, link, note and done as useful. Agents add what they leave someone to do, and mark what's done. Put a task in quotes if it has ": " or " #" in it (YAML reads those as a key and a comment); `backticks` make code.
- ☐Add your slogan to Magenta:Slogans as yourself: a line starting with *. Verifying the page's intro at Special:VerifyBotEdits is welcome tooA line magent writes waits as {{Bot_proposes}} until a person verifies it, and magenta#116 keeps such lines off the front page until then.
- ☐Verify Magenta:Voice (Special:VerifyBotEdits), so its lists are the ones used: only a trusted editor's revision countsUntil then the code's own lists, the same words, are used. Add a Said as line to hear the difference.
- ☐Sprint notes: "add this message to my current sprint notes" on any message, each of us keeping our own notes for a sprintMedium-term (Justin, 24 Oct 05:33Z): sometimes a message is just the perfect little snapshot of what to note. Settled with re, 25 Oct: the sprint is what Magenta:Current sprint names; notes on Magenta:Sprints/<sprint>/<person>; a note keeps words and link. Built in magenta#154.
- ☐The wake's fixed lines (others mentioned, how to hand off, how to set settings, waiting) on PickiPedia beside Cryptograss:Moods/Dials, read as the dial texts are (trusted editors only; the code's text if not)Justin, 24 Oct 05:48Z: where does that phrase live? In poller/mood_poller.py today. On the wiki it's readable, editable, and documented where it's used.
- ☐Tidings, still to build: #t- autocomplete in the composer; PickiPedia's backlinks know #t- links; download and keep yt-dlp-supported videos (no such fetcher exists yet); DrivingThatTrain writes Cryptograss:Tidings/top for Template:Top tidingsNot built: ticked by #111's merge, which only linked it. No PR link here until there is one.
- ☐Test faces end to end on a real photo of people: Who's in it?, naming a face, the names on Tidings, Depicts on a PickiPedia uploadJustin, 08:25Z: we haven't tested faces yet. magent can drive it with him once #109 is live.
- ☐Make Tidings and Prompts answer faster than their 1.5–2.6 s and 1.1–1.6 s (21 Oct, live)The picture scan (a LIKE over messages) and the link and prompt counting. Measure where the time goes first.
- ☐Find the flaky test: one full run on 21 Oct (05:30Z, look-dialog branch) had 4 failures and 4 errors; three runs after passedNot caught again in 13 runs. Found: three tests reach the network, and test_clips_library's posts start a Yarn fetch thread that can write during later tests (the likeliest cause). Plan in the issue: block the network in tests, mock those, keep_later inline.
- ☐Build each link's discussion on Tidings: its message's reply tree, read Hacker News style, with a box to reply from there; then tags on messagesJustin's 17:36Z memo. Comments are the message's replies, not a record apart. Forked agent sessions for a link's discussion: later, forked when first addressed there.
- ☐Stop magenta recording harness-added text as magent's own message: a loaded skill's text (22:11Z, 19 Oct) and an image's size note ('[Image: original 2360x1384…]', 16:48Z, 20 Oct)Cause not looked at yet: likely how the importer reads text the harness adds to a session.
- ☐Deploy delivery-kid: maybelle-config#207 (merged) gives its /health an uptime, which the status page shows; it was last deployed 15 Oct
- ☐Decide: give memory-lane on maybelle a GitHub token, so the status page's pickipedia-mcp comparison and the to-do lists' merge checks aren't left to GitHub's 60 calls an hour for unauthenticated requests (the status page says 'could not query GitHub: HTTPError')maybelle_github_token is in the vault but goes only to Jenkins, and may carry more than reading needs. A token with no scopes reads public repositories; it would be a new vault key. The same eight calls work from hunter: 29 ahead of upstream's v0.19.0, 0 behind, upstream 23 on since. At 15:27Z on 20 Oct the live page read GitHub fine, which fits a rate limit that comes and goes: so not urgent, but it will be back on a busy hour.
- ☐Build a status page for agents: every vendor each harness knows, and which have keysJustin, 16:22Z on 18 Oct: the vendors without a key leave the settings menu (#220) and show there instead.
- ☐Give re and the Mood containers our wiki tool instead of npx @latest (maybelle-config PR), now pickipedia-mcp#30 is in#30 merged 05:36Z and is live in magent's own workspace (ef685da): whoami and a signed-in write to User:Magent/sandbox work.
- ☐Decide how long the offsite copy is kept: today it mirrors daily/ (7 days). E.g. Sunday's dump kept 8 weeks and the 1st of each month kept a year, in their own folders, outside the --deleteA dump is about 395 MB and growing. The 7-day mirror is about 2.8 GB offsite; adding 8 weekly and 12 monthly copies is about 8 GB more.
- ☐Decide, before the freeze: memory-lane#165 (record events docs, proposed) and #74 (memory commitment): merge, close, or carry into magenta
- ☐Rebase memory-lane#201 (Sky's brighter folded settings line) onto #213 once #213 is in: both change the settings row
- ☐Agents' turns read like chat: one block per wake (two agents at once no longer shred into strips); the answer stands as a message, the work folded behind one line; thinking shut by default, in a panel of its own; notes along the way smaller than the answerJustin said go, 03:34Z on 18 Oct. Thinking folded with the steps: memory-lane#217. Still open: notes along the way smaller than the answer; a line for re's instructions: think, then write the reply once (it drafts the whole reply in its thinking).
- ☐Decide: a what's-in-it pass beside faces (instruments and setting by OpenCLIP, banner and sign text by OCR), written onto the photo's PickiPedia page?Same container on hunter, open models only. magent proposed it 17 Oct; waiting on your go.
- ☐
- ☐Put up reference photos: three or four clear face shots of each friend, each file page with {{Face reference|Their Name}}Anyone can do this; a dozen friends before IBMA is a good start. faces reads the category every ten minutes. magent's census, 01:2xZ on 18 Oct: of 52 people pages, 41 have no photo; only Justin has three clear shots of his face. Ready to mark now (the person is the only or largest face): Justin, Justin-seoul-sesame.jpg, Justin-st-pete-thompson.jpg, Justin-Holmes-Dees-East-Nash.png; Jake Stargel, Jake Stargel 58957.png and Tony-rice-jake-stargel.png; Cory Walker, Cory Loyd Walker Customer of the Year Award.jpg; Kyle Tuttle, Kyle Tuttle under the lights.jpg; Maddie Denton, Maddie Denton with Guitar.png. Wants a person's eye first: Skyler-justin-cory.jpeg (largest face, Skyler by elimination) and Harry Clark's mando photo (largest face, Harry by elimination).
- ☐Photos for the people pages without a usable face: 41 with no photo at all, and Tony Rice; Gaven Largent (his face is 48 pixels), Samson Grisman (two faces: which?) and Brendan Daniel (no face found)The IBMA photos can fill these. One clear, near, front-on face of 100 pixels or more makes a reference; a group photo serves only for its largest face.
- ☐Merge magenta#47 (magenta.sh reconnect: sign Claude in again in the container)Pull magenta after: magenta.sh runs from your own checkout.
- ☐Say which wallet is yours on User:SkymanJenkins, as an Ethereum Address the way User:JMyles does (your 3 Blue Railroads then show)The leaderboard has you at 0x5da9…cF4F. Any PickiPedia user page with an Ethereum Address gets the count.
- ☐Blue Railroads beside user links on PickiPedia tooNo extension decorates user links yet: a hook (HtmlPageLinkRendererEnd) in PickiPediaContent, the same count.
- ☐Try read-all in the car, after the voice PRs are deployedThe real test of ▶'s first sound, memos sent at stop, "Magent is thinking", and now "Pound general" and redeploys said.
- ☐
- ☐
- ☐
- ☐
- ☐
- ☐
- ☐Merge #147: magenta.sh clips save <file> <start> <end> "<subtitle>" (includes #113, agents playing clips); then redeploy maybelle (migration 0038) and pull your checkout for magenta.shNow also --preview (watch, replay, retime, then save) and words under a played clip.
- ☐
- ☐
Done (258)
- ☑Merge magenta#76 (a turn's heading says when it began; clicking that time copies the turn's link), and deploy maybelleFrom 00:22Z on 20 Oct. 934 tests OK.
- ☑Build 'tidings', beside status and settings: the last 20 pictures sent (who sent each, whether it's on PickiPedia, whether faces have looked at it), and each person's last 20 prompts (a message mentioning an agent, or the one before a short mention by the same person)Justin, 00:22Z on 20 Oct. re builds it; magent opens the PR from re's commits.
- ☑Merge magenta#78 (tidings: re's build, magent's review fixes), and deploy maybelle968 tests OK. Pictures only from Mood posts; a short nudge pairs only within 10 minutes.
- ☑Merge magenta#81 (a merge ticks every item linking it, and leaves a done said in words), and deploy maybelle#78's merge item went unticked, and re's worded done was overwritten: the bot stopped at the first item linking the PR. 971 tests OK.
- ☑Merge magenta#82 (tidings: compact gallery with small previews, each prompt's tokens and cost, times as links), and deploy maybelleJustin's five asks, 15:36Z on 20 Oct: re built them; magent's review fixes on top. 984 tests OK.
- ☑Merge magenta#83 (an agent woken by another is at work since its wake, not since the other began), and deploy maybelleJustin, 15:52Z on 20 Oct. Both clocks: the activity line and the turn heading. #81, #82 and #83 merge together cleanly.
- ☑Merge magenta#84 (thoughts as rings holding their word count; a quiet wake that thought, a dot holding its count), and deploy maybelleJustin, 16:44Z–16:50Z on 20 Oct, from the mockup he liked. #81–#84 merge together cleanly. Keep the mockup-thought-dots branch: the pictures in the Mood and in #84 link to it.
- ☑Merge magenta#85 (a memo posted without its words can be heard again by whoever sent it), and deploy maybelleJustin, 17:58Z on 20 Oct: ElevenLabs out of credit on the 17:36Z memo. After the deploy, '↻ hear it again' under it. 991 tests OK.
- ☑Merge magenta#86 (a message's own address: /messages/<id>, wherever it lives), and deploy maybelleJustin's 17:36Z memo. 997 tests OK. #86, #87 and #88 merge together in any order.
- ☑Merge magenta#88 (re's Prompts tab: /moods/prompts/ and /api/prompts/), and deploy maybellere built it, 18:13Z on 20 Oct. /api/tidings/ no longer carries prompts.
- ☑Merge magenta#87 (links on Tidings: promoted from a message's ⋯ menu), and deploy maybelleIncludes #88, its conflict resolved. Migration 0031 (tidings). 999 tests OK.
- ☑Merge magenta#90 (reading as they come: a clip that couldn't be fetched is tried again, never dropped), and deploy maybelleJustin's 18:38Z memo: the messages missed while another was read. The phone's own reports showed the clip requests failing and the reader dropping them unheard.
- ☑Merge magenta#91 (an agent said by its colour: 'the red agent' is re, 'at the red agent' is @re), and deploy maybelleJustin's 18:38Z memo. #86, #87, #88, #90 and #91 merge together cleanly.
- ☑Merge magenta#92 (a voice memo knows its length: written in when it's kept, found when an old one is played), and deploy maybelleJustin, 03:13Z on 21 Oct: total time and slider. MediaRecorder's WebM has no duration (ffprobe: N/A); now written in on upload. 1012 tests OK.
- ☑Merge magenta#93 (Promote to Tidings: whoever promotes picks which of a message's links), and deploy maybelleJustin, 03:13Z on 21 Oct. Migration 0032. #92 and #93 merge together cleanly.
- ☑Merge magenta#94 (prompts: a few questions of the database, not one per agent row and two per reply), and deploy maybellere found the prompts page taking ~20 s live (21 Oct). 5,253 queries → 9 on a seeded record. #92, #93 and #94 merge together cleanly.
- ☑Merge magenta#95 (agents' colours brighter: re #ff3c00, magent #ff67fd), and deploy maybelleJustin, 03:49Z on 21 Oct. #89 (blu) carries the identical line now: the two merge in either order, and with #92–#94.
- ☑Merge magenta#96 (your name written your way, BBS-style; your icon's colour; agents at work in theirs), and deploy maybelleJustin, 03:53Z on 21 Oct. Set from 'your name' in the account menu. Merges cleanly with #89 and #92–#95 in any order.
- ☑Look at magenta#98 (the top bar: magenta › moods › the Mood ✎, then tidings, prompts, status): merge if it's how you pictured itJustin, 04:43Z on 21 Oct: 'can I see how that will look?' Screenshots in the PR. #97 and #98 merge together cleanly.
- ☑Merge magenta#99 (the top bar never scrolls: what doesn't fit goes, least needed first), and deploy maybelleJustin, 04:52Z on 21 Oct: a scrollbar, 'status' cut off. Checked from 1600 px to 700 px, with '↻ new version' showing.
- ☑Merge magenta#100 (the top bar: the Mood's name at its own width, no gap), and deploy maybelleFollow-up to #99. Justin's screenshot (05:08Z, 21 Oct) found it: the sections were a <nav>, and the page's nav rule (the Moods pane's: 190 px, scrolling, a border) boxed them. Fixed here; checked at his width and 1.5x zoom.
- ☑Merge magenta#101 (one page: tidings, prompts, status and settings beside the Moods, each loaded once and kept; the mark alone; ⚙), and deploy maybelleJustin, 05:21Z on 21 Oct. Checked in a browser: back and forth reloads nothing; a link in Tidings opens its message in Moods. 1023 tests OK.
- ☑Merge magenta#102 (the name dialog: 'How your name will be displayed', your PickiPedia name, started from it, the sixteen colours), and deploy maybelleJustin, 05:26Z on 21 Oct. #101, #102 and #89 merge together cleanly.
- ☑Merge magenta#103 (the name dialog: the characters a BBS drew with, pressed into your name), and deploy maybelleJustin, 05:46Z on 21 Oct: the characters, not the colours. CP437's 256. 1025 tests OK.
- ☑Merge magenta#105 (names in a BBS's colours, backgrounds too; the characters' chart opens and closes), and deploy maybelleJustin, 06:05Z on 21 Oct. The chart never closed in #103 (display: grid outranked [hidden]). 1026 tests OK.
- ☑Merge magenta#106 (a section on its way says so; two tests brought up to date with blu), and deploy maybelleJustin, 06:17Z on 21 Oct. Also fixes main's suite: two tests fail since #89 (blu) merged. 1026 tests OK.
- ☑
- ☑Tidings follow-ups: comments drawn with their paragraphs and code (not one flattened line); a retitle/withdraw menu on a link's discussion pageBuilt in magenta#109, with Justin's 08:25Z round.
- ☑
- ☑
- ☑Reconcile re's round 2 with #109 and review it: TidingComment words drawn as the Mood draws themIn magenta#111, with review fixes (background refresh, tags, titles,
- ☑
- ☑Write Magenta:Slogans on PickiPedia, Justin's line first, once the namespace is liveWritten 22 Oct. The wiki wraps a bot's lines in {{Bot_proposes}}, so the slogan line itself is for a person (below); the front page shows Justin's line meanwhile.
- ☑
- ☑Once #119 is live: read from the record whether eleven_v4 honours a Mood's voice speed (words a second of clips at 1.2 against a Mood at 1.0), and say23 Oct: taken, but my voice came back about a fifth SLOWER at 1.2 (12.0 characters a second against 14.9 without). magenta#122 makes 1.0 the default until it's understood.
- ☑
- ☑Merge magenta#123 (voices on the settings page, found by typing from ElevenLabs' whole library, or an id pasted; the floating menu goes), then deploy maybelleNo migration. Choosing a library voice adds it to the ElevenLabs account, which takes an SSH key: the plan holds so many voices.
- ☑The same words at three speeds: once #122 is live, ▶ magent's message #m-a7e7cce6 in #magent-self (it was made at 1.2; it's made again at 1.0); then set #magent-self's voice speed to 0.8 on the settings page and ▶ it once moremagent reads each clip's length from the record and says whether 1.2 is faster, slower, or the same as 1.0, and 0.8 the other way. A few cents of ElevenLabs. 23 Oct 04:53Z: done -- all three the same length within 1% (31.3/31.0/31.0 s; 61.0/61.2/60.5 s): Eleven v4 ignores speed, as its docs say. magenta#125 takes the setting out.
- ☑Merge magenta#125 (no Mood voice speed: Eleven v4 takes a speed and ignores it), then deploy maybelleNo migration. #magent-self's saved 0.8 becomes inert.
- ☑Merge magenta#126 (agents on Tidings: @agent in a comment wakes it in the link's Mood; its answer comes back under the comment; agents' comments don't raise a link), then deploy maybelle AND hunterNo migration. hunter carries the poller, which tells memory-lane what woke a turn: without it, agents are woken but their answers stay in the Mood.
- ☑Merge magenta#127 (a memo whose microphone goes quiet: stopped after 10 s of dead mic and said, with 'record again'; a silent tail not sent; Ctrl+Enter says a Tidings comment), then deploy maybelleNo migration; page only. From the handoff out of #magent-self (the 8:23 memo silent after 2:24).
- ☑Merge magenta#128 (the front page's address as a QR code at its foot; on a phone, 'magenta, as an app' at the top of the front page and the Moods), then deploy maybelleNo migration. Adds segno to requirements.txt: the image is rebuilt with it. 21:10Z: the banner on the front page only, pushing the page down (Justin, 21:06Z).
- ☑
- ☑
- ☑Merge magenta#132 (a woken agent is told which other agents were asked too, and whether they're at work), then deploy hunterNo migration. The poller only: hunter.
- ☑Merge magenta#133 (an agent sets agents' settings in a Mood when a person asks: a ```settings block, the settings_may_set grant -- magent at first -- one ledger, a line above the first turn on new settings), then deploy maybelle AND hunterNo migration. The grant is the global setting settings_may_set, changed with an SSH key on the settings API (POST /api/settings/ {key, value}).
- ☑
- ☑
- ☑Merge magenta#137 (an agent waiting shows so: 'magent is waiting for re to answer', not only its quiet dot), then deploy maybelleNo migration; the server and page only.
- ☑
- ☑Waiting: an agent can choose to wait for another asked the same thing, as a state shown in the Mood, ending in the other's answer or a quiet spell; mutual waits broken by who was named first; then who's waiting, shownThe third of three (Justin and re, 24 Oct). re's invariants: a wait is never a mention or a post that wakes; it always ends in an answer. Built in magenta#135.
- ☑Merge magenta#135 (an agent can wait for another asked the same thing: <wait for="re"/>, held and shown, ending in their answer, 5 minutes, or first-named on a mutual wait), after #134, then deploy hunter AND maybelleNo migration. Carries #134's commits: merge #134 first.
- ☑
- ☑Merge magenta#124 (a front-page tiding opens its discussion at once, not the Moods first; signed out, 'sign in with PickiPedia' and back to the discussion, in place of a box that does nothing; [[ suggests PickiPedia titles in a discussion's box), then deploy maybelleNo migration. [[ already suggested titles in a Mood's composer; this brings it to Tidings.
- ☑Show who's listening by voice: 🎧 beside their name where people are shown (who's here, the Moods list), for this Mood or every MoodJustin said yes, 22:16Z (not too noisy; and the switcher to say who's listening). Built into magenta#119: 🎧 on names in the Moods list; 🧭 says who else is listening.
- ☑Switch Moods by voice: 🧭, one tap, hears only "go to <Mood>" (matched against the Moods' names, said back before switching), never postsJustin said yes, 22:01Z, as a tap rather than press-and-hold. Built into magenta#119.
- ☑Merge magenta#118 (reading by ear: a chime before each message, another when all's read; ⏩ reads on one tap), then deploy maybelleNo migration. Then try ⏩ on the phone: one tap should chime and start reading. If one ever does nothing, say when, and magent compares it with the phone's heard rows.
- ☑
- ☑Merge magenta#114 (the front page: the mark, slogans from Magenta:Slogans taking turns, top 3 tidings, who's been talking where; Tidings ranked by votes, talk and age on a half-day clock; pins for SSH keys; top · new), then maybelle-config#221 (Caddy stops sending / to #general), then deploy maybelleBoth before one deploy is fine: / may answer 404 for the minute the container rebuilds after Caddy reloads. No migration.
- ☑Merge magenta#112 (editing and deleting what's said about a link, by the Mood's rules, sealed first), then deploy maybelle (migration 0036)23 Oct 04:45Z: main merged in (one conflict, pins beside edit rights); 1,109 tests pass; mergeable again.
- ☑An agent woken from a link's discussion answers into it: the wake prompt asks it to begin with ↩ #m-<id> (option 1, 21 Oct 10:22Z)On Justin's yes. re's pointer: poller/mood_poller.py ~1012, where the wake text already knows the replied-to id. 23 Oct: built in magenta#126 the sturdier way -- the runner says what woke a turn and magenta puts the answer under it, no instruction for the agent to forget; and asked in a Tidings comment, too.
- ☑
- ☑Save Cryptograss:Agents/GeneralOrders and Cryptograss:Agents/Blu/Rules as yourself (a small edit), so blu's rules count: only revisions by JMyles or SkymanJenkins doUntil then blu gets the recovery rules and says its own are missing. Both pages' last edits are Magent's.
- ☑Merge magenta#107 and maybelle-config#211 (blu's rules as each turn's system prompt), then deploy hunterEither order is safe: without #107, blu's poller refuses --rules-bundle and stays asleep. After the deploy, magent wakes blu.
- ☑Wake blu, once #107 and mc#211 are deployed on hunter21 Oct: blu's poller has run since 06:44Z, but waking it then would have given it no rules at all.
- ☑Merge magenta#79 (messages still sending stay last, in the order sent: no jump), and deploy maybelleJustin, 14:50Z on 20 Oct. Checked in a browser: ~A ~B → A ~B → A B. 947 tests OK.
- ☑Merge magenta#80 (thinking alone makes no turn: a quiet wake stays a dot in its row), and deploy maybelleJustin, 14:51Z on 20 Oct. #76, #78, #79 and #80 merge together cleanly in any order: 968 tests OK; one maybelle deploy for all four.
- ☑Deploy hunter: the status page's uptime for hunter comes from the faces service's /health, which reports it only from magenta#51 on (faces runs on hunter, last deployed 18 Oct)Nothing else hunter runs (poller, watcher, MCP, agents/) has changed since the fold; magenta.sh is for laptops.
- ☑Merge magenta#74 (each message in an agent's turn keeps its time and link, so its address can be copied), and deploy maybelleFrom 21:20Z on 19 Oct (the reply to #m-97769e4a). Merges cleanly beside #72 and #73.
- ☑Merge magenta#72 (a voice memo says how it's going until it's in the thread; menu as Sounds and Notifications; a notification once, dated when said, urgent for mentions, opening its own Mood), and deploy maybelleFrom your voice memo at 19:32Z on 19 Oct. 924 tests OK. After deploying, open magenta once on the phone so it subscribes again and its leftover subscriptions go.
- ☑Merge magenta#73 (reading aloud goes on after a message's own ▶, which used to stop it for good; ⏩ beside each ▶ reads from that message on, in this Mood or every Mood), and deploy maybelleFrom your voice memo at 19:41Z on 19 Oct, on the bike. Merges cleanly beside #72. 923 tests OK.
- ☑Decide: read aloud with the phone locked, by keeping a quiet audio session open while reading aloud is on (lock-screen controls; costs battery)?Nothing to decide: magenta already does this (a silent track while reading aloud, with lock-screen controls). What made it look missing was the stall magenta#73 fixes.
- ☑Merge magenta#68 (magenta.sh runs the Mood tools from its own checkout, downloading nothing), then git pull your own magenta checkoutSettling the fold: login, renew, attest, kick and unban fetched their scripts from jMyles/memory-lane, frozen at 145ef6e.
- ☑Merge pickipedia#149 (Recent Changes leaves out the Moods' to-do lists unless asked), and deploy PickiPedia74 of a day's 115 changes were to-do edits, most not bot-flagged. Tested in a throwaway MediaWiki 1.43.6: hidden by default, shown when asked.
- ☑Merge magenta#67 (the servers' faces in dark mode: each page's own dark portrait, image_dark)Redone 19 Oct with your dark versions (maybelle-config ascii-art/), not inversions. maybelle only.
- ☑Verify Cryptograss:Hunter, Cryptograss:Maybelle and Cryptograss:Delivery-kid: each infobox has image_dark, the dark-mode portrait (marked proposed)Hunter's and maybelle's from maybelle-config ascii-art/ (the portrait, without the banner's lettering); delivery-kid's its light portrait inverted, each character to its mirror on the ramp ' .:-=+*#%@'.
- ☑A dark version of delivery-kid's portrait, if you want one: it's the only server with just one (ascii-art/delivery-kid.txt); until then it sits on a light tile in dark modeJustin, 06:27Z on 19 Oct: just invert. Done: Cryptograss:Delivery-kid's image_dark.
- ☑Merge magenta#66 (read aloud: nothing read over a memo you're recording; the queue shown under the bar, now / next / then, each droppable; ⏭ says who it skips to)maybelle only. From the voice memo at 20:52Z on 18 Oct.
- ☑Decide: PickiPedia pages list the Mood messages that link them, from a ledger on the wiki (Cryptograss:Moods/<mood>/links/<month>, written by DrivingThatTrain, shown at the foot of every page by PickiPediaContent) or fetched live from magenta?Decided 06:36Z on 19 Oct: the ledger.
- ☑Build the backlinks ledger: magenta notes the PickiPedia links in Mood messages; DrivingThatTrain writes them to Cryptograss:Moods/<mood>/links/<month>; PickiPediaContent lists them at the foot of each page linkedBuilt: magenta#69 and pickipedia#150. DrivingThatTrain's edits are flagged a bot's, so Recent Changes leaves the ledgers out by default.
- ☑At Special:BotPasswords, signed in as DrivingThatTrain, add Create, edit, and move pages to the magenta-todo bot password (it has Edit existing pages and High-volume)Justin, 17:12Z on 19 Oct: DrivingThatTrain has it already.
- ☑Merge pickipedia#150 (each page lists the magenta messages that link it, Linked from magenta: when reading, editing, in its history, and on a red link's edit form), and deploy PickiPediaTested in a throwaway MediaWiki 1.43.6 serving real pages. Before or with magenta#69: until it's in, the ledger pages show their YAML as text.
- ☑Merge magenta#70 (👀 or 🔨 beside each agent turn, and on an agent's @mention of another: look only or full tools), and deploy maybellememory-lane#172 built this on 13 Oct but merged into #170's branch, so it never reached main. Now per turn, not per session. Merges cleanly beside #69, in either order. 911 tests OK.
- ☑Merge magenta#69 (the Moods' links written to PickiPedia, a ledger for each Mood and month), and deploy maybelle16 pages to begin with: 241 links from 176 messages. A message reaches the wiki within a minute (no hour's wait, 17:12Z). 916 tests OK.
- ☑Decide: an agent's journal at Agent:<Name>/Journal, an entry each time it awakens (new session, after a compaction): which rules it woke with (shared, its own, the Mood's, each at its version), its first answer, and the compaction's summary. Mood sessions only?Decided 06:36Z on 19 Oct: at Agent:<Name>/Journal/<blockheight>, one page an entry.
- ☑Build agents' journals at Agent:<Name>/Journal/<blockheight>: an entry each awakening in a Mood (new session, compaction, lost session), with the rules it woke with at their versions, its first answer, and a compaction's summary and tokensMoved to magent-self with the rules and namespacing (Justin, 19:20Z on 19 Oct): Cryptograss:Moods/magent-self/todo.
- ☑Merge magenta#50 (memory-lane under memory-lane/, with its history; magent's instructions to agents/magent.md), then maybelle-config#206 (hunter and maybelle build memory-lane from magenta)The freeze: no merges to cryptograss/memory-lane after 145ef6e (#221). magenta#50 first: hunter's image fetches memory-lane/requirements.txt from magenta. maybelle-config#206: https://github.com/cryptograss/maybelle-config/pull/206
- ☑Merge magenta#51 (re's status page, /moods/status/; Recent changes and Open work gone from the lower left), and maybelle-config#207 (its sources: the backups mounted read-only, MAGENTA_COMMIT, delivery-kid's uptime); deploy maybelle and delivery-kidre built it (18:30Z); magent opened both for it (re has no GitHub account) and fixed on top: last seen and backups for an SSH-key sign-in only, last seen right on Postgres, pickipedia-mcp compared with upstream's release commit (live: 29 ahead, 0 behind; upstream 17 on since). maybelle-config#207: https://github.com/cryptograss/maybelle-config/pull/207
- ☑Decide whether re gets a GitHub account of its own (it built the status page and had to hand it over as a patch)Decided 23:02Z on 19 Oct: no, for now. Other agents run their changes through magent, who opens the PRs, keeping them as the commits' authors.
- ☑Deploy maybelle, then hunter, once magenta#50 and maybelle-config#206 are inChecked 20:00Z on 18 Oct: all six people's and Moods' containers mount /opt/magenta/magenta-source/memory-lane/poller; watcher and faces run once each, project memory-lane-source, from magenta-source/memory-lane; faces /health 200; this Mood's wake worked; the rules page shows agents/magent.md; ~/CLAUDE.md is gone, so magent reads its instructions once.
- ☑After the fold deploys: re-open memory-lane#201 in magenta (and #165, #74 if wanted), move memory-lane's 13 open issues to magentaThe 13 issues are magenta#52 to #64. #201 is magenta#65. #165 and #74 wait on the decision item for them.
- ☑Archive cryptograss/memory-lane (Settings → Archive), once the fold deploys and its PRs and issues have movedReady but for memory-lane#165 and #74 (the decision item): archived, they can still be read and re-opened in magenta from their branches. Archived by Justin, 19 Oct.
- ☑Merge memory-lane#215 (/compact for re: Pi's RPC compact, forked like a turn; the server lets /compact through for Pi agents)Tried against the real Pi 1.1.0 on hunter up to the summarizer (magent's container has no provider key); a compaction that succeeds is first seen with the first /compact re after deploy. Deploy maybelle and hunter.
- ☑Merge memory-lane#216 (re's turn heads count every call, with what Pi says each cost: DeepSeek has no list price here)Has a migration (0030). Deploy maybelle and hunter. Turns already recorded keep what they had.
- ☑Merge memory-lane#217 (a turn: its head, its thinking and steps folded into one line, its answer open in its colour)maybelle only. Merges beside #215 and #216 (different lines).
- ☑Merge memory-lane#218 (an agent's @mention of another agent wakes it at once, not after the 10 minutes' grace)Why re didn't wake on magent's @re at 15:47Z: it was waiting for a session of its own that would never answer. hunter only.
- ☑Merge memory-lane#219 (switching Moods, the agents' settings row is drawn at once: no jump at the bottom)maybelle only. Measured: the row 0 px on opening a Mood on main, 25 px at once here.
- ☑Merge memory-lane#220 (agents' settings: a header row, only vendors with a key, chatty / moderate / reserved)maybelle only. Also fixes re's row sitting a column to the right (its context pie took a cell).
- ☑
- ☑Redeploy maybelle, then hunter, once #215 to #220 are inJustin, 17:01Z on 18 Oct: all merged and redeployed.
- ☑On maybelle:
rm /var/jenkins_home/.pickipedia-deploy-paused, so the staged PickiPedia build (#145, #146, #147) goes out; thentail -5 /var/log/pickipedia-deploy.logWhy the wiki stopped updating: the deploy cron does nothing while that file exists, probably since the Oct 10 database-password steps. Removed by Justin overnight; checked 18:09Z on 18 Oct: the wiki serves 3ffd310 (production's head) and the Agent: namespace (3010) exists. - ☑
- ☑Review and merge pickipedia-mcp#30 (onto upstream v0.19.0, keeping only our bot-edit marking, which now names whoever is signed in); then pull, npm ci, build and restart the stdio server in justin-arthelCI, 04:5xZ: preflight passes since e1c6c90 (the bundle file name). The tool-surface diff stays red for this PR only: upstream v0.19 removed set-wiki and remove-wiki, which nothing of ours calls; explained on the PR. Review guide on the PR: just our 12 files against upstream v0.19.0, and the marking port as one clean commit. Decided 2026-10-18 04:22 (rebase). Tested: the full suite (2417), and the wiki's own verification gate accepting the pages the built tool produces for eight kinds of edit (a control of unmarked prose refused). Supersedes #28 and #29 (closed). Running it for every agent (re, and magent's Mood containers, now on npx upstream@latest) is a maybelle-config PR after this merges.
- ☑Merge pickipedia#147 (an Agent: namespace: everyone reads it; each agent edits only its own pages, sysops any), deploy the wiki; at Special:UserRights add Magent and Re to the new agent group; at Special:BotPasswords, as each account, add the agent-edit grant; then merge pickipedia-mcp#30, which carries the Agent: exemption (see the item above)Where the notes go (Justin, 2026-10-18 03:29-03:37: on the wiki, everything public). Protected to write, not to read: an agent reads its notes as its own memory. Also where re's bot-facing docs can live, instead of protecting pages one at a time. pickipedia-mcp: https://github.com/cryptograss/pickipedia-mcp/pull/28
- ☑After the PickiPedia build: at Special:UserRights, add Magent and Re to the agent group; add the agent-edit grant to each one's bot passwordpickipedia#147 merged 05:36Z; not live until the Jenkins build (the item below). Magent's groups today: bot, user, autoconfirmed.
- ☑Say when memory-lane merges can freeze, for merging memory-lane into magenta (under memory-lane/, history kept)Asked 18:08Z on 18 Oct; magent said yes and opened magenta#50 and maybelle-config#206. The freeze is from 145ef6e (#221). Agreed 2026-10-18 03:24-03:26. The freeze runs from the copy until maybelle and hunter deploy from magenta; a memory-lane merge in that window would be lost. memory-lane#201, #203 and #204 (magenta-interface) are easiest merged or held first.
- ☑Review the rules files: AGENTS.md (what every agent keeps), agents/README.md (where each layer lives), agents/SUMMONING.md (how an agent is summoned today)re is checking SUMMONING.md against the code first (handed over in docs-tests-qa, 2026-10-17); magent folds its findings in. Nothing reads AGENTS.md until the next maybelle-config PR wires it in.
- ☑Merge memory-lane#210 (who's in a picture: 👤 Who's in it? in the lightbox; whose a face looks like offered with a ?, named only when a person says ✓ or types who; names go to PickiPedia as {{Depicts}})Has a migration (0029). Tried in a browser against a local faces with three references from the wiki: Justin and Cory offered right in the Skyler-justin-cory photo, Skyler asked Who?
- ☑
- ☑Redeploy maybelle and hunter, once memory-lane#209 to #214 and maybelle-config#203 and #204 are inChecked 05:5xZ: maybelle serves faces (Who's in it?, the key works: can_look true), the settings table, markdown, every agent at work, and the rules page; hunter's poller restarted 05:53Z with wiki_rules.py.
- ☑Merge maybelle-config#204 (backups at odd hours, so a 03:00 dump exists to keep as the day's and mirror offsite; cron-health now watches the daily and offsite copies)Deploy maybelle after. The two new cron-health stages stay red until a daily copy exists and an offsite sync sends something.
- ☑Tonight, by hand on maybelle (optional, a minute): keep today's dump as a daily copy and send it offsite, so there's one off the volume before the deploy's first 03:0005:25Z: magenta_memory_26216596.dump (396M, from 04:01) sent offsite, total size 414,693,251: the first copy off maybelle's volume since December.
- ☑Merge memory-lane#214 (the dials' texts from PickiPedia, Cryptograss:Moods/Dials, as the newest trusted editor's revision has them; the standing-rules half taken out, as magenta#49 gives agent rules their own route)Redeploy hunter (the poller) and maybelle (the rules page) after.
- ☑Verify Cryptograss:Moods/Dials (edit it, or take off the proposed mark): until a trusted editor's revision is there, the runner keeps the code's textsWord for word as poller/mood_poller.py has them. Also Template:Sent to agents and Cryptograss:Agents/Magent/rules (none yet; add yours).
- ☑
- ☑Merge memory-lane#212 (_underscores_ make italics and ~~tildes~~ strike, never inside a word; what you send shows formatted at once; every agent message in its colour down the margin)maybelle only. Bold, *italic*, code, lists and links already worked.
- ☑Check memory-lane's backups on maybelle:
ls -la /mnt/persist/magenta/backups/daily/andtail /var/log/nfs-backup.log04:59Z: daily/ empty since the folder was made (Feb 12), every offsite sync total size 0: no copy older than 24 hours, none off maybelle's volume, since December 2025. The cron runs at even hours, and the daily copy only at hour 03, so daily/ may be empty, and the 04:00 rsync --delete may have emptied the offsite copy too. re is opening the fix (cron at odd hours). - ☑Merge memory-lane#211 (every agent at work in a Mood shows, each on its own line in its colour: two woken by one post, or one asked and one looking in)Why the page said magent was thinking when you woke re (03:09Z on 18 Oct). maybelle only.
- ☑
- ☑Name faces in Mood photos: magenta asks the faces service, and offers the names it finds for a person to confirmBuilt: memory-lane#210, with Template:Depicts and Property:Depicts on the wiki.
- ☑Merge memory-lane#208 (commands for agents in one form,
/compact <agent>[,<agent>…] <what to keep>, anything else refused; every slash command offered as you type)Replaces #207 (closed). Deploy maybelle before or with hunter: the poller hunter has now runs the new form fine; a new poller before maybelle would miss commands. - ☑Merge memory-lane#206 (faces: whose faces are in a picture, from reference photos on PickiPedia)No deploy of its own: hunter builds it from memory-lane main once maybelle-config#202 is in.
- ☑Make the faces key:
openssl rand -hex 32, vaulted asfaces_api_keyNeeded before the hunter deploy: the role stops without it, and never makes one up. - ☑
- ☑Redeploy hunter, once #206, #208, maybelle-config#202 and the key are inhunter 00:44Z on 18 Oct. faces answers at https://faces.hunter.cryptograss.live/health, refuses /match without the key, and found both faces in a test photo with it.
- ☑
- ☑
- ☑Redeploy maybelle, once #203, #204 and #208 are inmaybelle 23:14Z on 17 Oct; checked in the page magenta serves: the tray, the lightbox (Back closes it, desktop and phone), the slash commands.
- ☑
- ☑Redeploy maybelle, once #202 is inLive by 01:53Z on 17 Oct (checked in the page magenta serves); Justin's photo went up after it.
- ☑Merge memory-lane#199 (the word-search test runs only on Postgres; a real Postgres run is issue #198)Tests only: no deploy needed.
- ☑
- ☑Redeploy maybelle, once #197 and #200 are inmaybelle 00:45Z on 17 Oct; checked in the page magenta serves: the strip, agent colours, the share target.
- ☑
- ☑Redeploy maybelle, once #196 is in (an installed app may keep the old icon until it re-reads its manifest; on iOS, add it to the home screen again)maybelle 06:51Z; the logo, the mark and the badge are served.
- ☑
- ☑Redeploy maybelle, once #195 is inmaybelle 05:57Z on 16 Oct; checked in the page magenta serves.
- ☑Decide: rename re to redd? (what it touches is in the Mood, 2026-10-16 00:3x)Decided 06:53Z: no, it stays re.
- ☑
- ☑Redeploy maybelle, once #190 is inmaybelle 05:57Z on 16 Oct; checked in the page magenta serves.
- ☑
- ☑Deploy PickiPedia (Jenkins pickipedia-build), once pickipedia#147 is in: one build carries #145, #146 and #147Live at 18:09Z on 18 Oct: the footer says 3ffd310 (with #145, #146, #147), once the deploy pause was lifted.
- ☑
- ☑Redeploy maybelle, once #185 is inmaybelle 05:57Z on 16 Oct; checked in the page magenta serves.
- ☑
- ☑Redeploy maybelle, once #184 is inmaybelle 05:57Z on 16 Oct; checked in the page magenta serves.
- ☑
- ☑Deploy PickiPedia, for maybelle-config#186 and #188 (its login hook)PickiPedia 06:15Z, on a maybelle-config with #186 to #188.
- ☑Merge memory-lane#181 (a run's end by when things happened: no "thinking" after a /compact; "compacting" while it runs)Merges cleanly with #179 and #180.
- ☑Merge memory-lane#180 (a background task's notice isn't filed as yours: the 02:09 stuck "thinking")Has a migration (0023). Merges cleanly with #179.
- ☑
- ☑Redeploy maybelle, once #179, #180 and #181 are inmaybelle 05:57Z on 16 Oct; checked in the page magenta serves.
- ☑
- ☑Redeploy maybelle and hunter, once #178 is in (hunter last: it restarts the poller)maybelle 01:45Z, hunter 01:51Z; effort shows on streamed turns.
- ☑
- ☑Deploy delivery-kid and PickiPedia, once #187 is in (their login hook; maybelle and hunter have it)Folded into the #188 deploy.
- ☑
- ☑Redeploy maybelle, once #177 is inDone with the 01:45Z maybelle deploy.
- ☑
- ☑
- ☑Merge memory-lane#172 (👀 look-only or 🛠️ full tools beside the agent's name), after #170Stacked on #170; GitHub retargets it to main once #170 is in.
- ☑
- ☑Make the SSH announcing key:
openssl rand -hex 32, vaulted asmemory_lane_access_keyIt can announce an SSH session and nothing else. Without it, #173 and maybelle-config#186 do nothing. - ☑Merge memory-lane#173 and maybelle-config#186 (who comes in by SSH, on every box, and as which account: root marked)#173 is in; maybelle-config#186 is still open, and needed for the boxes to say anything. maybelle's own deploy key isn't announced.
- ☑Merge memory-lane#175 (anything in a Mood can be replied to: a redeploy, a merge, a release, a wiki change)Merges cleanly with #173. maybelle for the page, hunter for agents reading the quote.
- ☑
- ☑Redeploy maybelle, once #170, #172, #173, #174, #175, #176 and maybelle-config#186 are inmaybelle 22:35Z (ea16a66); the page magenta serves has the new heading, ↩ on events, 👁 and the badges.
- ☑Redeploy hunter, once #171, #175 and maybelle-config#186 are in (the poller's screen and reply quotes; route-ssh and the login hook)hunter 01:51Z.
- ☑Deploy delivery-kid and PickiPedia, once maybelle-config#186 is in (their login hook)delivery-kid has it; PickiPedia folded into the item for #186 and #188.
- ☑Decide: quiet wakes cost $2–3.40 each, nothing cached (13 came to $31 in one session). Screen them with the cheap screen first, as posts are?Justin asked why they weren't already: built as memory-lane#171.
- ☑
- ☑Redeploy maybelle, once #162 and #167 are inLive by 17:12Z on 12 Oct (checked in the page magenta serves).
- ☑
- ☑Merge memory-lane#160 (a woken turn's tasks end when they do; a task opens to what it is)Merges cleanly with #157. The redeploy alone clears the helper still shown as running in #uploads-and-embeds.
- ☑Redeploy maybelle, once #157 and #160 are inLive by 00:20Z (checked in the page magenta serves).
- ☑Redeploy hunter, once #160 is in (the poller passes task notices on)Not yet at 21:00Z on 13 Oct: hunter's poller is still the one started 9 Oct, 20:40Z. One hunter redeploy covers this and #171.
- ☑
- ☑Redeploy maybelle, once #155 is inLive by 20:10Z (checked in the page magenta serves).
- ☑Merge memory-lane#154 (Yarn clips' picture kept here too: no more bare 'Yarn clip' cards)Has a migration (0022).
- ☑Redeploy maybelle, once #154 is inmaybelle 15:14Z; johnny's picture is kept (15:15Z).
- ☑Merge memory-lane#152 (Yarn clips kept here: fetched once by the server, played from magenta; includes #151)Yarn's Cloudflare stops browsers with a human check; the server fetches each clip once instead. Has a migration (0021).
- ☑Redeploy maybelle, once #152 is inmaybelle 15:02Z; the server got past Yarn's Cloudflare and kept both clips.
- ☑
- ☑
- ☑Merge memory-lane#149 (a fixed player isn't kept broken in the browser's copy; delivery-kid's mark comes and goes like the controls)Why Water Tower still wouldn't play for you: your browser's kept copy of the thread had the old player.
- ☑
- ☑Redeploy maybelle, once #147, #148, #149 and #150 are inmaybelle 04:10Z
- ☑
- ☑Deploy PickiPedia, once pickipedia#138 is inThe 04:11Z deploy built 052be02 (#137), just before #138 merged; a later deploy built 8e2aee3, which has it.
- ☑Merge memory-lane#145 (Release videos play: delivery-kid's HLS streams through hls.js, the plain file as fallback)Kenny's Water Tower video, and 26 of the first 40 video Releases, are HLS folders magenta couldn't play.
- ☑
- ☑Redeploy maybelle, once #145 and #146 are inmaybelle 20:44Z
- ☑
- ☑Deploy PickiPedia, once pickipedia#137 is inPickiPedia 20:39Z
- ☑
- ☑Redeploy hunter, once #144 is in (the poller runs there)hunter 20:41Z
- ☑
- ☑Deploy delivery-kid, once #175 is in (not while a video is finalizing)delivery-kid 20:33Z
- ☑
- ☑Redeploy maybelle and hunter, once #142, #143 and maybelle-config#174 are inmaybelle 18:39Z, hunter 19:01Z.
- ☑
- ☑Merge maybelle-config#174 (clone memory-lane and magenta from cryptograss)Both have moved, so it's ready.
- ☑Transfer jMyles/memory-lane to cryptograss (Settings → Danger Zone → Transfer)18:27Z. magent-cryptograss kept write access; the org's hook hears it (an edit to #142 arrived at 18:28Z).
- ☑Let magent-cryptograss create repositories in cryptograss, and say go: magent transfers magent-cryptograss/magentaInvited; magent joined and moved magenta at 18:28Z. The old URL redirects, so every container's clone keeps working.
- ☑
- ☑Redeploy maybelle, once #141 is in
- ☑Look at the webhook's Recent Deliveries on GitHub: its URL, and what they answeredFound 18:19Z: the hook is the cryptograss org's (a star there reached magenta, signed and accepted), and memory-lane and magenta weren't the org's repositories. Hence the move.
- ☑Merge memory-lane#140 (the bot's ticks for a page go in one edit, and it checks they stayed)Three ticks in one second lost #139's; this is why.
- ☑Redeploy maybelle, once #140 is in
- ☑Merge memory-lane#139 (→ PickiPedia in the lightbox too)Merges cleanly with #138.
- ☑
- ☑
- ☑
- ☑Redeploy maybelle, once #138, #139 and maybelle-config#173 are in
- ☑Redeploy maybelle, for #135 to #137
- ☑
- ☑
- ☑
- ☑Look at your devices → everyone: was Sky's 12:54 device signed out, and when?Answered 10:26Z: none of Sky's were signed out, so that browser lost its sign-in (or it was the other one: home-screen app vs browser).
- ☑
- ☑Deploy PickiPedia again, once #172 is in (for pickipedia#136: code and anchors on the wiki's list)
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Make the webhook secret (
openssl rand -hex 32); vault it asmemory_lane_github_webhook_secret - ☑Redeploy maybelle, once #131, #132 and maybelle-config#171 are in
- ☑Add the webhook on GitHub: pull requests, to
https://magenta.cryptograss.live/api/github/hook/ - ☑Deploy PickiPedia, for the todo tag (pickipedia#134)
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Make the recovery key pair; keep the private half offline; public half in the vault
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Propose and approve the "magenta uploads" OAuth 2 app; put its keys in the vault
- ☑Tick High-volume (bot) access on the DrivingThatTrain@deploy-logs bot password
- ☑Redeploy maybelle, once the merges are in18:07Z, by JMyles (Cryptograss:Maybelle/deploy logs/26149367).
- ☑Redeploy hunter (the poller's greeting wording, #105; the to-do line in every wake, #117; handoffs in wakes, #118)
- ☑Look at and merge pickipedia#155: a 'Verify all claims' button on the page you're looking at; then the wiki's deployMerged 25 Oct 00:05Z, but into main; the wiki deploys from production, so it never went live. Again as pickipedia#157.
- ☑Say yes, or what to change, to the check-in design for waiting (poller extends a wait itself while the awaited agent is at work; wakes the waiter only when something changed; follows a hand-on; capped)Yes, without the cap (13:49Z). Built as #144.