docs: two-tracker public/private issue tracking (open-core) (#1212)

* docs: split issue tracking into public/private trackers (open-core)

Reconcile contributor-facing docs and the issue-template chooser with the
two-tracker model: bugs/refactor/docs -> public abilityai/trinity;
features/epics -> private abilityai/trinity-enterprise.

- CONTRIBUTING/README: feature requests now route to Discussions (Ideas);
  issues are bugs-only. Removed the public Feature Request template; the
  New Issue chooser offers Bug Report + a "Request a feature" link to
  Discussions, with blank_issues_enabled: false. bug_report uses type-bug.
- CLAUDE.md / AGENTS.md: routing pointer to DEVELOPMENT_WORKFLOW Repository Routing.
- docs/OSS_VS_ENTERPRISE: new "Issue tracking (two-tracker model)" section.
- docs/GITHUB_ISSUES_MIGRATION: marked superseded.
- Bump .claude (trinity-dev) submodule: workflow doc + skill reconciliation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: move OSS_VS_ENTERPRISE.md to private enterprise repo

The comparison doc holds enterprise roadmap intent (in-development/planned
modules, tiering direction, licensing status). Per the two-tracker open-core
model this belongs in the private tracker, not the public repo. Relocated to
abilityai/trinity-enterprise:docs/OSS_VS_ENTERPRISE.md (commit 50318ff).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Eugene Vyborov <eugene@beingluminous.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: 3 people

.claude

@@ -2,7 +2,7 @@
 name: Bug Report
 about: Report a bug to help us improve Trinity
 title: '[BUG] '
-labels: bug
+labels: type-bug
 assignees: ''
 ---
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,8 +1,11 @@
-blank_issues_enabled: true
+blank_issues_enabled: false
 contact_links:
+  - name: 💡 Request a feature / share an idea
+    url: https://github.com/abilityai/trinity/discussions/new?category=ideas
+    about: Feature requests go in Discussions → Ideas. Maintainers triage accepted ideas onto the roadmap. The issue tracker is for bugs and core maintenance only.
+  - name: Questions & general discussion
+    url: https://github.com/abilityai/trinity/discussions
+    about: Ask questions, share what you built, and discuss with the community
   - name: Documentation
     url: https://github.com/abilityai/trinity#documentation
     about: Check the documentation before opening an issue
-  - name: Discussions
-    url: https://github.com/abilityai/trinity/discussions
-    about: Ask questions and discuss features

.github/ISSUE_TEMPLATE/config.yml

@@ -121,7 +121,7 @@ Caveats that matter to agents:
 - Tests: `python -m pytest -v --tb=short` (markers: `unit` needs no backend, `requires_agent` needs a running agent).
 - Layout: `src/backend` (FastAPI), `src/frontend` (Vue 3 + Pinia), `src/mcp-server` (TypeScript MCP proxy), `src/cli`, `docker/base-image` (agent runtime).
 - Backend pattern: router → service → db (`src/backend/routers|services|db`); schema changes require a versioned migration in `src/backend/db/migrations.py`.
-- Workflow: GitHub Issues with priority/type/theme labels; feature branches off `dev`; PRs target `dev` (releases merge `dev` → `main`). See [CONTRIBUTING.md](CONTRIBUTING.md).
+- Workflow: GitHub Issues with priority/type/theme labels; feature branches off `dev`; PRs target `dev` (releases merge `dev` → `main`). **Two-tracker open-core model:** bugs/refactor/docs live in public `abilityai/trinity`; features/epics in private `abilityai/trinity-enterprise` (see `.claude/DEVELOPMENT_WORKFLOW.md` → Repository Routing). See [CONTRIBUTING.md](CONTRIBUTING.md).
 
 ## Documentation map
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -90,7 +90,9 @@ All work follows a 4-stage lifecycle tracked via **GitHub Issues** (labels + ope
 - **In Dev**: PR squash-merged to `dev` — `status-in-dev` label, awaiting the next release cut (dev → main)
 - **Done**: Release PR merged to `main`, issue auto-closed via `Closes #N`
 
-**Full details**: `.claude/DEVELOPMENT_WORKFLOW.md`
+**Two trackers (open-core).** Issues route by type: `type-bug`/`type-refactor`/`type-docs` → public `abilityai/trinity`; `type-feature`/`type-epic` → private `abilityai/trinity-enterprise`. Tracker ≠ code repo — core code still lands as a public-repo PR. Query/picking skills union both trackers.
+
+**Full details**: `.claude/DEVELOPMENT_WORKFLOW.md` (→ Repository Routing)
 
 ---
 
@@ -108,7 +110,7 @@ All work follows a 4-stage lifecycle tracked via **GitHub Issues** (labels + ope
 - No creating documentation files unless explicitly requested
 
 ### 3. Follow the Roadmap
-- Check **GitHub Issues** for current priorities (`/roadmap` or `gh issue list`) — labels are the single source of truth
+- Check **GitHub Issues** for current priorities (`/roadmap` or `gh issue list`) — labels are the single source of truth. `/roadmap` unions both trackers (public bugs + private features/epics); a raw `gh issue list` sees only one repo — pass `--repo abilityai/trinity-enterprise` for feature/epic work
 - Work P0 issues first, then P1 (`type-bug` before `type-feature`, then newest issue number first), then P2/P3
 - Assign yourself and update `status-*` labels as you progress (see SDLC above)
 - Close issues when complete
@@ -155,7 +157,7 @@ Long-running multi-stage work inside agents (perception → synthesis → publis
 | `docs/planning/TARGET_ARCHITECTURE.md` | **Target system design + active orchestration direction** — pull / work-stealing coordination (Epic #1045, umbrella #1081). Use when evaluating tradeoffs and prioritizing work; consult before touching `task_execution_service`, `capacity_manager`, `slot_service`, `backlog_service`, `dispatch_breaker`, or `cleanup_service`. |
 | `docs/memory/feature-flows.md` | Index of vertical slice docs |
 | `docs/archive/plans/ORCHESTRATION_RELIABILITY_2026-04.md` | **Archived (historical)** — completed Sprint A–D′ execution-reliability plan (all shipped). Superseded 2026-06-05 by the pull-coordination direction in `TARGET_ARCHITECTURE.md`. Read for background on the slot/backlog/cleanup machinery. |
-| GitHub Issues | Prioritized task queue — labels are authoritative: priority (P0-P3), type, `theme-*`, `complexity-*`; status via `status-*` labels + open/closed; epics are `type-epic` issues with native sub-issues. No project board. |
+| GitHub Issues | Prioritized task queue — labels are authoritative: priority (P0-P3), type, `theme-*`, `complexity-*`; status via `status-*` labels + open/closed; epics are `type-epic` issues with native sub-issues. No project board. **Two trackers:** bugs/refactor/docs in public `abilityai/trinity`, features/epics in private `abilityai/trinity-enterprise` (see `.claude/DEVELOPMENT_WORKFLOW.md` → Repository Routing). |
 
 ---
 
@@ -343,7 +345,7 @@ The **[abilities](https://github.com/abilityai/abilities)** repo is the canonica
 - **Orchestration Reliability Plan (archived)**: `docs/archive/plans/ORCHESTRATION_RELIABILITY_2026-04.md` ← Sprint A–D′ historical record; superseded by `docs/planning/TARGET_ARCHITECTURE.md` (pull coordination) as the active execution-stack direction
 - **Full Architecture**: @docs/memory/architecture.md
 - **All Requirements**: `.claude/memory/requirements.md`
-- **Current Roadmap**: https://github.com/abilityai/trinity/issues
+- **Current Roadmap**: https://github.com/abilityai/trinity/issues (public bugs) + private `abilityai/trinity-enterprise` (features/epics) — use `/roadmap` to see both
 - **Recent Changes**: `git log --oneline --since="2 weeks ago"`
 - **Agent Guide**: `docs/TRINITY_COMPATIBLE_AGENT_GUIDE.md`
 - **Agent Network Demo**: `docs/AGENT_NETWORK_DEMO.md`

AGENTS.md

@@ -14,6 +14,12 @@ Trinity is licensed under the [Apache License 2.0](LICENSE). Unless you explicit
 
 ## How to Contribute
 
+> **Where things are tracked.** Trinity is open-core. The public issue tracker
+> ([abilityai/trinity](https://github.com/abilityai/trinity/issues)) is for
+> **bugs and core maintenance**. Feature ideas and roadmap discussion happen in
+> [Discussions](https://github.com/abilityai/trinity/discussions) — maintainers
+> triage accepted proposals into the product roadmap.
+
 ### Reporting Bugs
 
 1. Check if the issue already exists in [GitHub Issues](https://github.com/abilityai/trinity/issues)
@@ -26,10 +32,11 @@ Trinity is licensed under the [Apache License 2.0](LICENSE). Unless you explicit
 
 ### Suggesting Features
 
-1. Open an issue with the `enhancement` label
-2. Describe the use case and problem you're solving
-3. Propose a solution (optional)
-4. Be open to discussion and alternatives
+Feature ideas go in **Discussions**, not Issues — the public tracker stays focused on bugs, and maintainers curate the roadmap from accepted proposals.
+
+1. Open a [Discussion](https://github.com/abilityai/trinity/discussions) describing the use case and the problem you're solving
+2. Propose a solution (optional) and be open to alternatives
+3. Accepted ideas are picked up by maintainers and tracked on the roadmap
 
 ### Pull Requests
 

CLAUDE.md

@@ -701,8 +701,8 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 ## Community & Support
 
 - **Ask Trinity**: [docs.ability.ai](https://docs.ability.ai) — full documentation with a built-in agent you can chat with for instant answers
-- **GitHub Issues**: [Report bugs and request features](https://github.com/abilityai/trinity/issues)
-- **GitHub Discussions**: [Ask questions and share ideas](https://github.com/abilityai/trinity/discussions)
+- **GitHub Issues**: [Report bugs](https://github.com/abilityai/trinity/issues) — the public tracker is for bugs & core maintenance
+- **GitHub Discussions**: [Request features, ask questions, share ideas](https://github.com/abilityai/trinity/discussions) — feature ideas are triaged into the roadmap here
 - **Videos**: [Trinity Demo](https://youtu.be/ivljtZqsxeo) · [Loops Engineering](https://youtu.be/q3YvFYtuhec) · [Autonomous Cornelius](https://youtu.be/QUZ5ZgB5f6E)
 - **Free Workshops**: [Live every Thursday + full recording archive](https://www.ability.ai/workshops)
 - **Security Issues**: See [SECURITY.md](SECURITY.md) for reporting vulnerabilities

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # GitHub Issues Migration Plan
 
-> **Status**: Migration complete. Roadmap is now tracked via GitHub Issues and the **Trinity Roadmap** project board. The old `docs/memory/roadmap.md` has been archived to `docs/memory/roadmap-archive.md`. See `CONTRIBUTING.md` for the current SDLC.
+> **Status**: Historical (migration complete). Roadmap moved from `docs/memory/roadmap.md` (archived to `docs/memory/roadmap-archive.md`) to GitHub Issues. **Superseded since:** the project board was deprecated (issues-only SDLC), and tracking is now split across **two trackers** — public `abilityai/trinity` (bugs/refactor/docs) and private `abilityai/trinity-enterprise` (features/epics). For the current model see `.claude/DEVELOPMENT_WORKFLOW.md` → Repository Routing and `CONTRIBUTING.md`.
 >
 > Original purpose: Migrate from `docs/memory/roadmap.md` to GitHub Issues for roadmap tracking.