agent-zero-fix-summary.prose.md (added in 143dd3f) has no YAML frontmatter. CI validate scans every *.prose.md and has failed on the last 3 master pushes (Gitea runs 226/227/228) because of this one file.
The file is a dated session fix-log, not a contract. The durable operational knowledge already lives in agent-zero-openrouter-key.prose.md (kind: function), which the summary itself references. Renaming to .md takes it out of the contract scan path (validate/lint only process *.prose.md) and matches repo-root docs precedent (cron-prompts-review.md, AGENTS.md).
Local repro of CI validate loop: PASS (36 files, 0 failures)
bash scripts/prose-lint.sh: PASS at baseline 15 warnings — no new warnings
Intentionally NOT changed
No content edits to the summary (it is a historical log)
No other contracts touched
No frontmatter retrofitted onto non-contract docs
Agent Zero contract (agent-zero-openrouter-key.prose.md) unchanged — already valid
Fixes CI runs 226/227/228 (validate job failing on master pushes).
## Summary
`agent-zero-fix-summary.prose.md` (added in 143dd3f) has **no YAML frontmatter**. CI `validate` scans every `*.prose.md` and has failed on the last 3 master pushes (Gitea runs 226/227/228) because of this one file.
The file is a dated session fix-log, not a contract. The durable operational knowledge already lives in `agent-zero-openrouter-key.prose.md` (kind: function), which the summary itself references. Renaming to `.md` takes it out of the contract scan path (`validate`/`lint` only process `*.prose.md`) and matches repo-root docs precedent (`cron-prompts-review.md`, `AGENTS.md`).
## Changes
| File | Change |
|------|--------|
| agent-zero-fix-summary.prose.md → agent-zero-fix-summary.md | rename (100%, no content change) |
## Verified
- Local repro of CI validate loop: **PASS** (36 files, 0 failures)
- `bash scripts/prose-lint.sh`: PASS at baseline 15 warnings — **no new warnings**
## Intentionally NOT changed
- No content edits to the summary (it is a historical log)
- No other contracts touched
- No frontmatter retrofitted onto non-contract docs
- Agent Zero contract (`agent-zero-openrouter-key.prose.md`) unchanged — already valid
Fixes CI runs 226/227/228 (validate job failing on master pushes).
agent-zero-fix-summary.prose.md has no YAML frontmatter (kind/name/description),
so CI validate fails on every master push that touches it (runs 226-228).
It is a dated session fix-log, not a contract - the durable knowledge already
lives in agent-zero-openrouter-key.prose.md (kind: function, referenced from
the summary). Rename to .md so validate/lint (which scan only *.prose.md)
stop rejecting master; matches repo root docs like cron-prompts-review.md.
Verified live: local validate repro PASS (36 files), prose-lint PASS at
baseline 15 warnings, no new warnings. Intentionally NOT changed: no content
edits, no other files, no contract frontmatter added to non-contract docs.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
agent-zero-fix-summary.prose.md(added in143dd3f) has no YAML frontmatter. CIvalidatescans every*.prose.mdand has failed on the last 3 master pushes (Gitea runs 226/227/228) because of this one file.The file is a dated session fix-log, not a contract. The durable operational knowledge already lives in
agent-zero-openrouter-key.prose.md(kind: function), which the summary itself references. Renaming to.mdtakes it out of the contract scan path (validate/lintonly process*.prose.md) and matches repo-root docs precedent (cron-prompts-review.md,AGENTS.md).Changes
Verified
bash scripts/prose-lint.sh: PASS at baseline 15 warnings — no new warningsIntentionally NOT changed
agent-zero-openrouter-key.prose.md) unchanged — already validFixes CI runs 226/227/228 (validate job failing on master pushes).