Skip to content

Home

Jump to bottom
issuelens[bot] edited this page Oct 10, 2026 · 13 revisions

Welcome to the IssueLens wiki!

Project documentation

  • README: short public overview, capabilities, example requests, and getting-started links.
  • Contributing: development setup, repository layout, agent/skill maintenance, local checks, CI, and pull request guidance. Keep contributor instructions here rather than expanding the public overview.
  • Setup and usage guide: local execution, configuration, protocols/media, automation, team memory, Foundry authentication, deployment, and troubleshooting, with a topic table of contents. Operational details belong here; older commit-pinned README citations elsewhere in this wiki remain historical evidence.

Source: microsoft/IssueLens#48, merged at cdc30c04aa325859cc50cccc530d791c5477eb05, also the inspected push-after/source-tip revision. Documentation-contract tests now target the contributor guide for CI instructions and the setup guide for operational details. This documentation/test reorganization changes no runtime code, agent prompts, or workflow files and does not establish deployment. The 12-file inventory and merged blob identities were checked; 11 PR patches were inspected, while the oversized README patch was replaced by a full merged README read. Tests were inspected, not executed during maintenance.

Architecture

  • Foundry model authentication: Microsoft Entra-only inference, token lifecycle, configuration, and identity/migration guidance.
  • Tool execution and recovery: execution envelopes, agent-owned recovery, exact-base wiki publication, notification acceptance, and safe failure telemetry.
  • The deployed IssueLens orchestrator runtime prompt is maintained at agents/issuelens.md. It is intentionally separate from repository-maintenance instructions.
  • .github/copilot-instructions.md provides guidance for GitHub Copilot coding assistants maintaining this repository; it is not the deployed orchestrator runtime prompt.
  • Large-change investigation uses existing GitHub MCP reads in ordinary agent turns: PR file pages and commit file pages can be requested through page 3,000 (subject to GitHub's 3,000-file ceiling). get_commit defaults to stats (no patches); callers request full_patch explicitly when needed. The read-only change-analysis skill is preloaded for triage, planning, and team-memory, and requires source revalidation and explicit reporting of incomplete evidence rather than a separate analysis runtime. Source: PR #35, merge commit df2d74fa007d468dab9f6137cfed4ef4ccaa92df.
  • PR metadata compatibility: get_pull_request alone pins its REST request to 2022-11-28 to retain GitHub's authoritative merge_commit_sha, removed from the 2026-03-10 response schema. The pin covers App-authenticated and anonymous public reads; other REST operations retain the 2026-03-10 default. Repository scope, pull_requests: read permission, public-read fallback, response limits, and write safeguards are unchanged; no fallback lookup or inferred merge SHA is introduced. Open PRs retain GitHub's null or temporary merge SHA, which is not evidence of a completed merge. Removing the pin requires an authoritative replacement for merged-commit verification. Schema-aware mocked tests cover both authentication paths, merged/open values, and isolation from other reads and writes; this is not live deployment verification. Sources: PR #37, merge commit 41d9c266de2b603999209d6e1a3129afd931132e, pinned implementation, tests, and compatibility documentation.

Engineering and operations

  • Foundry deployment: manual approval and exact-commit CI gates, pinned azd extensions, identity/configuration prerequisites, protocol smoke checks, and recovery limits.
  • The repository CI workflow runs for pull requests and for pushes to main. It uses read-only repository permissions, disables persisted checkout credentials, cancels superseded runs for the same workflow/ref or pull request, and applies per-job timeouts.
  • CI runs the application unittest suite on Python 3.13. MCP tests and the MCP package build/install smoke test run on Python 3.12 and 3.13; the package check builds both distribution formats, installs the wheel into a clean virtual environment, verifies dependencies, and imports the issuelens-github-mcp console-script entry point.
  • A separate workflow-validation job installs an immutable actionlint revision and validates the repository workflow files. Compatibility exceptions are scoped to the existing Copilot billing-probe permission and the exact unsupported concurrency queue diagnostic in team-memory-coordinator.yml; tests enforce the coordinator queue settings. Source: PR #50, merge commit 4175ea71e170938826fb847e6bd5108f0f5597cf.
  • Team-memory automation: opt-in standalone push dispatcher, shared coordinator queue for automatic ranges and manual PR requests, artifact-free source preflight, credentials, publication receipts, and recovery limits. The IssueLens coordinator remains same-source by default; reconciliation verifies a caller-selected range, not the original push boundary. Source: PR #51, merge commit 0bc63baa3b6426b1f22daabe80e4ab004801f39b. This is merged-source behavior, not live deployment verification.
  • Team-memory workflow tests validate actions/checkout and azure/login by exact action identity plus a 40-character lowercase hexadecimal commit SHA, rather than duplicating particular dependency revisions. Tags, branches, abbreviated SHAs, other actions, and trailing content are rejected. Trusted workflow-SHA checkout, disabled credential persistence, sparse checkout, and preflight-ordering assertions remain intact. This test-only change does not change workflow pins or runtime behavior. Source: PR #46, merge commit f71690af4cc87d0fffc1aeb69cbd82540259fc43; tests at that revision are identical at inspected source tip b61ece62ffb5555ae979855a3a694ea96d513bc0. Tests were inspected, not executed during maintenance.
  • These checks describe repository CI coverage, not a release or deployment guarantee. Source: PR #30, merge commit 49df3d97547069f891a68248be6ed722c2aeca2f.
  • Run usage is complete only when a root-agent usage observation exists; subagent-only usage remains partial, while an observed zero-token root call is valid coverage. Source: PR #35, merge commit df2d74fa007d468dab9f6137cfed4ef4ccaa92df.

Decisions

Clone this wiki locally