feat(github-agent): add @gittensory ask command with cited contribution-context output

[claytonlin1110]

Summary

• Add @gittensory ask <question> to support contribution-quality Q&A from connected cached sources with source/freshness notes.
• Thread parsed question text into mention command orchestration so responses can be scoped to the user’s prompt.
• Add tests for parsing/rendering and preserve public-surface sanitizer boundaries.
  Closes feat(github-agent): add repo and docs context Q&A from connected sources #142

Scope

• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked an issue, or this is small enough that the summary explains why an issue is not needed.

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; global coverage stays at or above 97% for lines, statements, functions, and branches (aim for 98%+ branch coverage locally so CI variance does not fail near the threshold)
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

• Ran targeted suites for touched behavior:
  • vitest run test/unit/github-commands.test.ts
  • vitest run test/unit/queue.test.ts
  • vitest run test/unit/product-usage.test.ts test/unit/openapi.test.ts test/integration/api.test.ts
• Full repo validation matrix was not run in this local pass.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include screenshots or a short recording.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

Notes

• Touches:
  • src/github/commands.ts
  • src/queue/processors.ts
  • test/unit/github-commands.test.ts
• Net diff: 69 insertions, 5 deletions.
• Issue context: feat(github-agent): add repo and docs context Q&A from connected sources #142

[dosubot]

Related Knowledge

2 documents with suggested updates are ready for review.

gittensory

For Maintainers

View Suggested Changes

@@ -350,6 +350,16 @@
 @gittensory help
 ```
 
+##### `@gittensory ask <question>`
+
+Answers contribution-quality questions from connected cached sources with citations and freshness notes. Supports contribution-quality Q&A with source citations from connected cached sources including GitHub issues/PRs/recent merges/checks, signal snapshots, focus manifest, and upstream ruleset status. Answer scope is limited to contribution quality and repository policy. Sources are cited with freshness and public-boundary redaction.
+
+**Example:**
+
+```
+@gittensory ask what are the coding standards for this repo?
+```
+
 ##### `@gittensory preflight`
 
 Summarizes PR hygiene and validation readiness. Shows up to 3 relevant actions from preflight analysis, including linked context, branch freshness, and validation status [[48]](https://github.com/JSONbored/gittensory/blob/1e7506f4c5226d0b9b5da8fcd219309d84bacfcd/src/github/commands.ts#L165-L180).

✅ Accepted

Gittensory Architecture

View Suggested Changes

@@ -80,7 +80,7 @@
 - `backfill.ts`: Syncs repos, issues, and PRs from GitHub's REST API
 - `webhook.ts`: Handles incoming GitHub webhook events
 - `app.ts`: Manages GitHub App installation and token generation
-- `commands.ts`: Parses @gittensory mention commands (help, preflight, blockers, duplicate-check, miner-context, next-action, reviewability, repo-fit, packet, queue-summary, review-now, needs-author, confirmed-miners, duplicate-clusters). The last five commands are maintainer-only queue digest commands that build from cached GitHub metadata rather than agent runs [[25]](https://github.com/JSONbored/gittensory/pull/190)
+- `commands.ts`: Parses @gittensory mention commands (help, ask, preflight, blockers, duplicate-check, miner-context, next-action, reviewability, repo-fit, packet, queue-summary, review-now, needs-author, confirmed-miners, duplicate-clusters). The last five commands are maintainer-only queue digest commands that build from cached GitHub metadata rather than agent runs [[25]](https://github.com/JSONbored/gittensory/pull/190)
 - `comments.ts`: Posts public-safe intelligence comments to PRs/issues
 - `labels.ts`: Applies Gittensor labels based on repository settings
 - `public.ts`: Fetches public GitHub user profiles

✅ Accepted

^{How did I do? Any feedback?}  

[JSONbored]

@claytonlin1110 the @gittensory ask command is a good product direction, and the public-surface sanitizer coverage is the right constraint.

A few notes:

• Parsing the question text and threading it into the command objective is useful.
• The command is still behaviorally weaker than the PR title/body promise.
• The current output mostly repackages agent actions and generic source notes; it does not provide concrete cited source references.
• The refresh path for ask currently renders Next-action snapshot refresh, which is the wrong command framing.

Required changes:

• Make ask output concrete contribution-context source references, or narrow the PR/body copy so it does not claim cited output.
• Fix the refresh path so @gittensory ask uses ask/contribution-context refresh wording.
• Add tests that assert source/freshness details are present for successful ask output and that refresh output uses the ask label.

Validation expected:

• Re-run validate, with focused coverage for parser, command rendering, authorization, and public-output sanitizer paths.

[claytonlin1110]

@JSONbored updated. please review

[JSONbored]

@claytonlin1110 this is closer, but the ask command still needs stronger cited-source behavior.

Required changes:

• Ensure answers include concrete cited source references, not just generic snapshot language.
• Complete the validation matrix or explain any skipped checks.
• Keep public output sanitized and low-noise.

Validation expected:

• npm run test:ci
• Targeted GitHub command/output tests for cited ask responses

[claytonlin1110]

@claytonlin1110 the @gittensory ask command is a good product direction, and the public-surface sanitizer coverage is the right constraint.

A few notes:

• Parsing the question text and threading it into the command objective is useful.
• The command is still behaviorally weaker than the PR title/body promise.
• The current output mostly repackages agent actions and generic source notes; it does not provide concrete cited source references.
• The refresh path for ask currently renders Next-action snapshot refresh, which is the wrong command framing.

Required changes:

• Make ask output concrete contribution-context source references, or narrow the PR/body copy so it does not claim cited output.
• Fix the refresh path so @gittensory ask uses ask/contribution-context refresh wording.
• Add tests that assert source/freshness details are present for successful ask output and that refresh output uses the ask label.

Validation expected:

• Re-run validate, with focused coverage for parser, command rendering, authorization, and public-output sanitizer paths.

@JSONbored Updated

[JSONbored]

@claytonlin1110 this still needs stronger cited-source behavior.

A few notes:

• Adding @gittensory ask is the right product direction.
• The parser and sanitizer coverage are useful.
• The title/body promise is still stronger than the current output unless concrete source references are included.

Required changes:

• Make successful ask responses include concrete cited source/freshness references.
• Fix any refresh wording so it reads as ask/contribution-context behavior, not generic next-action refresh.
• Complete the validation matrix or explain skipped checks precisely.

Validation expected:

• Full npm run test:ci
• Focused GitHub command rendering tests for cited ask output

[claytonlin1110]

@claytonlin1110 this still needs stronger cited-source behavior.

A few notes:

• Adding @gittensory ask is the right product direction.
• The parser and sanitizer coverage are useful.
• The title/body promise is still stronger than the current output unless concrete source references are included.

Required changes:

• Make successful ask responses include concrete cited source/freshness references.
• Fix any refresh wording so it reads as ask/contribution-context behavior, not generic next-action refresh.
• Complete the validation matrix or explain skipped checks precisely.

Validation expected:

• Full npm run test:ci
• Focused GitHub command rendering tests for cited ask output

Fixed

[JSONbored]

approving for merge.