[mellelieuwes]

Flux issue: https://app.basecamp.com/5734045/buckets/45557517/todos/10448800497

Problem

The CLI's AppSignal read commands (v0.6.0) don't work against flux-test or production:

• flux appsignal incidents list fails with failed to decode response: json: cannot unmarshal object into Go struct field IncidentsResponse.incidents of type []api.Incident.
• flux appsignal incidents get <N> prints an empty # Incident #N: / State:.
• flux appsignal resources prints nothing.

Cause

The CLI drifted. The server hasn't changed: since the AppSignal endpoints were added (eyra/flux c8aa577, 2026-02-05), each one wraps AppSignal's MCP text (Markdown) as content:

• GET …/appsignal/incidents, --type exception or anomaly: {"incidents": {"type": "exception", "content": "# Exception Incidents\n…"}}
• GET …/appsignal/incidents, all types (the default): {"incidents": {"exceptions": {…}, "anomalies": {…}}}
• GET …/appsignal/incidents/:number: {"number": 121, "content": "# Incident #121: ArgumentError\n…"}
• GET …/appsignal/resources: {"sections": ["users", …], "content": "# Application Resources\n…"}

The CLI's AppSignal commands (5910d69, 2026-06-17) were written against structured incidents and resources that no server version ever sent.

Fix (CLI only)

• The CLI decodes these four shapes and prints AppSignal's Markdown as is. Listings come exceptions first, and AppSignal's own "no incidents found" text comes through.
• --json:
  • incidents list prints [{"type","content"}, …];
  • incidents get prints {"number","content"};
  • resources prints {"sections","content"}.
• Any other response is an error, never an empty result: "unexpected incidents response", "unexpected incident response" or "unexpected resources response". That covers null, {}, a missing key or field, a listing without a type, and the old structured shapes.
• The skill's incidents get example now passes the number as an argument, as the command takes it.
• The server is unchanged, so this works with the flux-test and production servers that are deployed now. No release order is needed.

All commits are fix:. Merging into master makes tag.yml tag and release v0.6.1 (a patch release).

Tests and verification

• api: TestListIncidents, TestListIncidentsUnexpectedShape, TestGetIncident, TestGetAppSignalResources and TestAppSignalUnexpectedShapes (success and error cases).
• cmd: TestAppSignalIncidentsList and TestAppSignalIncidentsGetAndResources (text and --json).
• All tests use response shapes captured from eyra-flux-test on 2026-10-27. Run against master, the cmd tests fail: list with the decode error above, and get and resources with empty output.
• go test -race ./..., go vet ./... and go mod tidy -diff pass.
• A local build from this branch works against both environments:
  • flux-test (--app Flux/prod): incidents list (all, --type anomaly, --json), incidents get 121 and resources (--sections namespaces, --json).
  • production (--project next --app Next/next.eyra.co): incidents list, incidents get 1 and resources.

Not in this PR: the server's appsignal apps list keeps AppSignal's header and URL lines (Flux issue 10448845294).

Pre-reviewed by an AI agent (herdr-projects flux · t-0083, head 8a58d3b): fixed M1 (an unknown, null or missing incidents shape fails with ErrUnexpectedIncidents instead of printing "No incidents found") and L1 (error-case tests); the incidents get and resources delta had no findings.

🤖 Generated with Claude Code

_{Written by an AI agent (Claude Code · claude-opus-5-5, herdr-projects flux · t-0079).}

[JoeriDijkstra]

Review notes: https://app.basecamp.com/5734045/buckets/45557517/todos/10448800497#__recording_10450526375