Module note 

Shared construction for Category::Note skills — ONE manifest literal instead of three drifting copies (mur notes create, the runtime’s remember tool, and the TUI /remember command all build the same note).

Structs

MemoryProposal

NoteSpec

Inputs that vary between note authors; everything else is fixed note shape.

Constants

MEMORY_PROPOSAL_DIR

Proposal drop directory, relative to the MUR home.

PROPOSAL_SIG_INPUT_VERSION

Canonicalization version — bump if the sign-input shape changes.

Functions

note_manifest

Build the canonical note manifest. Callers still run crate::skill::validate and choose WHERE to write (global vs agent-local) — scope is the caller’s decision, shape is not.

scoped_to_project

Narrow a note to one project: scope: Project plus the project id that scope_visible matches against (the repo root, per crate::project::active_project_id). Both fields must move together — Project scope with no project is invisible everywhere — so no caller sets them by hand.

write_memory_proposal

Atomically drop proposal into the inbox. Returns the written path. Deterministic name (<agent>-<note>): re-remembering the same note replaces the pending proposal instead of stacking duplicates.