This repo has no pre-commit config, and adopting the suite is not a drop-in #87
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-proxy#87
Loading…
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?
agent-proxyships no.pre-commit-config.yaml. Runningpre-commit run --all-fileshere fails withInvalidConfigError: .pre-commit-config.yaml is not a file, so none of the catalog validators have ever run against this tree.Why it was missed
agentic-os/scripts/apply-agentic-os-hooks.pydrives off "every git working tree under~/projects/<org>/*". This repository is not in the on-disk residency set, so the rollout has never seen it. Tracked separately at coilyco-flight-deck/agentic-os.ward-mcpis missing it for the same reason.What adopting it costs
I generated the config with the owning tool (
--rev aos-precommit-v0.18.0) against a scratch copy and ran the suite. 15 hooks pass, 11 fail. Nothing below is committed.Mechanical, minutes each
context-load-points- add aCLAUDE.mdcontaining exactly@AGENTS.md. One file.catalog-block-present-.ward/ward.yamlneeds a top-levelcatalog:block.catalog-trifecta-README.mdneeds a## See alsosection linkingAGENTS.md,docs/FEATURES.md, and.ward/ward.yaml.source-doc-refs-.ward/ward.yaml:3points atdocs/ward-yaml.md, which does not exist.trailing-whitespaceandend-of-file-fixer- auto-fixed on run.Likely repo config rather than defects
typos- flagsserinsideser8, our own host name. Needs an allowlist, not a correction. About 50 output lines, mostly this.actionlint- rejectsruns-on: docker, which is the self-hosted Forgejo runner label. Needs an actionlint config, not a workflow change.Real work
code-comments- 97 output lines, dominated by.ward/ward.yamlcomments sitting below the top header block.catalog-doc-sizeanddocumentation-layout-docs/architecture-v2.mdis 10839 chars and 180 lines against caps of 4000 and 80.docs/FEATURES.mdis 8181 chars.docs/ROADMAP.mdis 5810. Splitting these is editorial work, andarchitecture-v2.mdis load-bearing for the v2 migration.actions-run-one-line- twopython3 -cbodies inlined in.forgejo/workflows/ci.ymlneed extracting into tracked scripts.Worth knowing before picking a rev
deployis still pinned to the olderv0.102.0block, which carries neithertyposnoractionlintnoractions-run-one-line. Adoptingaos-precommit-v0.18.0here would makeagent-proxythe first repo on the newer set, so it would absorb new-hook friction that is not specific to this repository. Pinning to the same rev the rest of the fleet runs is a smaller first step.Suggested order
Land the config with the doc-size and code-comment hooks temporarily excluded, fix the mechanical items and the two config gaps in that same change, then remove the exclusions as the docs get split. That keeps
maingreen throughout instead of landing a repo that fails its own gate.