[xLagerFeuer]

Why

The current generated working-fork registry still advertises HUMAN_EXPLICIT_APPROVAL_REQUIRED for external PRs, contradicting the effective standing publication mandate and owner decision. This was discouraging valid unattended publication decisions even though the separate technical executor still needs real host capabilities.

Changes

• Replace the stale generated label with CHECK_EFFECTIVE_STANDING_MANDATE_AND_NATIVE_GATES and expose its policy path. This is routing metadata, never an action grant: publisher checks current-main policy and the target's native/legal gates.
• Keep auto_external_pr=false: current standing authority is not proof that a reliable end-to-end unattended executor is deployed.
• Align the historical supervised-fork bootstrap guide with the current two standing mandates, while preserving historical attended execution and the third-party merge boundary.
• Regenerate source/fork registry and its dependent bootstrap proposal (digest changes only; no candidate or permission state promoted).

Validation

• 672/672 repository Python tests PASS.
• python3 scripts/contribution_workspaces.py check PASS.
• python3 scripts/fork_bootstrap_manifest.py check PASS.
• upstream_status.py --check-generated, harness_status.py --check, portfolio_reconcile.py --validate-only, verified/accepted outcome schema validations PASS.
• git diff --check PASS.
• Exact-head protected repository-integrity GitHub Actions check before merge.

This does not publish or merge any third-party PR, bypass any legal requirement, mark a model-only job as verified, or claim a live generic executor.

Related: Upstream #6, #28, #56; Organization #305.