Finding
maintenance_notes.txt (261 lines at repo root) contains critical, action-required operational knowledge for maintainers:
- When Fedora releases go EOL,
FEDORA_ATOMIC_FALLBACK_TAG must be updated in atomic_image_builder.py.
- Workflow patcher helpers (
patch_workflow_signing_steps, ensure_workflow_job_env_entries, patch_container_workflow, patch_bluebuild_workflow) have strict indentation and anchor regex sensitivity, silently returning text unchanged if template snapshots diverge.
- Containerfile-method image identity conventions with
image-template.env (since ublue-os/image-template revision a18ae9b5).
However, maintenance_notes.txt is not referenced or linked anywhere in maintainer_docs/MAINTAINER.md, CONTRIBUTING.md, or README.md. It is only mentioned in inline source comments within atomic_image_builder.py and Containerfile. A maintainer reading MAINTAINER.md has no signposted path to discover these notes.
Steps to Reproduce / Evidence
- Search for references to
maintenance_notes across documentation:
grep -rn "maintenance_notes" README.md CONTRIBUTING.md maintainer_docs/ docs/
Yields 0 results.
- Check existing references across the repository:
grep -rn "maintenance_notes" .
# Only matches inline comments in Containerfile and atomic_image_builder.py
maintainer_docs/MAINTAINER.md defines a dedicated ## Traps section (line 271) and ## Reading the weekly audit section without referencing maintenance_notes.txt.
Recommendation
Add a reference to maintenance_notes.txt in maintainer_docs/MAINTAINER.md under ## Traps (or a 'See also' section) summarizing the key operational items it covers (Fedora fallback tag EOL bumps, patcher indentation sensitivity, and template identity handling).
Filed by scanner agent (ACMM L4 — issues-only mode)
🐝 Hive Agent: scanner | Instance: hive-wild-mole | SHA: fee4d89
— hive: agent=scanner backend=agy model=gemini-3.7-flash-high effort=low agy=1.1.19
Finding
maintenance_notes.txt(261 lines at repo root) contains critical, action-required operational knowledge for maintainers:FEDORA_ATOMIC_FALLBACK_TAGmust be updated inatomic_image_builder.py.patch_workflow_signing_steps,ensure_workflow_job_env_entries,patch_container_workflow,patch_bluebuild_workflow) have strict indentation and anchor regex sensitivity, silently returning text unchanged if template snapshots diverge.image-template.env(since ublue-os/image-template revisiona18ae9b5).However,
maintenance_notes.txtis not referenced or linked anywhere inmaintainer_docs/MAINTAINER.md,CONTRIBUTING.md, orREADME.md. It is only mentioned in inline source comments withinatomic_image_builder.pyandContainerfile. A maintainer readingMAINTAINER.mdhas no signposted path to discover these notes.Steps to Reproduce / Evidence
maintenance_notesacross documentation:grep -rn "maintenance_notes" README.md CONTRIBUTING.md maintainer_docs/ docs/Yields 0 results.
maintainer_docs/MAINTAINER.mddefines a dedicated## Trapssection (line 271) and## Reading the weekly auditsection without referencingmaintenance_notes.txt.Recommendation
Add a reference to
maintenance_notes.txtinmaintainer_docs/MAINTAINER.mdunder## Traps(or a 'See also' section) summarizing the key operational items it covers (Fedora fallback tag EOL bumps, patcher indentation sensitivity, and template identity handling).Filed by scanner agent (ACMM L4 — issues-only mode)
🐝 Hive Agent:
scanner| Instance:hive-wild-mole| SHA:fee4d89— hive: agent=scanner backend=agy model=gemini-3.7-flash-high effort=low agy=1.1.19