code-fleet-watch: policy findings

coilyco-ops commented

2026-07-29 03:23:55 +00:00

Member

This issue is maintained automatically by code-fleet-watch.

Current product-policy findings:

!product:aos@coilyco-flight-deck/ward@cmd/ward/agent_release_transaction.go
!product:aos@coilyco-flight-deck/ward@docs/agent-release-transaction.md
!product:aos@coilyco-flight-deck/ward@scripts/release_contract_test.go
!product:repo-coilysiren@coilyco-flight-deck/ward@cmd/ward/git_clone.go
!product:repo-eco-ops@coilyco-flight-deck/ward@cmd/ward/atlas_catalog_graph.json
!product:repo-homebrew-tap@coilyco-flight-deck/ward@AGENTS.md
!product:repo-homebrew-tap@coilyco-flight-deck/ward@README.md
!product:repo-infrastructure@coilyco-flight-deck/ward@cmd/ward/git_clone.go
!product:repo-scoop-bucket@coilyco-flight-deck/ward@README.md

The scanner publishes aliases and paths only. It never writes decoded terms or matching content to Forgejo.

This issue is maintained automatically by code-fleet-watch. Current product-policy findings: * <code>!product:aos@coilyco-flight-deck/ward@cmd/ward/agent_release_transaction.go</code> * <code>!product:aos@coilyco-flight-deck/ward@docs/agent-release-transaction.md</code> * <code>!product:aos@coilyco-flight-deck/ward@scripts/release_contract_test.go</code> * <code>!product:repo-coilysiren@coilyco-flight-deck/ward@cmd/ward/git_clone.go</code> * <code>!product:repo-eco-ops@coilyco-flight-deck/ward@cmd/ward/atlas_catalog_graph.json</code> * <code>!product:repo-homebrew-tap@coilyco-flight-deck/ward@AGENTS.md</code> * <code>!product:repo-homebrew-tap@coilyco-flight-deck/ward@README.md</code> * <code>!product:repo-infrastructure@coilyco-flight-deck/ward@cmd/ward/git_clone.go</code> * <code>!product:repo-scoop-bucket@coilyco-flight-deck/ward@README.md</code> The scanner publishes aliases and paths only. It never writes decoded terms or matching content to Forgejo.

coilyco-ops referenced this issue from coilyco-flight-deck/infrastructure

2026-07-29 03:26:38 +00:00

Deploy a read-only code-fleet-watch k3s CronJob #668

coilyco-ops added the

labels

2026-07-29 03:47:39 +00:00

coilyco-ops closed this issue

2026-07-29 06:04:35 +00:00

coilyco-ops reopened this issue

2026-07-30 00:17:49 +00:00

coilyco-ops commented

2026-07-30 00:17:49 +00:00

Author

Member

code-fleet-watch detected a product-policy regression.

coilyco-ops commented

2026-07-30 17:37:08 +00:00

Author

Member

code-fleet-watch refreshed the current product-policy inventory (40 finding(s)).

coilyco-ops commented

2026-07-31 08:29:07 +00:00

Author

Member

Closing as absorbed by the headless product-boundary work in #1622. That issue owns removing AOS and AOSguard from Ward runtime code, shipped prompts, product documentation, tests, and examples. The scanner can reopen or refresh a finding if residue remains after #1622 lands.

coilyco-ops commented

2026-07-31 08:35:24 +00:00

Author

Member

Correction: reopened and restored to its prior triage state. The earlier closure was premature because Kai asked to review consult and interactive issues together before changing their disposition.

coilyco-ops commented

2026-07-31 09:25:31 +00:00

Author

Member

Closing as duplicate automated inventory during the Ward v1 seal. Actionable product-boundary work is owned by #1622, #1495, #1528, #1623, and #1624. The scanner may publish fresh evidence if violations remain after those headless issues land.

coilyco-ops closed this issue

2026-07-31 09:25:36 +00:00

coilyco-ops reopened this issue

2026-08-01 00:17:56 +00:00

coilyco-ops commented

2026-08-01 00:17:56 +00:00

Author

Member

code-fleet-watch detected a product-policy regression.

coilyco-ops commented

2026-08-05 09:48:55 +00:00

Author

Member

Decision resolved by Kai on 2026-08-05.

This issue is a generated product-policy sentinel, not an implementation target.

Never dispatch an agent directly against #1616.
code-fleet-watch owns and refreshes the issue body.
While findings remain, keep the issue open at P4 with no workflow label.
Resolve findings through their owning issues, currently #1622, #1495, #1528, #1623, and #1624.
Close the sentinel only when its generated inventory reaches zero.
A later genuine regression may reopen or refresh it.

This decision clears the consult gate without treating derived scanner output as an independent work item.

Decision resolved by Kai on 2026-08-05. This issue is a generated product-policy sentinel, not an implementation target. * Never dispatch an agent directly against #1616. * code-fleet-watch owns and refreshes the issue body. * While findings remain, keep the issue open at P4 with no workflow label. * Resolve findings through their owning issues, currently #1622, #1495, #1528, #1623, and #1624. * Close the sentinel only when its generated inventory reaches zero. * A later genuine regression may reopen or refresh it. This decision clears the consult gate without treating derived scanner output as an independent work item.

coilyco-ops removed the

autonomy

async-consult

label

2026-08-05 09:48:59 +00:00

coilyco-ops referenced this issue

2026-08-05 09:59:53 +00:00

Make the shipped Ward product AOS-opaque #1622

coilyco-ops added the

autonomy

async-consult

label

2026-08-05 10:26:08 +00:00

coilyco-ops closed this issue

2026-08-05 21:22:08 +00:00

coilyco-ops reopened this issue

2026-08-06 00:18:22 +00:00

coilyco-ops commented

2026-08-06 00:18:23 +00:00

Author

Member

code-fleet-watch detected a product-policy regression.

coilyco-ops commented

2026-08-07 00:18:06 +00:00

Author

Member

code-fleet-watch refreshed the current product-policy inventory (9 finding(s)).

coilyco-ops referenced this issue from coilyco-flight-deck/infrastructure

2026-08-14 06:40:46 +00:00

Retire code-fleet-watch #830

coilyco-ops commented

2026-08-14 06:41:32 +00:00

Author

Member

code-fleet-watch is retired. See coilyco-flight-deck/infrastructure#830.

No sweep will refresh this issue again, so it is closed as unmaintained rather than resolved. The findings listed above were never reviewed and their disposition is unknown. Anyone who wants them addressed should open a fresh issue with the specific claim, since the alias-only format above is not readable without the retired denylist.

code-fleet-watch is retired. See coilyco-flight-deck/infrastructure#830. No sweep will refresh this issue again, so it is closed as unmaintained rather than resolved. The findings listed above were never reviewed and their disposition is unknown. Anyone who wants them addressed should open a fresh issue with the specific claim, since the alias-only format above is not readable without the retired denylist.

coilyco-ops closed this issue

2026-08-14 06:42:02 +00:00

Rows
Columns

code-fleet-watch: policy findings #1616