Skip to content

Wire agent-rules, ver, and issues-browser into docs hub - #1

Merged
AMDphreak merged 1 commit into
mainfrom
feature/wire-agent-rules-ver-issues-browser
Aug 8, 2026
Merged

Wire agent-rules, ver, and issues-browser into docs hub#1
AMDphreak merged 1 commit into
mainfrom
feature/wire-agent-rules-ver-issues-browser

Conversation

@AMDphreak

Copy link
Copy Markdown
Contributor

Summary

  • Playbooks source issues-browser, agent-rules, and ver
  • Tools portal stubs + nav entries

…ools hub.
Co-authored-by: Cursor <cursoragent@cursor.com>
@cursor

cursorBot commented Aug 8, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@AMDphreak
AMDphreak merged commit 1da1479 into mainAug 8, 2026
1 check passed
@AMDphreak
AMDphreak deleted the feature/wire-agent-rules-ver-issues-browser branch August 8, 2026 02:35

@cursorcursorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation review — PR #1

Verdict: The wiring is correct and follows established portal-stub patterns. Component names in remote docs/antora.yml files (agent-rules, ver, issues-browser) match the playbook URLs and portal xrefs. Production build (pnpm run build:online) completes successfully with the new content sources.

What this PR covers well

  • All three playbooks updated consistently (production, local, testing)
  • Portal stubs with description, component xref, repository link, and highlights
  • Sensible rename handling: issue-tracker → redirect stub, new issues-browser page with NOTE
  • Tools index and sidebar nav updated

Gaps addressed in follow-up PR

A companion PR adds documentation that should ship alongside this wiring:

  1. where-docs-live.adoc — Still referenced issue-tracker; now documents issues-browser, agent-rules, and ver
  2. activity-log.adoc — No entry for this integration
  3. Changelog — No changelog structure existed; index + detail pages backfilled
  4. README.adoc — Missing Docs | Dev-Centr and Deploy CI badges

Optional follow-ups (not blocking)

  • Home portal cardsindex.adoc does not yet feature Agent Rules, Ver, or Issues Browser (FixNow and Ibex have cards). Consider adding cards if these are priority surfaced tools.
  • xref style — New stubs use xref:agent-rules::index.adoc; FixNow uses xref:fixnow-dev:ROOT:index.adoc. Both resolve; consider standardizing on the explicit ROOT form for consistency.
  • AI search extension — Org playbook has Lunr but not @antora-supplemental/antora-ai-help-extension yet (org-wide, tracked separately).
Open in WebView Automation

Sent by Cursor Automation: Generate docs

* CLI, DlangUI GUI, daemon, and tray client
* SDL forge profiles (GitHub implemented; GitLab stub)

NOTE: Formerly named `issue-tracker`. Prefer `issues-browser` for new links.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good rename note. The redirect stub at issue-tracker.adoc plus this NOTE gives bookmark/link migration a clear path.

Comment threadantora-playbook.yml
branches: HEAD
start_path: docs
- url: https://github.com/dev-centr/issue-tracker.git
- url: https://github.com/dev-centr/issues-browser.git

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified against remote docs/antora.yml: component name is issues-browser (not issue-tracker). Playbook URL and portal xref align.

== Highlights

* Shared `RULES.md` + `general/` + `profiles/` for end-user agents
* Separate from product automation (`devcentr-agent-rules`)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The distinction between end-user agent rules and devcentr-agent-rules product automation is valuable context — consider mirroring this in the component repo's intro if not already there.

Sign up for freeto 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

@AMDphreak