feat(mcp): remote instance (device) read tools

[andypalmi]

Summary

Phase 1 read-only MCP tool for the remote instance (device) resource, added to forge/ee/lib/mcp/tools/devices.js:

• platform_list_team_provisioning_tokens - GET /teams/:teamId/devices/provisioning. Lists a team's device provisioning tokens. The summary view omits the token secret, so it is safe to expose read-only.

The tool describes the device resource, so it is filed with the existing device tools, following the one-file-per-resource convention. It is annotated readOnlyHint: true, destructiveHint: false.

Consolidation notes

• The remote instance audit-log, history, and HTTP-tokens reads that this PR originally carried are generalized on feat(mcp): hosted instance read tools #7727. platform_get_instance_audit_log, platform_get_instance_history, and platform_list_instance_http_tokens each take an instanceType: 'hosted' | 'remote' argument and live in the new forge/ee/lib/mcp/tools/shared-instances-devices.js, so they serve remote instances (devices) too and no remote-only variants are needed here.
• The CSV audit-log export is dropped. The GET /devices/:id/audit-log/export route only produces CSV, which is not a useful shape for an automation tool; the shared platform_get_instance_audit_log returns audit entries as JSON.

Permissions

No permissions changes. #8185 removed the hardcoded user:expert-mcp scope allow-list, so expert MCP tokens now inherit the user's permissions gated by team role and no allow-list entries are needed.

Closes #7708

Test plan

• eslint clean on the changed files
• mocha unit tests

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.95%. Comparing base (d3419bb) to head (c9274df).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7726   +/-   ##
=======================================
  Coverage   75.94%   75.95%           
=======================================
  Files         445      445           
  Lines       23990    23994    +4     
  Branches     6404     6404           
=======================================
+ Hits        18220    18224    +4     
  Misses       5770     5770           

Flag	Coverage Δ
backend	75.95% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 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.

[andypalmi]

Testing results of new/changed tools

@cstns for visibility.

This PR now adds a single tool, platform_list_team_provisioning_tokens, which was invoked against a running local platform. The context the calls ran against:

• Three teams were available; one was seeded with a single device provisioning token, the other two had none.
• The seeded token was created through the platform's own create route, whose response returns the token secret; the list summary is expected to omit that secret.

Payloads below are redacted for ids, names and secrets; structural values (counts, statuses, error codes, and which fields are present) are verbatim. No credential secret is reproduced.

platform_list_team_provisioning_tokens

Lists a team's device provisioning tokens. The summary view omits the token secret.

Case	Input params	Verdict	Returned payload (redacted)
team with no tokens	{teamId: TEAM_ID}	PASS	{meta:{}, count:0, tokens:[]}
team with one token	{teamId: TEAM_ID}	PASS	{meta:{}, count:1, tokens:[{id, name, team, expiresAt:null}]} - no token secret field
per-token field check	{teamId: TEAM_ID}	PASS	token entry keys are exactly id, name, team, expiresAt; token is absent
nonexistent team	{teamId:"doesnotexist"}	PASS	404 isError, {code:"not_found"}

Findings

• The tool passes the route response through unchanged: the tool output matched the raw GET /teams/:teamId/devices/provisioning response byte-for-byte for the same team.
• The summary view omits the token secret. The create route returns a token field, whereas each list entry exposes only id, name, team, and expiresAt, confirming the tool is safe to expose read-only.
• An unknown team surfaces a clean 404 rather than an empty list.

Conclusion

The single tool added in this PR verified against its description, including the secret-omission guarantee. No open defects.