feat(analysis): bind support-edge refusals to an analysis-run profile

[seonghobae]

Consolidation status

fold_into_landing_vehicle — support_edge_v1 / tepp.support_edge.v1 is a Validation / Analysis Run profile and changes the same shared integration surface as #416 (Cargo.lock, crates/analysis_engine/Cargo.toml, crates/analysis_engine/src/lib.rs, DOCUMENTATION.md, docs/TRACEABILITY.md, and docs/adr/README.md). It is therefore a Draft fold child of #416, not an independent protected-main landing authority.

Current exact child head: f71591864efc2beff336ced7ef35d5a013305c36. Current surviving #416 head: 0b7155cc238defb1e55129ff3000658f04b343cf. Retargeting is non-destructive; unique source/tests/doctoring remain on this branch until a real conflict-resolving fold verifies their inheritance.

Preserved profile evidence

• Profile/contract support_edge_v1; schema tepp.support_edge.v1.
• Inference status evidence_is_not_transition.
• Binds existing support_edge::EvidenceKind and refuse_evidence_as_transition on protected main.
• Mixed census keeps support, contradiction, summarizes, and outcome-of evidence distinct from a forward state transition after cutoff exclusion.
• Request cutoff equality is typed through KnowledgeCutoff::instant().
• AvailableTime <= knowledge_cutoff admission occurs before duplicate-identity checks.
• MAX_EVIDENCE_UNITS bounds execution admission and artifact validation.
• edge_kind_recovery_rate remains library-side; inspect payloads remain metric-free.
• Not GPU, not MCMC, not topic birth/split/merge, and not implemented-main.

ADR 0078 is implementation lineage pending repository-wide ADR normalization under #437; it does not create a new bounded context or branch-local architecture authority.

Merge authority

Only the eventual surviving #416/successor exact head counts after the fold. Reacquire all required current-head workflows, resolve current review threads, and satisfy live ruleset 18156473, which currently requires one qualifying current-head approval and dismisses stale approvals after pushes. Bot COMMENTED/APPROVE evidence is not treated as independent human approval. No self-approval, force push, destructive rebase, routine admin bypass, or child-head evidence transfer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}