Skip to content

spec: add-features-roadmap-menu (proposal only)#1306

Open
rubenvdlinde wants to merge 2 commits intobetafrom
specs/features-roadmap-menu
Open

spec: add-features-roadmap-menu (proposal only)#1306
rubenvdlinde wants to merge 2 commits intobetafrom
specs/features-roadmap-menu

Conversation

@rubenvdlinde
Copy link
Copy Markdown
Contributor

Summary

Proposes a cross-repo Features & Roadmap menu item mounted in every Conduction app's NcAppNavigationSettings slot, above the Settings gear. Spec-only PR — no implementation yet.

  • Features tab: shipped capabilities extracted at build time from each app's own openspec/specs/ into docs/features.json (committed; also powers a shared Docusaurus public features page).
  • Roadmap tab: open GitHub issues from the app's own repo, sorted by reactions, with a pipeline-label blocklist and full markdown body rendering (marked + DOMPurify).
  • Suggest-feature modal: user-generated feature requests as the primary value — launched from the route header and from any widget/page declaring a specRef via its NcActions menu.
  • Backend: extends existing GitHubHandler with listIssues() + createIssue(); user PAT preferred, server PAT fallback with attribution prefix; 1 submission per user per 60s rate limit.

Capabilities introduced

  • github-issue-proxy — GET + POST endpoints on OpenRegister
  • features-roadmap-menu — cross-repo UX contract (component, manifest, Docusaurus)

Out of scope (deferred to follow-ups)

  • Company-wide ADR mandating fleet-wide adoption (drafted separately in hydra)
  • Adoption PRs in every app beyond the OpenRegister pilot
  • GitHub Discussions integration (chose Issues directly)
  • "Accept → specter → spec" wiring
  • Webpack plugin flavour of the manifest generator

Validates

`openspec validate add-features-roadmap-menu --strict` → 0 errors.

Test plan

  • Architecture review of `design.md` (22 decisions documented)
  • Verify `specs/github-issue-proxy/spec.md` requirements match existing `GitHubHandler` surface
  • Verify `specs/features-roadmap-menu/spec.md` covers all UI states (loading, empty, rate-limited, no PAT)
  • Confirm task split maps cleanly onto backend / shared-lib / manifest / docusaurus / pilot boundaries

Proposes a cross-repo Features & Roadmap menu item mounted in every
Conduction app's NcAppNavigationSettings slot above the gear.

- Features tab: shipped capabilities from openspec/specs/, extracted
  at build time into docs/features.json (committed, also powers
  Docusaurus public features page)
- Roadmap tab: open GitHub issues from the app's own repo, sorted by
  reactions, with pipeline-label blocklist and full markdown body
  rendering
- Suggest-feature modal launched from the route header and from any
  widget/page declaring a specRef via its NcActions menu
- Extends existing GitHubHandler with listIssues() + createIssue();
  user PAT preferred, server PAT fallback with attribution prefix
- Out of scope: ADR-019 fleet rollout, Discussions, Accept->specter wiring

Capabilities:
- github-issue-proxy
- features-roadmap-menu

Validates strict.
Base automatically changed from development to beta April 22, 2026 12:38
Hydra's orchestrator requires a hydra.json per change to dispatch. Adds
the schema-v2 file pointing at issue #1328 with empty depends_on (greenfield
change with no spec dependencies).

Without this file, Hydra's supervisor silently skips the change even if
it carries the `ready-to-build` label.
@github-actions
Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openregister @ aec02a2

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 147/147
npm ✅ 599/599
PHPUnit
Newman
Playwright ⏭️

Quality workflow — 2026-04-22 18:20 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant