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-mcp@docs/FEATURES.md
!product:aos@coilyco-flight-deck/ward-mcp@docs/ci.md
!product:repo-agentic-os@coilyco-flight-deck/ward-mcp@docs/ci.md
!product:repo-deploy@coilyco-flight-deck/ward-mcp@README.md
!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/DESIGN.md
!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/FEATURES.md
!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/chart.md
!product:repo-inbox@coilyco-flight-deck/ward-mcp@README.md
!product:repo-inbox@coilyco-flight-deck/ward-mcp@docs/DESIGN.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-mcp@docs/FEATURES.md</code> * <code>!product:aos@coilyco-flight-deck/ward-mcp@docs/ci.md</code> * <code>!product:repo-agentic-os@coilyco-flight-deck/ward-mcp@docs/ci.md</code> * <code>!product:repo-deploy@coilyco-flight-deck/ward-mcp@README.md</code> * <code>!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/DESIGN.md</code> * <code>!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/FEATURES.md</code> * <code>!product:repo-deploy@coilyco-flight-deck/ward-mcp@docs/chart.md</code> * <code>!product:repo-inbox@coilyco-flight-deck/ward-mcp@README.md</code> * <code>!product:repo-inbox@coilyco-flight-deck/ward-mcp@docs/DESIGN.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:41 +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 (9 finding(s)).

coilyco-ops closed this issue

2026-08-05 21:23:59 +00:00

coilyco-ops reopened this issue

2026-08-06 00:18:23 +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-14 05:40:48 +00:00

Author

Member

Assessed, not actioned - this one is not hand-fixable from inside this repo.

All nine findings are keyed to coilyco-flight-deck/**ward-mcp**@<path>, which is the pre-rename repo identity. The repo is mcp-beaver now. So the alias set is stale on top of whatever it was originally reporting, and the paths it names (README.md, docs/DESIGN.md, docs/FEATURES.md, docs/ci.md, docs/chart.md) have all been edited since - several by me today, in the #48, #49, #57, #59 and #61 work.

Two reasons to leave it alone rather than guess at it:

The issue body says it is maintained automatically by code-fleet-watch. Hand-editing it would be overwritten, and closing it would just be reopened on the next scan.
The scanner publishes aliases and paths only, never decoded terms. That is the right privacy posture, and it also means I cannot tell from this issue what any individual finding actually objects to. Acting on it from here would be guessing.

What would resolve it is a re-scan under the current repo name, which belongs to code-fleet-watch's own rollout rather than to this repo. If the findings survive that re-scan with mcp-beaver paths, they become actionable and I am happy to take them then.

Left open and untouched, consistent with its P4 label.

Assessed, not actioned - this one is not hand-fixable from inside this repo. All nine findings are keyed to `coilyco-flight-deck/**ward-mcp**@<path>`, which is the pre-rename repo identity. The repo is `mcp-beaver` now. So the alias set is stale on top of whatever it was originally reporting, and the paths it names (`README.md`, `docs/DESIGN.md`, `docs/FEATURES.md`, `docs/ci.md`, `docs/chart.md`) have all been edited since - several by me today, in the #48, #49, #57, #59 and #61 work. Two reasons to leave it alone rather than guess at it: 1. **The issue body says it is maintained automatically by code-fleet-watch.** Hand-editing it would be overwritten, and closing it would just be reopened on the next scan. 2. **The scanner publishes aliases and paths only, never decoded terms.** That is the right privacy posture, and it also means I cannot tell from this issue what any individual finding actually objects to. Acting on it from here would be guessing. What would resolve it is a re-scan under the current repo name, which belongs to code-fleet-watch's own rollout rather than to this repo. If the findings survive that re-scan with `mcp-beaver` paths, they become actionable and I am happy to take them then. Left open and untouched, consistent with its `P4` label.

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:41 +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:18 +00:00

Rows
Columns

code-fleet-watch: policy findings #37