[kwent]

Why

Ticket: IR-6585

What changed

N/A

Proof

Verified at 0839c603dbed: no harness test run at HEAD, lint passed, 0/4 criteria proved at HEAD (4 awaiting re-proof), council approved · proofs · Soil lane

Criteria at 0839c603dbed, each on what the harness ran or captured:

• ✗ AC1 rootly incidents create --title=... --services=a,b --types=c sends service_ids and incident_type_i… — not proved: the evidence judge found the harness output does not show it: The proofs do not address this criterion at all.
• ✗ AC2 rootly incidents update <id> --services=... --types=... sends them only when the flag is passed an… — not proved: the evidence judge found the harness output does not show it: The proofs do not address this criterion at all.
• ✗ AC3 README documents --services, --types and the other association flags from Add incident association flags #55 on incidents create/up… — not proved: the evidence judge found the harness output does not show it: The proofs do not address this criterion at all.
• ✗ AC4 No code changes; update.go untouched; PR body states the flags shipped in Add incident association flags #55 and this PR only adds … — not proved: the evidence judge found the harness output does not show it: Artifact 1 only shows go vet passing for internal/api and internal/cmd/incidents (exit=0), which says nothing about whether code changed, whether update.go is untouched, or what the PR body states.

Existing tests for create/update associations and INC-123 normalisation pass; diff is README.md only; --help lists every flag the README names:

--- PASS: TestRunUpdateCanClearAssociations
--- PASS: TestCreateIncident
--- PASS: TestUpdateIncident
--- PASS: TestNormalizeIncidentID
git diff --name-only master...HEAD: README.md

References: IR-6824, IR-6586, IR-6584, IR-5478, IR-6588, IR-6585, IR-5846

Risk: low

Overrides

• context at 57534c36ca, by the operator: the finding is wrong for this lane. The six URLs are separate tickets, each with its own lane and PR (IR-6824 → rootlyhq/rootly#26389, IR-5846 → rootlyhq/rootly#26390, IR-6586 → [IR-6586] feat(02-03): warn when resolving an incident from the CLI #83, IR-6584 → ir-6584-304657; IR-5478 and IR-6588 were already done upstream). The human asked for one — overrode: these parts of the ask have no acceptance criterion: "https://linear.app/rootly/issue/IR-6824/mcp-claude-desktop-and-claude-code-sdk-cannot-connect-the-mcp-server"; "https://linear.app/rootly/issue/IR-6586/cli-add-status-page-commands-incidents-update-statusresolved-leaves"; "https://linear.app/root
• verify at 26ecc5e1f9, by the operator: this check doesn't apply. The change is README.md only (+23 lines, no Go code), documenting flags that already shipped with tests in rootly-cli#55. There is no behaviour for a harness test or prove_fix to show. The run captured at HEAD 26ecc5e (environment exec log) shows the diff is README-only and — overrode: acceptance criterion AC1 is not proved: it cites only files the lane wrote (tmp/soil/proofs/verify.txt, tmp/soil/environment/exec-mw2mjiw0-e02499026a21.log), not anything the harness ran or captured. A criterion is proved only by something the harness ran or captured at HEAD — a harness test run (it; acceptance criterion AC2 is not proved: it cites only files the lane wrote (tmp/soil/proofs/verify
• verify at 0839c603db, by the operator: this re-applies my 26ecc5e override at HEAD 0839c60. The change is still README.md only, with no Go code, documenting association flags that shipped with tests in rootly-cli#55. No harness test or prove_fix can go red before and green after for a docs change. go vet passes at HEAD and the existing c — overrode: Verify proof missing: acceptance criteria proved at HEAD (AC1, AC2, AC3, AC4 not yet)

Full run report: council review, criteria, every capture and output.

[soil-cloud]

Soil is watching this PR. It acts on CodeFlow's review of the latest commit, review comments and change requests, red CI (after checking master and re-running once for flakes) and merge conflicts: one commit per fix, with a reply in each thread it handles. It skips comments containing "(aside)".
The PR's owner can comment stop (or stop: <reason>) to have Soil close this PR.

• Disable Soil's automatic review, CI and merge-conflict monitoring

[greptile-apps]

Confidence Score: 5/5

[Low impact] This documentation-only PR appears safe to merge.

Summary

Updates README.md to document existing incident association flags.

• Incident commands now document how to link related records.

No actionable issues found. The documented flags match the command code and existing tests. Tests were inspected, not run.

_{Reviews (1) · Last reviewed commit: "docs: reference rootly pulse create --se..." · Reviewed by Greptile}