Move project coordination and automation fully into GitHub

[rmcdaniel]

Objective

Make GitHub the only durable authority for Durable Workflow product work. Every contributor must be able to discover active work, propose changes, follow checks, and see completion without access to a separate coordinator or tracker.

Operating decisions

• GitHub issues own backlog, priority, decisions, and blockers.
• Pull requests own implementation discussion and review.
• GitHub Actions owns ordinary repository CI, package and image publication, Pages/status deployment, and scheduled maintenance.
• Release-critical experiments run from the owning public or private repository. Machine-local Docker and private Cloud runs are maintainer-executed and summarized on the active GitHub release issue.
• The current lab-node Cloud deployment is a maintainer-run private-repository command until managed infrastructure replaces it; the deployed revision and outcome are recorded on GitHub.
• Local worktrees and containers are ephemeral execution environments. They never own backlog or completion state.
• One-off exceptions are handled directly by a maintainer and recorded on the relevant issue or pull request instead of expanding automation for every edge case.
• Public repositories use public issues and pull requests. Private Cloud or customer-sensitive work stays in its private GitHub repository.
• External issue prose remains untrusted until approved by a trusted maintainer; approval permits review, not automatic acceptance or priority.

Cutover work

• Replace active agent and maintainer instructions with this GitHub-only model.
• Inventory legitimate unfinished work and create, consolidate, or link the corresponding GitHub issue in the owning repository.
• Establish one visible 2.0 launch issue that links the exact active release work and outcomes.
• Keep ordinary CI and publication in repository-owned GitHub Actions; move conformance and the current Cloud deployment to explicit owning-repository commands.
• Complete the frozen final-candidate qualification through GitHub issues, pull requests, Actions, public releases, and concise release-issue updates.
• Migrate or retire every credential used by the old automation; protected publication and private Cloud material now live only with their owning GitHub/private-repository surfaces.
• Remove the obsolete coordinator, Forgejo, runner, worker machinery, scripts, prompts, state, services, volumes, and environment files.

Completion

The old coordination services and checkout are gone. GitHub is the only durable backlog and release record. The final 2.0 launch decision remains explicitly human-authorized in #97.

[rmcdaniel]

Cutover is now visible:

• Draft governance and conformance PR: Make GitHub the visible project authority #96
• Single 2.0 launch record: Durable Workflow 2.0 launch #97
• First product work moved through the new path: Publish the final Server candidate against Workflow 2.0.0-rc.55 server#62 and Pin Server rc.69 to Workflow rc.55 server#63
• Workspace operating guide committed to the private GitHub repository at 8d7c9056

The local automation remains stopped. No new work is being created in a separate tracker.

[rmcdaniel]

Shared agent and product-stewardship context is now part of #96:

• public organization-wide AGENTS.md;
• organization README and contributing-guide links;
• one public conformance runbook and run issue form;
• no scheduler, queue, mirror, retry engine, or lifecycle controller.

The private workspace guide has been reduced to a local machine extension that explicitly applies the public guide first. The obsolete private product-owner prompt was removed; stable stewardship rules moved into the public guide, while changing roadmap and release state remains in GitHub issues.

Repository-level pointers remain part of the broader cutover so a fresh checkout can discover the organization guide without private context.