Event-loop turns run to completion, so I/O on shared, remote, or slow
state belongs between turns (async); synchronous access is fine only for
state local, prompt, and private to the actor, such as a Durable
Object's SQLite. Sourced from Miller, Tribble & Shapiro, "Concurrency
Among Strangers" (TGC 2005), §5.2 and §6 footnote 5.
Generated-by: Claude Opus 5.5
The description repeated the body's procedure (which file, the losing
diagnosis, the exact winning? replies). Keep only trigger phrases and
artifact names, and add two missed triggers: reading a recording
without the magic words, and how to set one up.
Drop the link to ../lab-notebook-template.md and the mention of a
`watchme` specimen capture; neither exists in this repo.
Generated-by: Claude Opus 5.5
Every failure path leaves a trace in the logs, and no failure is
invented without checking what the API actually returns. Prompted by
diigo-cache's password-manager save reporting "not saved" on success
(CredentialsContainer.store() resolves with undefined).
Generated-by: Claude Opus 5.5
Prune references to other kriscendobot/garden skills and roles
(fixer, weaver, judge's panel, boatman/ferry, journal entries,
references/endo-but-for-bots) and per-PR session lore. Replace the
garden's created/updated/author frontmatter with name + a
trigger-first description. Keep the two skills cross-linked, since
both now live here, and credit upstream with links pinned to the
source commits.
retcon: tag pre-retcon tip as a numbered step; verify with a single
empty `git diff pre-retcon HEAD`; drop `git -C project`.
yarn-lock-separate-commit: promote the rebase --skip recipe from
field notes to its own section.
Generated-by: Claude Opus 5.5
Front-load the description with trigger words (Generated-by trailer,
AI disclosure, commit message, PR description, Co-authored-by) and
add a when-not clause. Lead the body with a worked example; add
rules for mixed commits and PR descriptions.
Generated-by: Claude Opus 5.5
Code that works the first time may ship untested; a discovered goof
owes a regression test. Cites Dan Connolly's MadMode entry of
18 Mar 2006 on test-driven debugging.
Generated-by: Claude Opus 5.5