[#371] 🤖 - Keep automated reports out of Bugbot human context

[efraespada]

📌 Summary

Preserves provider-authenticated bot classification for issue and inline review comments so automated reports are excluded from Bugbot human-discussion prompt budgets without filtering human authors based on login names.

---

🎯 Related Issues / Tickets

• Closes [#371] 🤖 - Keep automated reports out of Bugbot human context #371

---

🧩 Scope of Changes

• Added:
  • Optional isAutomatedAuthor metadata to issue and pull-request review comment ports.
  • GraphQL and REST provider-author classification mappings.
  • Tests for classification, prompt selection, and budget behavior.
• Updated:
  • Bugbot human-discussion filtering.
  • Bugbot documentation.
  • Generated bundles and declaration files.
• Removed:
  • Reliance on login-name heuristics as the source of automated-author classification.
• Refactored:
  • Comment repository mappings to preserve provider-authenticated author metadata across application boundaries.

---

🛠️ Technical Details

• GraphQL issue comments request author { login __typename } and classify __typename === 'Bot' as automated.
• REST review comments classify user.type === 'Bot' as automated.
• Provider-classified automated comments are excluded before human-discussion item and character budgets are applied.
• Human authors with automation-looking login names remain eligible for prompt context.
• The metadata is optional, preserving compatibility with existing callers and fallback paths.
• Generated build/ bundles and declarations are synchronized with the source changes.

---

🔍 How to Test

1. Run the focused Bugbot review-context, issue-comment repository, and pull-request review-comment repository test suites.
2. Verify GraphQL Bot authors and REST user.type === 'Bot' authors receive isAutomatedAuthor: true.
3. Verify human authors with automation-looking login names remain in the prompt.
4. Verify automated comments do not consume the human-discussion item or character budgets.
5. Run typecheck, lint, build, package, documentation, agent-docs, docs-page, workflow, specification, and generated-bundle validation.

---

🧪 Test Coverage

• Unit tests
• Integration tests
• End-to-end (E2E) tests

Validation covered classification mappings, prompt filtering, truncation behavior, fallback metadata, and the changed Bugbot repository surfaces. The reported validation result is 428 suites and 3,796 tests passed, with 97.48% statement, 95.48% branch, 95% function, and 97.94% line coverage on the focused changed surface.

---

📸 Screenshots / Recordings (UI changes only)

Not applicable; this PR does not change the UI.

---

⚠️ Breaking Changes

• None

---

🚀 Deployment Notes

• Requires database migration
• Requires environment variable changes
• Requires feature flag toggle
• No special deployment steps

Details: No database migrations, environment-variable changes, or feature-flag changes are required. Generated bundles are synchronized for packaging and deployment.

---

🔒 Security Considerations

• Sensitive data handling changes

Provider-authenticated author classification defines the boundary for excluding automated discussion from prompt budgets. Human authors are not filtered by login-name heuristics, and discussion remains untrusted context for analysis.

---

📈 Performance Impact

• No performance impact
• Improves performance
• Potential performance regression (explain)

Automated reports no longer consume the bounded human-discussion item and character budgets, leaving more budget for human-authored context.

---

📝 Notes for Reviewers

Verify the metadata flow across GraphQL issue comments, REST inline review comments, prompt filtering, truncation behavior, and fallback paths. Confirm that classification is provider-authenticated and is never inferred solely from a login name.

---

✅ Checklist

• I have self-reviewed my code
• Code follows project standards and conventions
• Tests have been added or updated
• Documentation has been updated (if applicable)
• No new warnings or lint errors
• Breaking contract changes and required consumer updates are documented

---

📚 Additional Context

Typecheck, lint, build, npm package, documentation, agent docs, docs-page, workflow, and specification validation passed. Generated bundles are synchronized, and graphify was updated.

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~371

Documentation is deployed and generated using docs.page

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.12%. Comparing base (274db40) to head (c2a19e8).
⚠️ Report is 710 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #371      +/-   ##
===========================================
+ Coverage    90.94%   92.12%   +1.18%     
===========================================
  Files          135      642     +507     
  Lines         6251    16465   +10214     
  Branches      1338     4242    +2904     
===========================================
+ Hits          5685    15169    +9484     
- Misses         172      523     +351     
- Partials       394      773     +379     

Files with missing lines	Coverage Δ
...ases/steps/commit/bugbot/bugbot_finding_context.ts	68.57% <ø> (ø)
...cases/steps/commit/bugbot/bugbot_review_context.ts	100.00% <100.00%> (ø)
...ory/issue/bugbot_issue_comment_query_repository.ts	96.87% <100.00%> (ø)
...st/pull_request_review_comment_query_repository.ts	88.13% <100.00%> (ø)

... and 700 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[vypbot]

Bugbot: review complete

Current status: No active findings on c2a19e8.

Pull request · Verified commit · Workflow run