Reconcile and confirm an elicitation evidence plan

Edit elicitation-plan.json. activities has distinct id, kind, start, duration and people. capture also needs source and method from the supplied packet contract. review instead needs findings: [{id,revision}]. A review takes one slot per finding, even when bundled. mean needs team-lead; routes needs coordinator or both day-lead and duty-lead; policy needs policy-owner. No review may precede the end of any accepted or excluded evidence capture. A reviewer confirms only a complete accurate current revision; this simulated confirmation is not requirement approval. findings has one record for mean, routes and policy: id, positive revision, evidence (fact IDs), exclusions ([{fact,reason}]) and value. Partition every captured fact for that need exactly once between evidence and justified exclusions. duplicate requires an accepted copy of the same key, date, revision and data; outside-window requires an out-of-window date; superseded requires a lower policy revision than the current effective rule. Never count a copied batch twice. mean must cover morning and evening in inclusive dates 95..100 and report the pooled observation mean as {numerator,denominator}; sum wait totals and sample counts rather than averaging batch means equally. routes must cover day and duty in dates 95..100 and report summed category counts as {supervisor:count,duty-manager:count}. policy must cover exception and report its integer limit, using the highest rule revision effective by date 100; older conflicting rules remain traceable exclusions when captured. Cite only acquired facts. Each review references the finding's current revision; repairing a finding invalidates any earlier revision reference. Choose direct observation or records plus reconciliation, fit the actual calendars, and confirm all three results. Equivalent reduced fractions and harmless activity ordering are accepted.