finding (audit): 2026-05-13 - audit finding walkthrough prints a agentic-os-kai path for findings that actually live under coily #40
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?
Originally filed by @coilysiren on 2026-05-18T03:42:45Z - https://github.com/coilysiren/coily/issues/217
Migrated from
coily-audit-meta/findings/2026-05-13-audit-finding-walkthrough-emits-wrong-skills-path.mdon 2026-05-17 as part of coilysiren/coily#215. Original file preserved in git history; see deletion commit on coilysiren/coily#215.2026-05-13 - audit finding walkthrough prints a agentic-os-kai path for findings that actually live under coily
What was observed
Running
coily --commit-scope=/home/kai/projects/coilysiren/agentic-os-kai audit finding --id 019e23b4-73d9-7829-be9f-dd2529090b90 --slug ops-aws-passthrough-mangles-query-output-flags(audit row019e23bb-9a70-7cc4-bdfe-fa2b60f5dc84, ts 1778715957, verbaudit.finding) emitted a Step 3 instruction with this path:The
coily-*-metaskill directories do not exist underagentic-os-kai/.claude/skills/. They live undercoily/.claude/skills/. The "References" block at the end of the walkthrough reinforces the same wrong location forcoily-meta-improvement/SKILL.mdandcoily-skill-authoring/SKILL.md.The agent following the walkthrough caught this on contact (the target directory was missing, ran a
findover/home/kai/projects/coilysirento locate the realcoily-ops-aws-meta, then wrote the finding to the correct path undercoily/). The walkthrough did not catch itself.Why it slipped
The walkthrough copy was probably authored when the meta skills lived (or were planned to live) under
agentic-os-kai, and the path string was hardcoded into the walkthrough emitter. When the meta skills landed undercoily/.claude/skills/instead (where they sit alongside the source they document), the walkthrough emitter wasn't updated. Nothing in the build verifies the printed path resolves on disk before shipping a coily release.This is a class of drift the audit-finding loop is uniquely vulnerable to. The walkthrough is the onboarding doc for new agents writing findings. If it points to a wrong path and an agent trusts it verbatim, the finding lands in an orphan tree under
agentic-os-kai/.claude/skills/coily-<area>-meta/findings/that the meta-improvement loop never reads from. The bad outcome is a finding that quietly disappears, not a loud failure.Rule it produced
Anti-signal candidate (data only, not promoted): "the path printed by
coily audit finding's walkthrough is the canonical location to write the finding." Today it is not. Verify the directory exists undercoily/.claude/skills/coily-<area>-meta/findings/before writing. Forward action filed at coily#148.