Standardize GitHub work management across repositories

[LucasSantana-Dev]

Goal

Establish one shared GitHub work-management contract across Forge Space:

• Discussions for intake, RFCs, Q&A, and announcements
• Issues for the canonical actionable backlog
• Projects for roadmap, prioritization, and reporting

Why

Repo-local issue templates and missing discussion/project defaults are creating drift between repositories and making backlog intake inconsistent.

Rollout checklist

• Ship org-level issue forms and discussion forms in Forge-Space/.github
• Publish a governance document that defines the Discussions / Issues / Projects split
• Audit repo-local ISSUE_TEMPLATE overrides and converge where possible
• Enable Discussions with the expected categories in repos that should use them
• Provision org-level Project fields and views for roadmap tracking

Repositories with known local issue-template overrides

• Forge-Space/core
• Forge-Space/ui-mcp
• Forge-Space/mcp-gateway
• Forge-Space/branding-mcp
• Forge-Space/siza-gen
• Forge-Space/siza

Note

The file-based defaults can land now. Live GitHub Project provisioning and some discussion/category enablement still depend on an authenticated GitHub CLI or manual admin setup.

[LucasSantana-Dev]

Rollout status update:

• Draft baseline PR is open in docs: add shared GitHub work management baseline #9.
• The umbrella issue now has explicit child issues for the remaining live rollout work:
  • Provision org-level GitHub Project for roadmap reporting #10 org-level GitHub Project provisioning
  • Enable and align GitHub Discussions categories across repositories #11 Discussions enablement and category alignment
  • Audit repo-local issue template overrides against the org baseline #12 repo-local ISSUE_TEMPLATE override audit
• The file-backed baseline is ready to review. The remaining gap is live GitHub admin work, which still needs authenticated gh access or equivalent manual org/repo admin action.

Current blocker on this machine:

• gh auth status is invalid
• GITHUB_TOKEN and GH_TOKEN are not exported

That means I can keep shipping repo-backed governance changes through the connector, but I cannot provision org Projects or change live repo settings through the CLI path yet.

[LucasSantana-Dev]

Scope note for this rollout:

• From this point forward, the active rollout scope is Forge-Space only.
• All new issues, project artifacts, and roadmap surfaces should remain in English.
• vsantana-organization is intentionally paused and out of scope for the current pass.

[LucasSantana-Dev]

Project wiring is now live on the existing Forge Space org projects:

• Platform Roadmap: Platform Roadmap
• Engineering Board: Engineering Board

Current seeding:

• .github#8, .github#11, .github#12 are on Platform Roadmap
• .github#11 and .github#12 are on Engineering Board

That means the rollout is no longer tracked only by issues and PRs. It now has actual roadmap cards and engineering-board visibility on the org-level surfaces.

[LucasSantana-Dev]

Rollout update:

• org baseline PR docs: add shared GitHub work management baseline #9 is merged
• the first repo-level convergence batch is open:
  • docs: inherit org GitHub workflow baseline core#184
  • docs: inherit org GitHub workflow baseline ui-mcp#186
  • docs: inherit org GitHub workflow baseline mcp-gateway#278
  • docs: inherit org GitHub workflow baseline branding-mcp#67
  • docs: inherit org GitHub workflow baseline siza-gen#56

This moves the work from org setup into repo execution. The remaining template-convergence outlier is Forge-Space/siza#581, which needs a repo-specific pass.

[LucasSantana-Dev]

The last template-convergence outlier now has an implementation PR:

• docs: align GitHub workflow with org baseline siza#582

At this point the active Forge Space rollout is fully represented by open PRs and closed Discussions-enable issues rather than local-only notes.