cli-guard <-> ward dependency cycle: cut one direction (leak-guard cat-3) #139

New issue

Open

opened 2026-06-12 08:15:42 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-12 08:15:42 +00:00

Owner

leak-guard (agentic-os#208) category-3 example: cli-guard and ward reference
each other, so the dependency edge is a cycle. The cli-guard-ward-cycle rule
is configured to ban the cli-guard -> ward direction, but a demo run flags many
real references, mostly in cli/**/*_test.go plus AGENTS.md and .agentic-os.toml.

Those look like genuine ward-interop tests, not a stray back-reference, so the
direction to cut needs a domain decision:

Is the true layering ward -> cli-guard (cli-guard lower), making the test-side
ward references the ones to remove / move to ward's repo?
Or are these legitimate and the rule should be dropped / inverted?

Resolve the direction, clean the chosen side, then enable leak-guard here via the
ansible rollout. Context: coilysiren/inbox#95.

leak-guard (agentic-os#208) category-3 example: cli-guard and ward reference each other, so the dependency edge is a cycle. The `cli-guard-ward-cycle` rule is configured to ban the cli-guard -> ward direction, but a demo run flags many real references, mostly in `cli/**/*_test.go` plus AGENTS.md and .agentic-os.toml. Those look like genuine ward-interop tests, not a stray back-reference, so the direction to cut needs a domain decision: - Is the true layering ward -> cli-guard (cli-guard lower), making the test-side ward references the ones to remove / move to ward's repo? - Or are these legitimate and the rule should be dropped / inverted? Resolve the direction, clean the chosen side, then enable leak-guard here via the ansible rollout. Context: coilysiren/inbox#95.

coilysiren added the

label

2026-06-17 07:04:40 +00:00

coilysiren added

and removed

labels

2026-06-17 08:39:29 +00:00

coilysiren added

consult

and removed

labels

2026-06-18 06:17:27 +00:00