Specify reviewable session-closeout memory proposals #97

Design deliverable

Describe a session-end proposal with kind (new/update/duplicate/conflict), target canonical reference, base revision, source evidence, rationale, summary/detail, scope and visibility. Default to a few durable findings prepared by the active agent; no new background model service.

Worked example

A task discovers that Data Protection keys must survive deployment. Search existing knowledge first; show either a new gotcha or a diff against an existing revision, citing the task/deployment evidence. If the evidence contradicts a current decision, present a conflict instead of replacing it.

Acceptance

• Example payloads and review interactions for all four kinds.
• Explicit relation to existing author/store/moderator permissions and stale-revision handling.
• Secrets/transient logs excluded; scope/visibility never silently broadened.
• Distinguish suggested, saved and published states; specify success metrics.

Dependencies

Concept work can start now. Implementation remains outside this design task; later use #73/#75 references.