fix(compliance): remove tab character from runner-output-contract.yaml (backport 3.1.x) - #6065
Conversation
adcontextprotocol#6042) A literal tab at line 303 (a pure comment line) makes the file unparseable by strict YAML parsers — tabs cannot start a token — so consumers of the packaged 3.1.4/3.1.5 compliance caches fail to load the runner output contract. Replace the leading tab with spaces; comment text and semantic content unchanged. Verified: yaml.safe_load parses the file clean after the change, and `grep -rP '^\t' static/compliance/source/` reports zero remaining tab-leading lines (this was the only occurrence). Refs adcontextprotocol#6038 Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
![aao-secretariat[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
|
Gentle nudge for prioritization: So new 3.1.x caches are being cut without this backport, and platform engines that strict-parse the cache keep degrading. Merging this before the next 3.1.x cache cut would get the fix (already on main via #6042) into the published caches. Happy to rebase if anything's needed on my side. |
|
Confirming status after @fgranata's note: CI: all 9 checks green (CodeQL, TypeScript Build, Server integration tests, changeset, PR title, code_review, GitGuardian, Analyze). One blocker: the Argus automated review timed out and posted a warning that a human reviewer should take this PR before merge. That's the only thing between this and landing. Escalated impact: the PR description cited v3.1.6 as the last affected release. @fgranata's comment confirms Ready for a quick human review pass — the diff is +11/-1, one file. Generated by Claude Code |
2 participants
Backport of #6042 to the
3.1.xline, per the triage recipe on #6038 — cherry-pick of the merged main commit, no conflicts.Note: v3.1.6 was cut before #6042 merged on main, so the shipped 3.1.6 cache still carries the malformed
runner-output-contract.yaml; this backport is what gets the fix into the next 3.1.x cache release for platform-engine consumers.Refs #6038
🤖 Generated with Claude Code