Onboard IssueLens for Java Pack

[Changyong Gong (chagong)]

Summary

• Replace the local CLI/email triage workflow with the shared IssueLens action pinned to 49df3d97547069f891a68248be6ed722c2aeca2f. Handle opened/reopened issues, human issue comments, and default-branch manual runs without checkout or PR-code execution. Use read-only GitHub workflow permissions plus OIDC and activity/status output; remove the legacy email/output-artifact steps.
• Add opt-in post-merge team memory for PRs merged into the default branch, plus guarded manual runs using the same action pin.
• Configure four policy domains: additive labeling; read-only duplicate search across ten Java tooling repositories with evidence-backed High confidence (90–100); new assignments limited to chagong or wenytang-ms using commit history or the approved fallback; and an architecture-based wiki structure explicitly targeting microsoft/vscode-java-pack. Preserve existing labels/assignees, explicit write authorization, source provenance, and wiki consistency safeguards. The native duplicate threshold replaces the old retrieval cutoff by maintainer decision, not numeric conversion.

Validation

• actionlint 1.7.12 passed for both workflows.
• Configuration passed the published IssueLens JSON schema at the pinned revision.
• 92 focused assertions passed, including 18 event/ref/actor/opt-in gate cases, current policy decisions, existing labels, local links, and exact seven-file scope.
• git diff --check passed; no source-code changes require an extension build.

Rollout prerequisites

Live Azure/OIDC, agent, GitHub App, and wiki operation was not exercised or configured. Supply AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_SUBSCRIPTION_ID, ISSUELENS_AGENT_URL (the deployed HTTPS invocation endpoint), and ISSUELENS_AGENT_SCOPE. Verify event/ref-scoped OIDC federation for issue events, dispatch, and post-merge runs; source App access and authorized issue writes; and an initialized destination wiki with App Contents read/write permissions.

Set ISSUELENS_TEAM_MEMORY_ENABLED=true only when memory maintenance is ready. No workflow dispatch, runtime activation, permission/secret changes, wiki writes, or other-repository onboarding is included.

[Copilot]

🟡 Changes recommended

Retire or gate the legacy triage path before enabling the new issue trigger to prevent duplicate or conflicting updates.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Onboards the pinned IssueLens action for Java Pack issue triage and optional post-merge team-memory maintenance.

Changes:

• Replaces local triage automation with guarded IssueLens workflows.
• Adds labeling, duplicate detection, assignment, and wiki-memory policies.
• Adds opt-in post-merge team-memory maintenance.

File summaries

File	Summary
.github/workflows/team-memory-post-merge.yml	Optional post-merge team-memory workflow.
.github/workflows/issueLens-run.yml	Issue event and manual-run IssueLens workflow; its issues: opened trigger overlaps with the legacy triage workflow and may cause duplicate or conflicting updates.
.github/issuelens/team-memory.md	Wiki organization, provenance, and maintenance safeguards.
.github/issuelens/labels.md	Additive labeling rules.
.github/issuelens/duplicates.md	Bounded duplicate-detection policy.
.github/issuelens/assignment.md	Assignment restrictions and preservation rules.
.github/issuelens.yml	IssueLens policy-domain and wiki-target configuration.

Review details

• Files reviewed: 7/7 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[wenyt (wenytang-ms)]

better to send message for some necessary info update to maintainer.