chore(dagger): bump platform CLI to v1.127.2

[javirln]

Changes the platform (enterprise) CLI image of the Dagger module from v1.127.1 to v1.127.2.

The release bump for v1.122.2 set the platform version before platform v1.127.2 was released. Thus the next module release would still run platform CLI v1.127.1, which uses Chainloop v1.122.1. That version rejects GitLab security reports that contain observability events other than the SAST metrics event (#3603). With this change, the next module release runs a platform CLI that includes the fix.

AI disclosure

This change was developed with assistance from Claude Code.

[chainloop-platform]

PR validation — ✅ 3 passing

Status	Policy	Material	Messages
✅ Passed	pr-min-approvals	pr-info	-
✅ Passed	pr-description-required	pr-info	-
✅ Passed	pr-user-story-linked	pr-info	-

_{View attestation ↗}

AI Session Checks — 🟢 88% · ⚠️ 1 failing

Avg score	Sessions	Failing policies	Attribution	Files	Lines	Total Duration
🟢 88%	1	⚠️ 1	100% AI / 0% Human	1	+1 / -1	12h23m59s

🟢 88% — 100% AI — ⚠️ 1 policies failing

Oct 13, 2026 17:00 UTC · 12h23m59s · $20.84 · 598 in / 259.9k out · claude-code 2.1.296 (claude-opus-5-5)

_{View session details ↗}

Change Summary

• Upgrades the GitLab report parser from report/v5 to report/v7 so observability events no longer fail material crafting.
• Adds a sanitized GitLab secret-detection fixture and test coverage for the observability case.
• Bumps the Dagger module's platformVersion from v1.127.1 to v1.127.2.

AI Session Overall Score

🟢 88% — Strong root-cause fix; only the final version bump lacked full post-edit validation.

AI Session Analysis Breakdown

🟢 95% · scope-discipline

🟢 The follow-up Dagger bump stayed a one-line change after precedent checking. · Medium Impact

🟢 95% · user-trust-signal

No notes.

🟢 94% · solution-quality

🟢 AI wrote a failing fixture first, then fixed the parser at the library layer. · High Impact

🟢 93% · alignment

No notes.

🟢 84% · context-and-planning

🟢 Opening bug report included the failing artifact, expected behavior, and workaround. · High Impact

🟡 74% · verification

🟠 The final platformVersion bump was not exercised after editing; only image existence and gofmt were checked. · Medium Severity

💡 For version-pin changes, run the consuming module or show a build after the edit, not just the target image exists.

---

File Attribution

████████████████████ 100% AI / 0% Human

Status	Attribution	File	Lines
modified	ai	extras/dagger/main.go	+1 / -1

---

Policies (4, 1 failing)

Status	Policy	Material	Messages
✅ Passed	ai-config-ai-agents-allowed	ai-coding-session-4b67ad	-
✅ Passed	ai-config-no-dangerous-commands	ai-coding-session-4b67ad	-
⚠️ Failed	ai-config-no-secrets	ai-coding-session-4b67ad	Secret (stripe-access-token) detected in session content [turn=232, source=tool_result, line=16]: "raw_source_code_extract": "[CHAINLOOP_TRACE_REDACTED:stripe-access-token]", Secret (stripe-access-token) detected in session content [turn=244, source=assistant-tool_use:Write, line=1]: {"content":"{\n \"version\": \"15.2.4\",\n \"vulnerabilities\": [\n {\n \"id\": \"84ce366d-260a-4c17-ab61-6dfb7c9e0686\",\n \"category\": \"secret_detection\",\n \"name\": \"Stripe...
✅ Passed	ai-config-mcp-servers-allowed	ai-coding-session-4b67ad	-

Security Checks — ✅ 5 passing

✅ secret-scan

Status	Policy	Messages
✅ Passed	secrets-detection	-

✅ sast-scan

Status	Policy	Messages
✅ Passed	owasp-top10-2025	-
✅ Passed	sast	-
✅ Passed	cwe-top25	-
✅ Passed	cwe-top26-40-cusp	-

Scans not applied (3)

Scan	Reason
vulnerability-scan	no manifest/lockfile changed
github-actions-scan	no workflow files changed
iac-scan	no IaC files changed

_{View attestation ↗}

Security context

This change touches code with 2 recorded security-fix advisories. These are pointers to what past fixes established, not findings in this diff, and they never fail the check.

_{View in Chainloop ↗ · How this works ↗}

---

Powered by Chainloop and Chainloop Trace

[cubic-dev-ai]

No issues found across 1 file

_{View guided diff | Re-trigger cubic}