docs: separate documentation trust from agent execution

[dapi]

DNA now defines how readers establish a documentation claim’s owner, basis, scope and freshness. Agent reading order and conflict-handling actions belong to the existing flows/ layer.

• Distinguish requirements, observations, inferences and assumptions; active describes publication status and does not establish a claim’s truth.
• Make conflicting ownership, stale evidence and affected downstream claims explicit.
• Move governance priming and agent conflict handling to their process owners; synchronize navigation, glossary and both root READMEs.
• Preserve existing document paths, frontmatter enums and YAML forms. Record the boundary decision in project-local FT-DNA and ADR-002.
• Register the project-local R-DNA-EVAL experiment passport and proposed protocol: paired old/new comparison, 12 scenarios, quality and cost metrics, launch prerequisites and follow-up validation. The benchmark has not been executed.

Validation: priming tests and 16 manifests, template and project-instance lint, template doctor, projection and whitespace checks all pass. Local downstream initialization and lint pass. Independent code-converge --document-review --max-cycles 0 review of 7774c39cc673cecf55af0da72039e5571f471eb1 returned a structured clean verdict with no findings, including the requested repeat review.

The R-DNA-EVAL passport and protocol in de01eb122ace51cdf00ea946494ac2a1ddd740c1 also passed independent document review with no findings. Project-instance lint, projection and frontmatter checks pass.

Review evidence is bound to each reviewed commit in refs/notes/dna-trust-review; candidate snapshots are retained under refs/review-candidates/ft-dna/. No runtime code or deployment configuration changes.