[hhff]

Built on #107, which has the Keep-it loading state; the diff shrinks once #107 merges.

What

• dashboard/index.html: a lesson card has a one-line note box ("Add a note to refine it"). Keep it sends the note with the answer. The note survives redraws like other drafts.
• scripts/devteam.mjs:
  • knowledge set <k> --note "…" --owner: only the owner may add a note, as one line of at most 600 characters.
  • The dashboard's knowledge action passes the note.
  • knowledgeBlock renders … The owner adds: <note>, reading the note only from the owner's own log lines (ownerNote).
• schema/log.schema.json: knowledge.owner_note, which only the owner may set (x-authority.set.knowledge.owner).
• test/kit.test.mjs: a supervisor's --note is refused; a hand-written supervisor line carrying owner_note doesn't reach the prompt; the owner's note does.

Why

The owner wanted to keep a lesson but refine it slightly without rewriting the supervisor's statement.

Authority

The note goes into every agent prompt the lesson applies to, so it's the owner's alone: the CLI refuses anyone else, the schema allows only the owner to set the field, and prompts ignore any non-owner line carrying it.

Migration

None. Restart the dashboard after the sync.

🤖 Generated with Claude Code

[hhff]

Merging for v0.20.1 (upstream loop).

• Local release candidate (main with Tests never reach the machine's default tmux server #117, plus An owner's answer binds to the question as the owner saw it #116, Tickets in other repos: one fleet, one log and one graph across sibling repos #108, Lessons: keep one with an owner's note that refines it #114 and gate-change can be settled by the owner's own standing rule #115): Node 24.14.1 passed 122/123. The one failure is the hub test's "both instances listed with counts" timeout under load; it passed in the previous candidate's run and on CI.
• CI: 18/20/22/24 green on this head, with main merged in.
• Next: main's own CI checks the combined result before the tag.