integration-preflight notice fires on a plugin version-tag push, which involves no declared-vs-live infra #3

New Issue

2026-08-14T12:32:30+03:00

issuer-agent commented

2026-08-14 12:32:30 +03:00

In session oleks/2b0ac584 (2026-08-14) the fleet-integration:integration-preflight notice fired on git push -f origin v1.16.1 — a Claude Code plugin version tag in oleks/claude-plugin-plugin-publishing, classified as "rollout-shaped action (release tag push)".

That repo has no NixOS/fleet deployment, no HelmRelease, and no declared-vs-live configuration for the preflight to diff — the check it asks for has no target. The notice's stated rationale (declared vs LIVE reality, a successful-but-ineffective deploy) does not apply to publishing a plugin tag.

Suggested direction: exclude repos with no fleet/deploy surface, or narrow the tag-push matcher so plugin repos under ~/projects/claude-plugins/** don't match. Relevant because the notice's own text says it fires once per session and has been skipped four times across sessions — false positives on non-deploy repos are exactly what erodes an advisory guard's credibility. Related: hooks/rollout-preflight-notice.py is the hook in question, and its 31-assertion suite had no CI runner until this session wired one (oleks/claude-plugin-plugin-publishing#16).

Related, not duplicate: oleks/claude-plugin-fleet-integration#2 (closed 2026-08-14) tracked the OPPOSITE failure of this same skill — the preflight never firing when it should have (situation-shaped mandate, phrase-shaped trigger). This issue is the precision problem on the other side: it fires but on a target with nothing to check.

Found during a decision-flow session audit (session oleks/2b0ac584, 2026-08-14, grinding oleks/claude-plugin-plugin-publishing).

In session oleks/2b0ac584 (2026-08-14) the `fleet-integration:integration-preflight` notice fired on `git push -f origin v1.16.1` — a Claude Code plugin version tag in `oleks/claude-plugin-plugin-publishing`, classified as "rollout-shaped action (release tag push)". That repo has no NixOS/fleet deployment, no HelmRelease, and no declared-vs-live configuration for the preflight to diff — the check it asks for has no target. The notice's stated rationale (declared vs LIVE reality, a successful-but-ineffective deploy) does not apply to publishing a plugin tag. Suggested direction: exclude repos with no fleet/deploy surface, or narrow the tag-push matcher so plugin repos under `~/projects/claude-plugins/**` don't match. Relevant because the notice's own text says it fires once per session and has been skipped four times across sessions — false positives on non-deploy repos are exactly what erodes an advisory guard's credibility. Related: `hooks/rollout-preflight-notice.py` is the hook in question, and its 31-assertion suite had no CI runner until this session wired one (oleks/claude-plugin-plugin-publishing#16). **Related, not duplicate:** oleks/claude-plugin-fleet-integration#2 (closed 2026-08-14) tracked the OPPOSITE failure of this same skill — the preflight never firing when it should have (situation-shaped mandate, phrase-shaped trigger). This issue is the precision problem on the other side: it fires but on a target with nothing to check. Found during a decision-flow session audit (session oleks/2b0ac584, 2026-08-14, grinding oleks/claude-plugin-plugin-publishing).

oleks referenced this issue from a commit

2026-08-16 12:53:13 +03:00

ci(hooks-release): pin golang:1.26.4 so the bin/hooks diff gate compares like with like

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: oleks/claude-plugin-fleet-integration#3