spool-memory 0.2.3

Local-first developer memory system — persistent, structured knowledge for AI coding tools
Documentation
# GUI Metadata Round 9 Plan

## Summary

Round 9 should close the remaining write-surface inconsistency by letting GUI users enter lifecycle metadata for new writes.

The work is sequenced in this order:

1. add optional metadata inputs to the GUI create/propose form
2. keep the form narrow and map directly to existing service contracts
3. verify GUI behavior and update handoff status

## Key Changes

### GUI write metadata

- add optional inputs for:
  - `actor`
  - `reason`
  - `evidence_refs`
- thread them into GUI manual/propose writes
- keep lifecycle action buttons metadata-free for now unless the UX stays simple

## Test Plan

- GUI unit tests for metadata form parsing and validation
- GUI flow tests that written records show metadata in detail/history after create/propose

## Assumptions

- Round 9 does not add batch actions
- Round 9 does not redesign the MCP or CLI surfaces
- Round 9 keeps metadata optional

## Completion Status

Last checked: `2026-04-12`

Completed in this round:

- added optional GUI inputs for:
  - `actor`
  - `reason`
  - `evidence_refs`
- GUI create/propose flow now threads metadata into lifecycle writes
- GUI metadata shows up in detail/history after GUI writes via the existing shared contracts
- verification completed with full test and check passes

Checked for omissions against this plan:

- no missed items inside the scoped implementation baseline
- batch actions remain intentionally deferred
- CLI and MCP surfaces remain unchanged
- metadata remains optional

## Completion Status

Last checked: `2026-04-12`

Completed in this round:

- added optional GUI inputs for:
  - `actor`
  - `reason`
  - `evidence_refs`
- GUI create/propose flow now threads metadata into lifecycle writes
- GUI metadata shows up in detail/history after GUI writes via the existing shared contracts
- verification completed with full test and check passes

Checked for omissions against this plan:

- no missed items inside the scoped implementation baseline
- batch actions remain intentionally deferred
- CLI and MCP surfaces remain unchanged
- metadata remains optional