Strategy: context assets via Git LFS above threshold

[pewpewpotato]

Problem

Unbounded binary assets in a “normal git” context repo break stock GitHub review/history. We need a clear LFS policy enforced on the write path.

Who it’s for

Agents writing assets via MCP; humans cloning/reviewing the context repo.

Normative baseline (gate G4)

• Git LFS above default threshold 512 KiB (configurable)
• Small/text assets stay as normal git blobs
• Text/JSON/TOML stay plain git; warn if above ~1 MiB
• No Spool-specific asset remote / blob store as SoT

Acceptance criteria

• Default threshold 512 KiB documented and configurable
• MCP/write path routes assets ≥ threshold through Git LFS
• Text/JSON/TOML remain plain git blobs; warn above ~1 MiB
• Docs explain LFS requirement for consumers of the context remote
• Policy does not reintroduce a Spool-specific asset remote

Non-goals

Custom Spool blob store as SoT for assets.

Depends on

#99 layout (assets/); #100 write path enforcement.

Owner

Spool Architect (policy) + Spool Engineer (enforcement)

[pewpewpotato]

PO AC alignment (amended baseline):

• Default LFS threshold 512 KiB (configurable)
• Text/JSON/TOML stay plain git blobs; warn above ~1 MiB
• MCP/write path enforces policy; docs explain LFS for context-repo consumers
• No Spool-specific asset remote