foottrace 1.3.0

Adds shared, reference-only requirement evidence on the foottrace root entry: RequirementResult, RequirementCheck, RequirementCheckDisposition, RequirementReason, and the bounded readRequirementResults() reader.

• Results bind a requirement to a finding, time window and affected claims, with evidence, attempt and host-owned action references. Source-valid and learned-time references stay separate.
• RequirementReason contains exactly 12 domain-evidence reasons from the single gap registry. Requirement and check reasons reject trace-walk limits such as cycle, node-limit and strategy-failed; cause gaps and admission errors retain their existing broader vocabulary.
• The reader returns detached, frozen records and uses fixed typed refusals for malformed or oversized inputs. Structural admission does not authenticate a producer, establish domain truth or authorize an action; claim enforcement remains a consumer responsibility.
• Existing public entry points and execution-record bytes remain compatible. The optional cause reader remains ESM-only; the new requirement reader supports both ESM and CommonJS.

Validated on Node 22 and 24, including packed type/browser consumers, independent security and code reviews, rejection regressions and unchanged flow-record fixtures. No model or storage service is built in.