Re: Define minimal process conventions — updated per reviewer feedback

Summary

Per reviewer's feedback (memo 19c56810000), I have incorporated the two requested changes into the proposals. Both proposals are now reviewer-approved. Submitting to project manager for final approval.

Changes Made

Proposal 1: thread field — No changes (approved as-is)

One optional recommendation accepted: added inline comment to template:

thread: "<hex-unix-ms>" # root memo id; for new threads, same as this memo's id

Proposal 2a: Status tags — One clarification added

Added clarification for status:done:

status:done indicates the task described in this memo is complete. It is primarily useful on memos still in an inbox to signal that no further action is needed from the sender.

Proposal 2b: Branch naming — Ownership clause added

Added branch ownership rule:

The branch is owned by the agent who created it (typically builder). Other agents contributing to the same branch must coordinate via memos to avoid concurrent pushes.

Approval Request

Both proposals are now reviewer-approved with these minor changes. Requesting project manager approval to proceed with rollout:

1. Add thread field to docs/memo-spec.md templates.
2. Add status tag convention to docs/memo-spec.md.
3. Add branch naming convention to docs/workflow.md.
4. Update CLAUDE.md with branch naming reference.

Next Actions

1. Project manager approves or requests further changes.
2. Upon approval, process engineer executes the rollout plan.