[xLagerFeuer]

What changed

Qualify two source-native patches from historical open Upstream evidence drafts through a new, additive, exact-digest packet-selection manifest, without changing the frozen 2026-10-23 assessment batch.

• microsoft/fara@a675d6d: mismatched resumed task identity; new first-party fixture RED 1/3 → GREEN 3/3.
• kstawiski/evidence-gated-scientific-agent@85b396a: failed retrieval status incorrectly admitted as successful evidence; first-party policy fixture RED 1/16 → GREEN 16/16.
• Revalidated exact patch SHA-256s against unchanged current original default branches. A newly selected packet is accepted only when source/candidate identity, assessed review SHA, stored patch bytes/hash and dated native receipt match.
• Add fail-closed tests for duplicate selections and missing receipts; update current generated workspace registry, fork bootstrap proposal, and pilot catalog. Do not edit frozen screening manifests.

Validation

• python3 -m unittest discover -s tests: 674 PASS / 0 FAIL on rebased fa806c1 base.
• python3 scripts/contribution_workspaces.py check: PASS
• python3 scripts/fork_bootstrap_manifest.py check: PASS
• python3 scripts/pilot_catalog.py check: PASS
• python3 scripts/upstream_status.py --check-generated: PASS
• python3 scripts/harness_status.py --check: PASS
• python3 scripts/portfolio_reconcile.py --validate-only: PASS
• python3 scripts/verified_external_outcomes.py --validate-only: PASS
• git diff --check: PASS

Boundary

This is a technical admission/registry change, not source-fork staging, external PR creation, full first-party native CI, maintainer adoption or a VSM regrade. Follow-up is source-and-fork SHA/permissions/CI preflight and actual trusted one-use preparation under the separate active standing preparation policy. The other three sources of the five-source wave retain individual blockers.

Evidence and five-row disposition: reports/2026-11-12-native-packet-requalification-wave-01.md. Governing issues: #6 and #56.