Extract reusable PR consolidation methodology after Ontogenesis pass

[mdheller]

Context

The Ontogenesis 2026-05-14 consolidation pass established a repeatable pattern:

1. Inventory open PRs and issues from live repository state.
2. Identify supersession pairs and close superseded PRs with provenance comments.
3. Merge ready PRs in dependency order with exact-head protection.
4. Triage drafts with explicit per-PR promotion gates.
5. Document the consolidation pass in a durable repo artifact.
6. Open a release-readiness issue with validation and release criteria.
7. Run local validation.
8. If green, cut a release with consumer upgrade guidance.
9. If failing, use a pre-declared triage order and fix/revert discipline.

This pattern is now partially captured in docs/consolidation/2026-05-14-ontogenesis-gitops-consolidation.md and issue #92.

Problem

The methodology is useful beyond Ontogenesis. AgentPlane is the natural next consolidation target, and other SocioProphet repos will accumulate similar PR debt.

If the pattern remains implicit, future consolidations will re-invent it. If it is hoisted into a reusable methodology artifact, future passes can cite it and only record repo-specific decisions.

Decision needed

Choose where the reusable consolidation methodology should live:

1. Ontogenesis-local documentation only.
2. SocioProphet org-level methodology document in a governance/docs repo.
3. SocioSphere / workspace-controller methodology surface.
4. Superconscious / meta-program methodology surface, if that is the canonical place for reusable operating method.

Proposed reusable structure

A reusable consolidation methodology should include:

• live-state verification requirement
• supersession-pair audit protocol
• exact-head merge protocol
• conflict response protocol: replay clean rather than force-merge stale branches
• draft-gate comment template
• validation gate protocol
• issue-closure acceptance-criteria protocol
• release-readiness issue template
• consumer-upgrade note requirements
• post-merge failure triage rule
• release-tag decision rule

Acceptance criteria

• Decide canonical home for the reusable consolidation methodology.
• Create or link the reusable methodology document.
• Update the Ontogenesis consolidation addendum or a follow-up note to cite the reusable method.
• Apply the method to the next target repo, likely AgentPlane, rather than re-inventing the process.

Non-goals

• Do not block Ontogenesis v0.2.0 validation on this methodology extraction.
• Do not require all repos to use identical ontology-specific gates; the method should define the workflow skeleton and allow repo-specific validation gates.