Clean up documentation-layout / catalog-trifecta violations on agentic-os hooks #11
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/galaxy-gen#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The agentic-os pre-commit hooks (currently pinned to v0.3.0 after coilysiren/galaxy-gen#10) ship
documentation-layoutandcatalog-trifectavalidators that fail on long-standing files in this repo. They are bypassed today viaSKIP=documentation-layout,catalog-trifectaon commits that touch unrelated files.Violations
documentation-layout(26 entries):readme.md(wrong-case filename + over 80 lines / 4000 chars)development.md(top-level non-allowlisted filename)pkg/README.md(gitignored wasm-pack artifact, also over cap)docs/FEATURES.md(over 4000 chars)docs/perf-rewrite.md(1162 lines / 36k chars - very over)AGENTS.md(86 lines / 4813 chars).agents/skills/coding-galaxy-gen-{astrophysics,cosmology,references}/SKILL.mdandreferences/wikipedia-concepts.md(over caps).agents/skills/tooling-skill-authoring/SKILL.mdandreferences/handbook.md(over caps)catalog-trifecta(1 entry):AGENTS.mdmissing required H2 sections (Scope / Project shape / Repo boundaries / Validation / Safety / Cross-repo contracts / Release / Agent rules)Proposal
Pick one:
readme.md→README.md, movedevelopment.md→docs/, split oversized SKILL.md / handbook / perf-rewrite into smaller files, restructure AGENTS.md to the trifecta shape..agentic-os.tomlwithexcludes/enabledfor the legitimately-large or out-of-shape paths. Requires bumping the pin to v0.4.0+ (whereagentic_os.configships, per agentic-os@68ff09e).Option 2 is cheaper and matches the upstream escape hatch. Option 1 is more correct but invasive (the perf-rewrite session journal is a deliberate long-form artifact).
See also
Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.