Adopt the governance profile in the organization configuration repository #2685

Problem

The accepted Base governance design and implementation plan identify package 12/.github as a required deliverable. This issue translates that package into a reviewed, bounded issue/PR train; it does not authorize implementation before the issue reaches Ready.

Expected behavior

Inventory and apply only the governance requirements applicable to basefoundry/.github, the organization-configuration repository. GitHub Issues are disabled there, so this Base-repository tracking issue owns the work and its PR must link back to this tracker using the full issue URL. Do not enable repository Issues as a side effect. Treat this repository as a special organization-config profile; do not require a Base manifest or consumer governance/ folder unless a separately reviewed decision justifies it.

Scope and non-goals

Scope: Inventory and apply only the governance requirements applicable to basefoundry/.github, the organization-configuration repository. GitHub Issues are disabled there, so this Base-repository tracking issue owns the work and its PR must link back to this tracker using the full issue URL. Do not enable repository Issues as a side effect. Treat this repository as a special organization-config profile; do not require a Base manifest or consumer governance/ folder unless a separately reviewed decision justifies it.

Non-goals: Do not silently expand scope, activate unreviewed policy, mirror issue fields onto PRs, grant agents merge/release authority, or make changes outside the named affected areas. Any new product decision or materially new work gets a separate issue and decision record.

Affected areas

• basefoundry/.github repository's issue/PR templates, organization profile and workflow settings.
• Accepted source: governance design and implementation plan, PR #2664
• Parent tracker: #2665

Impact and evidence

1. Product intent: Implements only the accepted governance design and plan; any product-requirement change must be filed separately.
2. Architecture and contracts: Destination is the package-specific section of the merged governance design/implementation plan plus the affected canonical contract named above.
3. User guidance: The issue identifies likely guidance paths; the implementation PR must name updated user/FAQ/README paths or give a change-specific reason why none is affected.
4. CLI/API and reference: The affected-area list determines whether CLI/API/reference docs change; the implementation PR must cite the exact reference path or justify no impact.
5. Operations and safety: No privileged automation or merge authority is implied; the PR must list operational/security effects and any rollback.
6. Validation and testing: The issue lists the planned tests; the PR must report executed validation and explain any unavailable test.
7. Examples and downstream use: The implementation PR must identify affected examples/consumers or give evidence that this change has no downstream surface.
8. Governance and contributor process: This package changes or preserves the contributor/governance contract as described in Scope; links must point to the canonical rules.
9. Decision records: No new decision is accepted by this issue; any durable deviation requires a proposed decision record and explicit maintainer acceptance.
10. Release notes: The PR must include a user-facing release-note line or a reasoned none; this issue does not pre-decide that disposition.

These are issue-stage dispositions to refine during Triage. Before Ready, every category must have its exact destination or evidence-based no-impact reason; the PR repeats the ten-category evidence for actual changes.

Open questions

• None known. If implementation exposes an unresolved contract, return this issue to Triage and record the decision before implementation continues.

Plan

• S1: One focused PR for this issue. Use Fixes #N only if no additional slice is needed; if the maintainer approves multiple PRs, name each S1…Sn here before the first is opened and use Part of #N.
• Dependencies: the P2 issue, the P5a issue, the P8a issue, the P9 issue, the P16a issue, the P17 issue, the P19 issue, the P20 issue
• Acceptance criteria:
• The current .github repository contents, default templates, workflows, branch rules and issue-disabled setting are inventoried.
• Applicable org-level templates/policy are aligned with the accepted issue/PR contracts and do not contradict repo-specific configurations.
• Any non-applicable manifest/Project requirements have an evidence-backed no-impact disposition.
• The PR links to this Base issue, and issue-disabled state remains unchanged unless a separate explicit maintainer decision is recorded.
• All title and template changes have a rollback path and no org-wide policy is activated implicitly.
• Validation:
• Validate templates/workflows in the target repository and test fixture rendering/contract checks.
• Read back issue-disabled and branch policy settings.
• Compare effective org templates against representative repositories.
• Risks and rollback: Org defaults can affect every repository; stage with a preview inventory, keep repo-specific exceptions explicit and revert the PR if any consumer contract breaks.
• Decision impact: No decision is accepted merely by implementing the issue. Record the relevant accepted decision/ADR and file a superseding record if the maintainer approves a change.