feat: mark Creed outputs as generated (COD-452) - #50
Conversation
🤖 Automated Review PanelReviewer AInitial review identified stale/disabled metadata coverage, attribution after per-file output failure, missing dogfood output, then final review identified CRLF preservation and literal Git-attribute path escaping. All findings were addressed before this PR: generated blocks are CRLF-safe, preserve user content under uniform CRLF, escape literal paths, are only emitted after successful content emission, and dogfood output plus regression coverage are included. Reviewer BIndependently identified the same CRLF-preservation and path-pattern correctness risks. The final implementation preserves uniform CRLF content, rejects mixed endings rather than rewriting user bytes, and escapes attribute patterns so whitespace/glob characters cannot broaden rules. Validation
|
Auto-Merge GateConfidence: 0.91 The implementation directly satisfies COD-452: it deterministically emits target-owned Checks observed: CI / Test, Lint, Creed context drift, and Secret Scan — all completed successfully. Scope limits: eight files, confined to generated attribution support and its tests; no credentials, deployment, destructive behavior, or manual-review marker detected. |
Summary
.gitattributesblocks marking Creed-rendered outputs aslinguist-generatedValidation
go generate ./... && git diff --exit-codego build ./...go test -race -count=1 ./...go vet ./...test -z "$(gofmt -l .)"scripts/check-generated.shCloses COD-452.