fix(harbor-dev): gate teardown on deletionPolicy, verify the right Kustomization (PLT-1216)

[bdchatham]

The ticket premise is false. PLT-1216 says teardown leaks disks because a prune option is missing. Prune is already enabled — platform/clusters/harbor/engineers/base/sync.yaml:14, in the shared base that renders all nine engineer reconcilers. It works correctly for everything Flux owns. This PR changes no Flux YAML, no prune setting, and nothing in the platform repo.

What actually leaks the disks: SeiNetwork.spec.deletionPolicy defaults to Retain. On deletion the reconciler deliberately strips the owner reference from the child SeiNodes rather than deleting them (sei-k8s-controller internal/controller/seinetwork/controller.go:135-143). The orphaned validators keep running, each still holding its PVC and its EBS volume. Flux prune cannot reach them — the controller created them, so they were never in Flux's inventory — and garbage collection has no owner reference left to follow. Storage-class reclaim is irrelevant, because reclaim only fires on a PVC that actually gets deleted. gp3-10k-750 and gp3 are already reclaimPolicy: Delete; nothing needs changing there.

This PR does not stop the leak. It is docs/skills only. The load-bearing fix is benchmark SeiNetworks carrying deletionPolicy: Delete, tracked separately. What this PR does is stop the harbor-dev skill from reporting a successful teardown while disks are still running, and give the operator the procedure that prevents the orphaning in the first place.

What this fixes

1. Wrong reconcile target. Teardown verification reconciled flux-system and read its lastAppliedRevision. That root Kustomization tracks sei-protocol/platform at clusters/harbor — not harbor-engineering-workspace. So teardown verified a reconciler that never touched the engineer's change and reported success regardless. Workspace merges now target Flux Kustomization <alias> in namespace eng-<alias> (verified in-repo: references/onboarding-pr.md:110, references/cluster-inspection-recipes.md recipe #8). flux-system stays correct for platform-repo merges (onboarding), and the split is now a table rather than a single command.

2. No resource-disappearance check. A successful reconcile only means Flux issued the deletes. Added an explicit poll of the SeiNetwork/SeiNodes/PVCs on a bounded budget, with the caveat stated: deletion is asynchronous and sei.io/seinode-finalizer holds a SeiNode until the controller releases its PVC. An object still Terminating past the budget is a reportable finding — stripping the finalizer to make the check pass is exactly how a stuck teardown becomes a leaked disk.

3. The deletionPolicy: Retain trap was undocumented. Now a guardrail, a procedure step, a halt condition, and a section of the new reference. deletionPolicy is mutable (no CEL XValidation, no webhook — SeiNetworkSpec carries exactly three immutability rules: spec.genesis, spec.replicas, spec.dataVolume), so an operator can patch a live SeiNetwork to Delete. The ordering is the load-bearing part: the policy change must land in git and reconcile before the removal merges. A bare kubectl patch on a Flux-owned SeiNetwork is drift — the rendered manifest normally carries the server-defaulted Retain, so Flux owns the field and reverts the patch on its next pass, typically while the removal PR is in review. And once a Retain deletion has stripped the owner references and removed the parent, nothing restores the cascade at all.

4. No "destroy my namespace" procedure. Added, and honest about the boundary: a workspace PR removes the engineer's workloads only. The Namespace object, the three ServiceAccounts, the RBAC, and the Flux Kustomization itself are platform-owned and stay. So does anything created outside git — an escape-hatch apply, or an orphan from an earlier Retain teardown.

5. Teardown skipped the PR contract. Spinup goes through a PR; teardown now does too — branch, commit, gh pr create, merge, reconcile, verify.

6. No cleanup path for already-leaked resources. Added. Orphan signature: sei.io/role=validator and no ownerReferences and no live parent. Absence of owner references alone is not the signal — a follower from seictl node apply is a top-level object and legitimately has none. Cleanup is kubectl delete seinode on the confirmed orphan: its finalizer deletes the PVC and the Delete reclaim policy releases the volume. Disk signals are candidates, never verdicts — EC2 available means unattached, not unowned, and a volume backing a live Bound PVC reads available the moment its workload stops. Ownership resolves by walking volume ID → PV (spec.csi.volumeHandle) → claimRef → PVC → workload; any hop that is Forbidden, errors, or finds nothing escalates as UNRESOLVED, never as confirmed-safe. This skill never deletes an EBS volume.

Explicitly not done

• No Flux YAML, no prune setting, no platform-repo change. Prune is correct.
• No delete on persistentvolumeclaims added to the per-engineer Role. That restriction is deliberate: the controller's finalizer owns PVC lifecycle, PVCs are not in the workspace repo so prune never targets them, and widening the Role would be a security regression that does not fix this bug. The new reference says so in place, so the next reader does not re-propose it.
• No controller Go changes. No storage-class changes.

Files

File	Change
references/teardown.md	New. The canonical teardown reference: the Retain trap and patch-before-delete ordering, the PR-based procedure, the reconcile target + disappearance poll, the namespace procedures, the leaked-resource sweep, and seven halt conditions.
SKILL.md	Post-merge reconciliation retargeted with a repo→Kustomization table; Guardrail #10; Procedure: tear down (PR-based); three halt conditions; teardown + namespace intent rows; reference-index entry; step-11/step-16 pointers.
references/cluster-inspection-recipes.md	Recipes #9 (disappearance poll, stuck-Terminating read) and #10 (orphan detection); recipe #8 states it is the target for workspace merges; bench:teardown reconciles <alias> and confirms the objects went away.
references/seinetwork-crd.md	deletionPolicy documented as the disk-leak field: the orphan mechanism, mutability, the closing window, and what the Delete cascade does end to end.
references/ephemeral-chain-flow.md	Step 14 gates on deletionPolicy before the git rm.
references/comparative-bench.md	Step 16, the single-teardown bullet, and the half-comparison halt: both SeiNetworks need the gate.
references/preflight.md	Gate 2b's rationale names the right target per repo.
references/troubleshooting-seinode.md	The finalizer-strip override says what it costs; the Retain note distinguishes forensics from a leak.
README.md	Teardown is PR-based, and the skill gates on the field that leaks disks.
evals/evals.json	Two evals: the Retain halt (empty ≠ safe; forbids the prune/reclaim/Role "fixes") and a clean teardown happy path.

Verification

Docs/skills only — no build, no module compile.

• The teardown verifier distinguishes API failure from verified absence. It reports exactly one of GONE / PRESENT / UNVERIFIED, capturing kubectl's exit status separately rather than counting lines from a pipeline. A Forbidden or dropped connection is UNVERIFIED, never a pass. The poll deadline is arithmetic on date +%s; Bash's SECONDS is unset under sh, where the comparison fails with Illegal number and the loop never runs. Both behaviours were reproduced under this host's /bin/sh before and after the fix.
• writing/scripts/lint.sh (Vale 3.17.1, after vale sync): 0 errors on every added line (530 added lines across 9 changed .md files). Warnings remain (sentence length, passive voice) at the same density as the surrounding file; CI's fail_level is error.
• xreview/scripts/skill-package-checks.sh --skill-dir .claude/skills/harbor-dev: no block-severity failure. Same two pre-existing non-block failures as main (T2 info: missing state/.gitkeep; A1 warn: time-sensitive content in SKILL.md/preflight.md/seictl-cli.md). B1 passes — SKILL.md is 396 lines against the 500 limit.
• writing/scripts/check-{verifiers,artifact-length,coverage,contract-anchors,anchor-authorities,generated-rules,admission,consumer-scoping,template-deltas}.sh: all pass.
• scripts/verify-references.sh: no error-class finding. scripts/sync-skills.sh --verify: catalog coverage OK. scripts/tests/skill-package-checks.test.sh: 47 passed, 0 failed.
• evals.json parses; the diff is 49 insertions, 0 deletions.

No command in this PR was run against a live cluster — none was available. Every documented invocation is derived from the repo's existing conventions.

Inferred rather than verified

• --with-source on the workspace Kustomization. The GitRepository it references comes from the platform-repo base (clusters/harbor/engineers/base/sync.yaml), which is not in this repo, so its namespace is unverified. If it sits outside eng-<alias>, the engineer's namespace-scoped Role returns Forbidden. The docs state that failure mode and the fallback (reconcile the Kustomization alone) rather than asserting the flag always works.
• EBS volume tag keys. kubernetes.io/created-for/pvc/namespace and .../pvc/name are the EBS CSI driver's own convention, not something these repos set. The doc tells the operator to confirm the keys against a known-live volume before trusting an empty filter result.
• The offboarding file list. Derived by mirroring the verified onboarding four-file shape in references/onboarding-pr.md; no worked offboarding PR exists to check it against. Marked as such in place, and routed to the platform team rather than presented as a self-service runbook.

The Kustomization name for fix 1 was verified, not inferred — <alias> in eng-<alias>, from references/onboarding-pr.md:110 and recipe #8.

🤖 Generated with Claude Code

---

Fix round — cross-review findings addressed

All three P1s, the P2, and the three non-blocking items are fixed on this branch. Commits 85cca82, f470156, a65e1b3, 8b9ffea.

#	Finding	Fix
P1-1	A failed API read reported success — kubectl | wc -l takes wc's exit status, so a Forbidden yielded zero lines and printed "all objects gone"	The poll captures kubectl's status separately and reports one of GONE / PRESENT / UNVERIFIED, with distinct exit codes 0/1/2. UNVERIFIED is a halt condition. Reproduced the false pass under /bin/sh, then reproduced all three outcomes correctly after the fix.
P1-2	The live-patch fast path is revertible — Flux reconciles Retain from git back over the patch, typically mid-review	Git-first is now the documented default: a policy PR, merged and reconciled, verified on both the committed file and the live object before the removal PR merges. The live patch survives only as a repair for a SeiNetwork no reconcile owns, and carries the re-verify-immediately-before-merge requirement. Propagated to SKILL.md, seinetwork-crd.md, ephemeral-chain-flow.md, comparative-bench.md, and both evals.
P1-3	available / Used By: <none> treated as proof of garbage, routing live disks into a deletion escalation	Both demoted to candidate signals. Added an ownership walk (volume ID → PV spec.csi.volumeHandle → claimRef → PVC → workload) and a verdict table whose every failed hop lands on UNRESOLVED. kubectl get pv is cluster-scoped, so Forbidden is called out as the normal engineer case and an unresolved result. This skill now never deletes an EBS volume.
P2-4	Bash SECONDS in an sh fence skips the poll; PVC and bench checks were single reads; PVC expectation contradicted the imported-PVC exception	Portable date +%s deadline. poll_gone in recipe #9 is reused for CRs, PVCs, pods, and bench Jobs/ConfigMaps — bench now polls pods too, since a Job can be gone while its pod is Terminating. The PVC expectation is no longer zero: controller-managed PVCs must go, imported PVCs must survive, and inventory step 2 now records which nodes carry spec.import because nothing says so after they are deleted.
NB	Unsupported namespace-cascade claim	Restated as an operational preference. The namespace controller does remove namespaced resources; emptying first is about keeping the gate, the poll, and the sweep usable while the objects still exist.
NB	Non-Git resources acknowledged but given no cleanup path	Added a table covering direct-applied CRs, SeiNodeTaskWorkflow, hand-applied bench Jobs, controller-managed PVCs, and S3 artifacts — each with an escalation or a guarded path. Anything not in it escalates as unresolved.
NB	Forbidden on --with-source stated as diagnostic	Now "may indicate" the cross-namespace GitRepository, alongside expired session, missing access entry, or a Role without the Flux verbs. Read the message first.
NB	"run without --filters" would enumerate other tenants' volumes	Replaced with --volume-ids <known-live-id>, scoped to one volume the operator already knows.

Also corrected, and it was wrong in the original body as well as the doc: spec.resources was listed among the immutable SeiNetworkSpec fields. There are exactly three immutability rules — spec.genesis, spec.replicas, spec.dataVolume — and SeiNetworkSpec has no resources field. Removed from both.

Untouched by design, per the review: the reconcile target (A), PR parity (E), the orphan-detection triple, the legitimate flux-system command in preflight.md, and the three inference caveats.

Gates after the fix round

• Vale: 0 errors on all 530 added lines across 9 changed .md files.
• skill-package-checks.sh: 20 pass / 2 fail / 4 skipped — the same two non-block failures as main (T2 info, A1 warn), no block failure. B1 passes at 396/500 lines.
• All 9 writing/scripts/check-*.sh: pass. verify-references.sh, sync-skills.sh --verify, skill-package-checks.test.sh (47/0): pass.
• evals.json parses; internal anchors resolve.

---

Round 3 — cross-review findings addressed

All nine fixed. Commits dfc6d90, 4b2e6ab, 95b3f7c, 45a623c. No finding was disputed; findings 1, 2 and 4 were reproduced or re-derived locally before fixing.

#	Finding	Fix
1 (block)	teardown.md re-implemented the poll twice instead of calling the shared poll_gone, and the copies had already diverged — the PVC loop emitted no verdict at all, just counts until its deadline	Both call sites now invoke the shared functions. Recipe #9 is the single implementation and says so.
2 (block)	UNVERIFIED still exited 0 — break succeeds, so the completed while returned 0, and no caller checked poll_gone's return code either	Added record/VERDICT aggregation where the worst outcome wins (0 GONE < 1 PRESENT < 2 UNVERIFIED) and every call site records. Confirmed under dash: break-after-UNVERIFIED does exit 0; after the fix, UNVERIFIED then GONE aggregates to 2.
3 (block)	The "engineer insists" exception let a pre-merge re-read stand in for a committed policy	Exception deleted for Flux-owned networks, with the four-step losing sequence written out — a pre-merge read narrows the window but does not order against Flux's reconcile. Path B is now a stacked draft PR; a merged PR cannot carry a later removal commit.
4 (block)	.spec.import does not exist — the field is .spec.dataVolume.import.pvcName, so the query matched nothing and every imported claim was reclassified as one that must disappear	Inventory rewritten: real node→claim identities from the pods' own claimName, imported vs controller-managed classification, abort on any API or parse failure. Poll named managed claims; assert imported ones with expect_present. Field path caveated as repo-main API inspection, not the deployed CRD. Also corrected the three pre-existing spec.import prose mentions elsewhere in the skill — see "scope call" below.
5	EBS walk: no PVC→node relationship; kubectl-into-jq hid API failures; missing-claim rows read as plain candidates	Hop 3 resolves the claim to the mounting pod and its owner reference; an empty result is unresolved, not unowned. Every hop separates the API call from the parse and checks both. Missing-claim and no-PV rows are now explicitly unresolved candidates requiring platform review.
6	Scope guards: cluster-wide claimRef followed without a namespace check; deletes without namespace/context; a failed grep read as "no manifest"	Added the claim_ns != eng-<alias> escalation gate; every delete names --context harbor and -n eng-<alias>; the authorizing search runs against a freshly fetched clone and branches on grep's exit status — only 1 (no match) authorizes a delete, 2+ is unresolved. Verified the three exit codes.
7	sed -n '/Used By/,+3p' is a GNU extension; blanket POSIX claim	That parse is gone (replaced by the hop-3 jq). The claim now reads "portable shell (dash, ash, bash)" and names date +%s as a deliberate near-universal extension rather than POSIX.
8	Evals preserved the unsafe exception and let the happy path proceed on live Delete alone	Both scenarios now require committed Delete for a Flux-owned object; the live-patch forbidden signal no longer has an escape clause; the happy path requires named-claim polling with aggregation.
9	--with-source fallback claimed to help "whatever the cause"	Now: it helps only the cross-namespace-source case, repairs nothing for expired credentials or a missing permission, and the fallback itself must succeed or you have no reconcile at all.

One extra defect found while fixing 4. jq's unique sorts by codepoint; comm assumes its input is sorted the way the locale collates, and a locale that ignores punctuation orders hyphenated claim names differently. The inventory script now pins LC_ALL=C.

Scope call to flag. Finding 4 was scoped to teardown.md, but the same wrong path appeared in three pre-existing prose lines in troubleshooting-seinode.md and one in seinetwork-crd.md. Leaving them would have made the skill contradict itself on an API path, so they were corrected to spec.dataVolume.import — prose only, no query. Revert if you would rather keep that out of this PR.

Gates after round 3

• Vale: 0 errors on all 669 added lines across 9 changed .md files (one write-good.ThereIs introduced and fixed mid-round).
• skill-package-checks.sh: 20 pass / 2 fail / 4 skipped — the same two non-block failures as main (T2 info, A1 warn). B1 passes at 396/500.
• All 9 writing/scripts/check-*.sh pass. verify-references.sh, sync-skills.sh --verify, skill-package-checks.test.sh (47/0) pass. evals.json parses; internal anchors resolve.
• Not executed: the jq filters. This host has no jq, and installing one was out of budget — they are reviewed by inspection only. The shell control flow around them (aggregation, expect_present, set -eu abort on a redirected failure, grep exit codes, comm) was executed under /bin/sh.

[cursor]

PR Summary

Low Risk
Changes are limited to Claude skill documentation and evals; no production cluster, Flux, or controller behavior is modified.

Overview
Docs-only update to the harbor-dev skill so agents stop treating a workspace teardown as done while validator disks are still running. No Flux, platform, or controller code changes.

The skill now documents that default SeiNetwork.spec.deletionPolicy: Retain orphans generated validators (and their PVCs/EBS volumes) when manifests are removed, and adds Guardrail #10 plus a full Procedure: tear down backed by new references/teardown.md.

Post-merge behavior is corrected: workspace-repo merges must reconcile Flux Kustomization <alias> in eng-<alias>, not flux-system, then poll until resources are gone with GONE / PRESENT / UNVERIFIED outcomes (API failures must not read as success). Shared shell helpers live in cluster-inspection-recipes.md recipe #9 (verify_teardown, poll_gone, sweep_residual); recipe #10 covers orphan detection.

Teardown is explicitly git-first: set deletionPolicy: Delete in the manifest and reconcile before the removal PR (not a bare kubectl patch on Flux-owned objects). Comparative bench, ephemeral-chain, and bench teardown docs point at the same procedure; evals/evals.json adds halt and happy-path teardown scenarios. Minor fixes align imported-PVC field paths to spec.dataVolume.import in troubleshooting prose.

^{Reviewed by Cursor Bugbot for commit 2218e68. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/seinetwork-crd.md

Line 67 in da67c84

Keep `Retain` only to preserve a validator's disk for forensics after the network goes away, and say so where the choice is made — a retained disk is a cost somebody chose.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is made'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/seinetwork-crd.md

Line 67 in da67c84

Keep `Retain` only to preserve a validator's disk for forensics after the network goes away, and say so where the choice is made — a retained disk is a cost somebody chose.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 29 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 3 in da67c84

Teardown removes an engineer's workloads from `eng-<alias>` through the same PR contract that created them. One ordering rule governs the whole file: **patch `spec.deletionPolicy` to `Delete` on every SeiNetwork you are about to remove, and land that patch before the removal merges.** A SeiNetwork deleted under the default `Retain` orphans its generated validator SeiNodes, and each orphan keeps its PVC and its EBS disk running with nothing left to clean it up.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 28 in da67c84

That window closes at deletion. Once a `Retain` deletion has stripped the owner references and removed the parent SeiNetwork, no patch brings the cascade back — the parent is gone and the children are top-level objects. The leftover SeiNodes and PVCs then need the manual cleanup in [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 28 in da67c84

That window closes at deletion. Once a `Retain` deletion has stripped the owner references and removed the parent SeiNetwork, no patch brings the cascade back — the parent is gone and the children are top-level objects. The leftover SeiNodes and PVCs then need the manual cleanup in [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'be deleted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 59 in da67c84

The patch mutates a live object outside git. That is acceptable here only because the object is about to be deleted, and only after the verify read prints `Delete`. Say in the removal PR body that the patch ran, so the reviewer sees the whole teardown.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 35 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 70 in da67c84

`--dry-run` runs server-side apply against the apiserver, so a wrong path fails the render rather than the teardown. Keep `Retain` only when the engineer wants a validator's disk preserved for forensics after the network goes away, and say so in the PR body — a retained disk is a cost the engineer is choosing.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 37 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 74 in da67c84

With `deletionPolicy: Delete` the chain runs end to end: SeiNetwork deleted → generated validator SeiNodes deleted through their owner references → each SeiNode's finalizer (`sei.io/seinode-finalizer`) deletes the node's data PVC → the storage class's `Delete` reclaim policy releases the EBS volume.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is preserved'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 76 in da67c84

The finalizer **skips an imported PVC** (`spec.import` set on the SeiNode). An imported PVC is preserved by design; its disk is not a leak.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are required'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 95 in da67c84

5. **Remove the manifests** — `git rm -r engineers/<alias>/<task>/` **and** remove the `<task>` entry from `engineers/<alias>/kustomization.yaml`'s `resources:` list. Both edits are required: Kustomize fails to render with a missing-resource entry, and Flux then applies nothing at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 97 in da67c84

7. **Open the PR** — title `feat(eng/<alias>): tear down <task>`. The body names the chain-id, every CR that goes away, the `deletionPolicy` value the SeiNetwork now carries, and the patch path (A or B) that set it. `gh pr create --repo sei-protocol/harbor-engineering-workspace --base main`.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is burned'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 99 in da67c84

9. **Report what survives** — the chain-id's S3 genesis artifacts are **not** purged by teardown, so the chain-id is burned. A later respin uses a fresh chain-id or purges the `<chain-id>/` prefix in `harbor-sei-k8s-genesis-artifacts` first.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are applied'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 107 in da67c84

The engineer's manifests are applied by the Flux `Kustomization <alias>` in namespace `eng-<alias>`, which watches `harbor-engineering-workspace` at `./engineers/<alias>` and reconciles every 5 minutes. The root `flux-system` Kustomization tracks `sei-protocol/platform` at `clusters/harbor`. Reconciling `flux-system` after a workspace-repo merge reconciles a different repository and reports success without applying the engineer's change.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 135 in da67c84

A successful reconcile says Flux applied the change. It does not say the objects are gone. Deletion is asynchronous and finalizers hold objects in `Terminating` while the controller releases their PVCs, so poll instead of asserting once:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'be gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 154 in da67c84

Every PVC belonging to the torn-down chain must be gone. A `Bound` PVC that outlives its SeiNode is a held disk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are held'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 158 in da67c84

If the poll runs out with objects still present, do not report the teardown as done and do not force the objects away. Read why they are held:

---

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'very' is a weasel word!

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 170 in da67c84

"Destroy my namespace" means one of two very different things. Ask which before acting.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 204 in da67c84

Empty the namespace first, through the steps above. Deleting the `Namespace` object while SeiNetworks still live in it starts a namespace-wide cascade that races the controller's finalizers and can strand PVCs with no owning CR to inspect.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 223 in da67c84

Each line is a validator still running with nothing that will ever delete it. Confirm the parent is gone before treating one as an orphan:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is attached'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 232 in da67c84

An orphaned SeiNode still shows a **`Bound`** PVC — the disk is attached and billing, not free-floating. A disk whose PVC has already gone shows up on the AWS side as **`available`**. Check both.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was provisioned'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 240 in da67c84

On the AWS side, the EBS CSI driver tags each volume with the PVC it was provisioned for:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 42 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 249 in da67c84

`state: in-use` with an orphaned SeiNode above it is a running leak. `state: available` is a disk nothing references at all. Those tag keys are the EBS CSI driver's own convention rather than something this skill's repos set — run the command once without `--filters` against a volume you know is live to confirm the keys are present before trusting an empty result.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 261 in da67c84

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 261 in da67c84

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 277 in da67c84

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 277 in da67c84

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 278 in da67c84

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 279 in da67c84

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 119 in da67c84

This abandons the PVC and its EBS disk — the finalizer is what deletes the PVC, so removing it is how a stuck teardown becomes a leaked disk. Take it only with the engineer's explicit acceptance, record the PVC name, and follow up with the sweep in `teardown.md` → *find and clean up already-leaked resources*.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is governed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in da67c84

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in da67c84

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in da67c84

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 35 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is burned'. ASD-STE100 asks for the active voice.

[github-actions]

📝 [vale] <AgenticWriting.STE-NounCluster> _{reported by reviewdog 🐶}
Noun cluster of more than three nouns: 'Flux reconcile reports success'. Break it with 'of' or 'for'.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 37 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 286 in 85cca82

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 287 in 85cca82

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 119 in 85cca82

This abandons the PVC and its EBS disk — the finalizer is what deletes the PVC, so removing it is how a stuck teardown becomes a leaked disk. Take it only with the engineer's explicit acceptance, record the PVC name, and follow up with the sweep in `teardown.md` → *find and clean up already-leaked resources*.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is governed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 85cca82

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 85cca82

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 85cca82

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is made'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 29 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in f470156

For a SeiNode, whether its PVC survives deletion is governed by `spec.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 37 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 43 words. ASD-STE100 allows 25. Split it.

[github-actions]

📝 [vale] <AgenticWriting.STE-ParagraphLength> _{reported by reviewdog 🐶}
Paragraph has more than 6 sentences. ASD-STE100 allows 6.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was rendered'. ASD-STE100 asks for the active voice.

[cursor]

Stale Bugbot comment from a previous run.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 188 in 4b2e6ab

A successful reconcile says Flux applied the change. It does not say the objects are gone. Deletion is asynchronous and finalizers hold objects in `Terminating` while the controller releases their PVCs, so poll instead of asserting once.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 198 in 4b2e6ab

**A failed API read is never a pass.** A `Forbidden` or a dropped connection returns zero lines, and a check that counts lines without reading the exit status prints "gone" precisely when it cannot see the cluster.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 200 in 4b2e6ab

**And a later success must never overwrite an earlier failure.** Printing `UNVERIFIED` is not enough on its own: a `break` out of a loop, or a bare call whose return code nobody reads, still leaves the block exiting 0. A human sees the warning; a wrapper script or an agent reading `$?` sees success. Every check records its outcome into a running verdict, and the worst one wins.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are held'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 231 in 4b2e6ab

If the poll runs out with objects still present, do not report the teardown as done and do not force the objects away. Read why they are held:

---

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'very' is a weasel word!

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 243 in 4b2e6ab

"Destroy my namespace" means one of two very different things. Ask which before acting.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 277 in 4b2e6ab

**Empty the namespace first, through the steps above.** This is an operational preference, not a claim about a failure mode: the Kubernetes namespace controller does remove namespaced resources on its own. Emptying first keeps the `deletionPolicy` gate, the disappearance poll, and the leak sweep available while the objects are still there to inspect. Once the namespace is going away, a `Retain` SeiNetwork's orphans are much harder to reason about, and there is no inventory left to check them against.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 296 in 4b2e6ab

Each line is a validator still running with nothing that will ever delete it. Confirm the parent is gone before treating one as an orphan:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 307 in 4b2e6ab

- **EC2 `state: available` does not mean unowned.** It means unattached. A volume backing a live PV whose PVC is `Bound` reads `available` the moment its workload stops — a scaled-to-zero StatefulSet, a pod stuck `Pending`, a node drained mid-reschedule. Deleting on that signal destroys a disk somebody is coming back to.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is unwanted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 308 in 4b2e6ab

- **`Used By: <pod>` does not prove the pod belongs to an orphan**, and `Used By: <none>` does not prove the PVC is unwanted. `describe pvc` reports current pod attachment, not ownership.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 34 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 320 in 4b2e6ab

Those tag keys are the EBS CSI driver's own convention rather than something this skill's repos set. To confirm they are present before trusting an empty result, describe **one volume you already know is live, by ID** — never re-run without `--filters`, which enumerates every volume in the account including other tenants':

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is namespaced'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 347 in 4b2e6ab

`kubectl get pv` is cluster-scoped, and the per-engineer Role is namespaced. Expect `Forbidden` here as the normal case for an engineer — that is an **unresolved** result, not a clean one. Hand the volume IDs to the platform team and let them walk the chain.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was stopped'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 352 in 4b2e6ab

| Volume → PV → PVC → a live, wanted workload | **Not garbage.** Leave it. `available` only meant the workload was stopped. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 353 in 4b2e6ab

| Volume → PV → PVC whose claim is gone, PV `Released` | Candidate for platform-team deletion. Report the PV, PVC name, and reclaim policy. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 367 in 4b2e6ab

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 367 in 4b2e6ab

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 376 in 4b2e6ab

**Never delete an EBS volume from this skill.** Even a volume the ownership walk resolved to a dead PVC goes to the platform team: `ec2:DeleteVolume` is outside the engineer's policy, the walk can be wrong, and an EBS delete is unrecoverable. Hand over the volume IDs, sizes, creation times, and the walk's verdict per volume — including every `UNRESOLVED` one, labelled as unresolved. Escalate through `#harbor-onboarding`. Do not report the cleanup as complete while any ID is outstanding.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 380 in 4b2e6ab

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 380 in 4b2e6ab

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 398 in 4b2e6ab

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 398 in 4b2e6ab

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 399 in 4b2e6ab

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 400 in 4b2e6ab

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 402 in 4b2e6ab

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is preserved'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 65 in 4b2e6ab

- For **imported** PVCs (`spec.dataVolume.import` set on the SeiNode): the PVC is preserved; the recreated SeiNode reuses existing data.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'being recreated'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 66 in 4b2e6ab

- For **controller-managed** PVCs (no `spec.dataVolume.import`): the controller's `handleNodeDeletion` path deletes the PVC during teardown. Delete-and-recreate **wipes data**. Safe for ephemeral chains being recreated from genesis; not safe for archive nodes or any chain with state worth preserving.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is governed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 4b2e6ab

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 4b2e6ab

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 4b2e6ab

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 37 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 36 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is preserved'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'were imported'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is preserved'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 65 in 95b3f7c

- For **imported** PVCs (`spec.dataVolume.import` set on the SeiNode): the PVC is preserved; the recreated SeiNode reuses existing data.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'being recreated'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 66 in 95b3f7c

- For **controller-managed** PVCs (no `spec.dataVolume.import`): the controller's `handleNodeDeletion` path deletes the PVC during teardown. Delete-and-recreate **wipes data**. Safe for ephemeral chains being recreated from genesis; not safe for archive nodes or any chain with state worth preserving.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is governed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 95b3f7c

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 95b3f7c

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/troubleshooting-seinode.md

Line 319 in 95b3f7c

For a SeiNode, whether its PVC survives deletion is governed by `spec.dataVolume.import` (imported PVC = preserved) vs controller-managed (wiped on teardown) — documented under **Phase: Failed** above. A `SeiNetwork`'s `spec.deletionPolicy` (defaults `Retain`) governs whether the controller orphans its generated validator SeiNodes (and thus their PVCs) when the network is deleted. Forensics is the one case where `Retain` is the right answer; on an ordinary teardown it is a disk leak, because the orphaned validators keep running with no owner left to delete them (see `teardown.md`). The hardlink trick above is for **live debugging** while the node continues running. The two are complementary, not redundant.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 37 words. ASD-STE100 allows 25. Split it.

[github-actions]

📝 [vale] <AgenticWriting.STE-ParagraphLength> _{reported by reviewdog 🐶}
Paragraph has more than 6 sentences. ASD-STE100 allows 6.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 34 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 35 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is preserved'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'being recreated'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is governed'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is deleted'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

[seidroid]

Findings on the changed lines. The verdict and the summary are in this tool's comment on this pull request.

[seidroid]

blocker — This step now contradicts the section it links to. Verify the teardown polls PVCs by name from ./teardown-inventory/managed-claims.txt and imported-claims.txt — its PVC calls carry no -l to drop — and both line 245 here and cluster-inspection-recipes.md:249 state in bold that a namespace sweep is the wrong check, because imported claims and other chains' claims make it report PRESENT after a correct teardown. Step 1 of this procedure is a display-only kubectl get seinetwork,seinode,job,pvc, so it never generates those name lists: an operator following this step either runs the sweep the same file argues trains the reader to ignore the check, or has no inputs for the verification at all. It is also worst in the case that most needs it — a namespace holding orphans from an earlier Retain teardown, where a sweep can never reach GONE. Point step 1 at the inventory script from Procedure step 2, run over every chain in the namespace, and have step 4 use the same by-name calls.

[seidroid]

suggestion — 2>&1 merges stderr into out, and left=$(printf '%s' "$out" | grep -c .) counts every line in it as a remaining object. Any stderr line emitted alongside a successful read — an apiserver deprecation or warning header, a stale-cache notice — inflates the count, so the loop runs to the deadline and reports PRESENT for a namespace that is actually empty; expect_present at line 224 has the same construction and would report MISSING. The direction is fail-safe, but a false alarm is exactly what line 249 says trains the reader to ignore the check. Capture stderr into a separate variable or file so the count sees only stdout, and keep it for the UNVERIFIED message. (Correcting my earlier reviews: I attributed this to kubectl's "No resources found" notice; on the -o name path that is unverified, and the warning-header case is what holds.)

[seidroid]

suggestion — The gate names the wrong SeiNetwork for the steps it prefixes. This bullet lands deletionPolicy: Delete on the surviving side, but the two steps below git rm the failed side's chain-<a-or-b>/ and the closing line says Flux prunes the SeiNetwork on the failed side. The network whose policy decides whether validators are orphaned is the one being removed, so the gate belongs there; "the failed side needs the same read" leaves the load-bearing case as a secondary check. The verb is right now — swap which side it applies to.

[seidroid]

suggestion — This inventory is a bare kubectl get pvc -n eng-<alias> and step 9 says only "poll the PVCs too", so the always-loaded procedure produces neither the managed nor the imported claim-name list that recipe #9 now requires, and never mentions the record/VERDICT aggregation that keeps an early UNVERIFIED from being masked. An agent working from SKILL.md alone lands on the namespace sweep that teardown.md:245 and recipe #9 both call the wrong check. Point this step at the inventory script in references/teardown.md procedure step 2, and have step 9 name the by-name calls and the verdict aggregation.

[seidroid]

review found something blocking. The findings are on the lines they are about, and the summary is in this tool's comment on this pull request.

[seidroid]

What changed

The pull request moved again (merge commit 965ea6d, diff now 907 lines). references/teardown.md grew from 381 to 406 lines, cluster-inspection-recipes.md recipe #9 was substantially rewritten, and troubleshooting-seinode.md gained a hunk correcting spec.import to spec.dataVolume.import.

Three of my four blockers are addressed. Path B is now executable — it stacks a draft removal PR on the policy PR and states plainly that a single PR carrying both is not that path (teardown.md:65). The imported-PVC inventory is rebuilt: the field path is now .spec.dataVolume.import.pvcName, matching the only path this repo records, carrying an explicit caveat that it comes from controller main rather than the deployed CRD and that the CRD wins; and the inventory now emits real claim names, read from the pods' own spec.volumes[].persistentVolumeClaim.claimName rather than a guessed naming rule, split into managed and imported lists. The unselected poll_gone pvc is gone — PVCs are polled by name with --ignore-not-found, with a new expect_present asserting the imported claims survived, and a record/VERDICT aggregation so a later success cannot mask an earlier UNVERIFIED. The inventory script also avoids the kubectl | jq pipeline whose exit status belongs to jq, and pins LC_ALL=C for the comm against jq's codepoint sort. One blocker remains, and it is one this revision created.

A correction to my last two reviews: I said 2>&1 makes GONE unreachable because a namespaced kubectl get prints "No resources found" to stderr. With -o name, kubectl takes its non-human-readable print path, and I do not have a cluster here to confirm the notice is emitted on that path. Treat that claim as unverified — the narrower defect below is what holds.

1. Blocking

The namespace-emptying path instructs the check the verification section forbids, using files that path never creates. references/teardown.md:270 says to run Verify the teardown "with no -l selector, so the poll covers the whole namespace." The section it links to no longer works that way: its PVC calls take names from ./teardown-inventory/managed-claims.txt and imported-claims.txt, they carry no -l to drop, and teardown.md:245 and cluster-inspection-recipes.md:249 both state in bold that a namespace sweep is the wrong check because imported claims and other chains' claims make it report PRESENT after a correct teardown. The empty-the-namespace procedure's own inventory (teardown.md:264) is a display-only kubectl get seinetwork,seinode,job,pvc, so it never produces those name lists. An operator following this step either performs the sweep the same file argues trains readers to ignore the check, or has no inputs for the verification at all — and in the case the sweep is most likely to be run, a namespace holding orphans from an earlier Retain teardown, the poll cannot reach GONE at all.

2. Non-blocking

• references/cluster-inspection-recipes.md:202 (and :224) merge stderr into the counted output with 2>&1, and grep -c . counts every line in it; any stderr line emitted alongside a successful read — an apiserver deprecation warning, a stale-cache notice — inflates left/got and yields a false PRESENT or MISSING. Fail-safe in direction, but a false alarm is what the file at :249 says trains the reader to ignore the check; capture stderr separately and count only stdout.
• references/comparative-bench.md:429 names the wrong SeiNetwork: the bullet gates the surviving side, while the two steps it prefixes git rm the failed side's chain-<a-or-b>/ and the closing line says Flux prunes the failed side — the network being removed is the one whose policy decides whether validators are orphaned. (The verb was correctly updated to "land in the manifest" this revision.)
• SKILL.md:265 inventories with a bare kubectl get pvc -n eng-<alias>, and SKILL.md:272 says only "poll the PVCs too"; neither produces the named managed/imported lists that recipe chore(agents): add Output Discipline section to all agents #9 now requires, nor mentions the record/verdict aggregation, so the always-loaded procedure still leads to the sweep the reference forbids.
• references/teardown.md:3 states the file's governing rule as "patch spec.deletionPolicy to Delete … and land that patch before the removal merges", which the file's own :67 now closes off for any Flux-owned SeiNetwork.
• evals/evals.json:242 still says spec.import where the rest of the change moved to spec.dataVolume.import.
• references/teardown.md:26 asserts SeiNetworkSpec carries "exactly three" immutability rules, while the PR body says four and seinetwork-crd.md:38 names two.
• references/teardown.md:150 tells the reader to "source" poll_gone, expect_present, and record, but they live in a fenced block in a markdown reference with no file to source.
• references/teardown.md:342 uses sed -n '/Used By/,+3p'; the addr,+N form is GNU-only and fails on the BSD sed macOS ships, which is the laptop this skill's pre-flight assumes.
• "Render new chains with Delete from the start" (references/teardown.md:81-90) is still the only preventive step and still sits in the teardown-time file; the spinup procedure is untouched, so every new chain renders Retain.
• The Delete enum literal remains uncited in this repo — the /kubernetes kit corroborates only the Retain branch — and the PR body's "inferred rather than verified" list still omits it, unlike the field path and tag keys it now marks in place.
• references/teardown.md:367 asserts gp3-10k-750, gp3, and gp3-archive and their reclaim policies; those names appear nowhere else in the repo and carry none of the unverified marking the same file now gives the CRD field path.
• The escape-hatch row at references/teardown.md:385 directs seictl network|node delete without restating that SKILL.md:381 requires explicit per-invocation confirmation for that verb.
• The orphan jq (references/teardown.md:293, cluster-inspection-recipes.md:331) emits - when the sei.io/seinetwork label is absent, and the follow-up kubectl get seinetwork <seinetwork-label-value> then runs against -.

3. Summary

This revision closed Path B, the imported-PVC field path and identifier, and the unselected PVC poll — the three blockers I carried in, one of which was codex's from an earlier dispatch — and the replacements are stronger than what I asked for: claim names read from the pods rather than guessed, a MISSING assertion for preserved claims, verdict aggregation so no later success masks an earlier UNVERIFIED, and a field-path caveat that defers to the deployed CRD. What blocks now is a seam the rewrite opened: the empty-the-namespace step still calls for a namespace-wide poll that the verification section it links to has just finished arguing is the wrong check, and it depends on inventory files that path never generates. I also retract, above, my earlier claim that the 2>&1 capture makes GONE unreachable — the mechanism I named is unverified for -o name, and the remaining defect is narrower and non-blocking. Codex contributed no reading this dispatch — it reported reading no diff — so nothing was carried over or dropped from it here. The repository has no REVIEW.md on main.

_{seidroid review · decision request_changes · session 9e5542c4a82248afa23681c6eda59b44 · turn resp_claude_d4d3a5917b087706481b35377ecaeb84 · item 1c5c78d4c2045a9aaf3f5902ae91ab0f}

Findings: 1 blocking | 14 non-blocking | 4 posted inline | 1 pre-existing

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

SKILL inventory omits claim classification

Medium Severity

Step 9 now polls controller-managed PVCs by name from the step-2 inventory and forbids a namespace-wide sweep, and the happy-path eval requires capturing imported versus managed claims. Step 2 still runs kubectl get pvc -n eng-<alias> and never classifies those claims, so an agent following SKILL.md inventories the sweep that step 9 says makes a correct teardown report PRESENT.

Additional Locations (2)

• .claude/skills/harbor-dev/evals/evals.json#L239-L254
• .claude/skills/harbor-dev/references/teardown.md#L101-L145

 

^{Reviewed by Cursor Bugbot for commit 45a623c. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 447 in 91a99aa

| Volume → PV → PVC whose claim is gone, PV `Released` | **Unresolved candidate.** Platform review required. Report the PV, PVC name, and reclaim policy; do not act on it here. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is told'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 453 in 91a99aa

Only the first two rows are verdicts. Every other row is an escalation, and the platform team is told which row it came from.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 455 in 91a99aa

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is namespaced'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 455 in 91a99aa

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 455 in 91a99aa

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 467 in 91a99aa

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 467 in 91a99aa

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 476 in 91a99aa

**Never delete an EBS volume from this skill.** Even a volume the ownership walk resolved to a dead PVC goes to the platform team: `ec2:DeleteVolume` is outside the engineer's policy, the walk can be wrong, and an EBS delete is unrecoverable. Hand over the volume IDs, sizes, creation times, and the walk's verdict per volume — including every `UNRESOLVED` one, labelled as unresolved. Escalate through `#harbor-onboarding`. Do not report the cleanup as complete while any ID is outstanding.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 480 in 91a99aa

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 480 in 91a99aa

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 493 in 91a99aa

**Every namespace-scoped command above names its namespace, and every destructive one names its context.** An unqualified `delete` deletes wherever the shell happens to point, and that is not a typo you can retry — it is a delete in the wrong place.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 32 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 497 in 91a99aa

If a workflow genuinely needs `seictl` for a destructive verb, pin the cluster out of band and prove it immediately before, in the same command list — a guard that runs, not a parenthetical:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 511 in 91a99aa

Before deleting anything imperatively, prove the object is **not** in the workspace repo. A search that fails must never read as "no manifest found" — `grep` exits 1 for no match and 2 or more for an error, and an unreadable or stale clone produces the same empty output as a genuinely absent manifest.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 47 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 527 in 91a99aa

**Only exit status 0 from this block authorizes a direct delete.** Every branch used to end in a successful `echo`, so the block's own status was 0 whatever it found — a scripted caller could not tell "not in git" from "the search failed", which is the same class of defect as counting lines without reading an exit status. `1` routes to the PR path; `2` means the question was never answered.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 534 in 91a99aa

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 534 in 91a99aa

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 535 in 91a99aa

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 536 in 91a99aa

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 538 in 91a99aa

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[seidroid]

Findings on the changed lines. The verdict and the summary are in this tool's comment on this pull request.

[seidroid]

blocker — This is the block an operator following teardown.md runs, and it is a generation behind the recipe it cites. It never reads $INV/status, it inlines $(cat ./teardown-inventory/managed-claims.txt) into the arguments, and it uses ; record $? — the two patterns recipe #9 names as defects, one in the words 'losing the inventory reads as a clean teardown'. The new inventory makes the consequence concrete: inventory.sh writes managed-claims.txt before completeness check 1, so an aborted run leaves that file present but missing the unresolved node's claim while status reads UNRESOLVED. This block polls the truncated list, finds nothing, and prints TEARDOWN VERIFIED — precisely the node whose disk may be leaking, reported as verified. Two smaller faults in the same block: it hardcodes ./teardown-inventory while the namespace procedure now directs per-chain INV=./teardown-inventory-<chain-id> directories, and a missing file collapses to an empty argument list that turns poll_gone pvc --ignore-not-found into the namespace sweep this page forbids. Line 256 already says not to re-implement the helpers: replace the block with recipe #9's read_inventory/OR-list version, parameterised on INV, or drop it and link there.

[seidroid]

suggestion — The gate still names the wrong side. It lands deletionPolicy: Delete in the surviving side's manifest, but the two steps below git rm the failed side's chain-<a-or-b>/ and the closing line says Flux prunes the SeiNetwork on the failed side. The network whose policy decides whether its validators are orphaned is the one being removed, so the gate belongs there; 'the failed side needs the same read' leaves the load-bearing case as a secondary check. The verb is correct now — only the side needs swapping.

[seidroid]

suggestion — This step is still a bare kubectl get seinetwork,seinode plus kubectl get pvc -n eng-<alias>, which captures no imported-versus-managed split and produces none of the named-claim files. Step 9 now correctly tells the agent to poll 'by name from the step-2 inventory' and to aggregate outcomes, so the always-loaded procedure asks its own step 2 for something it does not produce — and an agent working from SKILL.md alone lands on the namespace sweep that teardown.md and recipe #9 both reject. Point this step at inventory.sh in references/teardown.md procedure step 2, and name the status/managed-claims.txt/imported-claims.txt outputs step 9 consumes.

[seidroid]

review found something blocking. The findings are on the lines they are about, and the summary is in this tool's comment on this pull request.

[seidroid]

What changed

The pull request moved again (merge commit daf1fb5, diff now 1116 lines). Only references/teardown.md changed, 459 → 542 lines; every other file is byte-identical to the last revision.

Two of my three blockers are closed. The inventory script now writes $INV/status — UNRESOLVED up front, flipped to OK only after both completeness checks pass — and produces the unresolved-nodes.txt that recipe #9's gate names, so the verification block can reach VERIFIED on a clean teardown instead of always reporting UNVERIFIED. The empty-the-namespace path no longer calls for the sweep the verification forbids: it enumerates the namespace's chain-ids, runs inventory.sh once per chain into its own INV directory, and states that the CR and pod polls may drop -l while the claim checks may not. Beyond what I raised, the inventory now attributes claims node-by-node and refuses to pass when a SeiNode resolves to no storage — closing the "node whose pod is absent goes unverified" gap I had listed as non-blocking — surfaces unattributed namespace claims, and marks the pod-to-node attribution as a convention rather than a contract. The ownership walk's hop 3 now separates parse failure from "no pod mounts it", and the ownership-search block returns distinct exit statuses instead of always exiting 0. The switch of direct deletes from seictl to kubectl --context harbor checks out against seictl-cli.md:31-34, which lists only --kubeconfig and -n/--namespace as common flags and carries no --context anywhere in the file. One blocker is untouched, and the hardening around it has made it sharper.

1. Blocking

The verify block in teardown.md is still the pre-rewrite version, and it now silently discards the safety the inventory just gained. references/teardown.md:256-278 inlines $(cat ./teardown-inventory/managed-claims.txt) into the helpers' arguments and uses ; record $? — the two patterns recipe #9 explicitly names as defects, one of them in the words "losing the inventory reads as a clean teardown" — and it never reads $INV/status. The concrete consequence is new this revision: when inventory.sh aborts at completeness check 1, it has already written managed-claims.txt, so that file exists but omits the unresolved node's claim while status reads UNRESOLVED. This block polls the truncated list, finds it clean, and prints TEARDOWN VERIFIED — a node's disk never checked, reported as verified. It also hardcodes ./teardown-inventory while the namespace path four sections down now directs per-chain INV=./teardown-inventory-<chain-id> directories, and a missing file yields an empty argument list that turns poll_gone pvc --ignore-not-found into the namespace sweep the same page forbids. Line 256 tells the reader not to re-implement these helpers while the block underneath does exactly that; recipe #9's read_inventory/OR-list version already exists to be pointed at.

2. Non-blocking

• The whole inventory now hinges on a pod's first owner reference name equalling the SeiNode name (references/teardown.md:130-139); the file marks it a convention and fails safe, but if the controller's StatefulSet naming differs at all, every node lands unresolved and inventory.sh exits 2 on every chain, so the documented teardown can never complete until someone verifies the convention.
• references/comparative-bench.md:429 gates the surviving side, while the two steps it prefixes git rm the failed side's chain-<a-or-b>/ and the closing line says Flux prunes the failed side — the network being removed is the one whose policy decides whether validators are orphaned.
• SKILL.md:265 inventories with a bare kubectl get pvc -n eng-<alias> and captures no imported-versus-managed split, while step 9 tells the agent to poll "by name from the step-2 inventory"; the always-loaded procedure's step 2 still does not produce those names or mention inventory.sh.
• references/cluster-inspection-recipes.md:293 hardcodes INV=./teardown-inventory, which the new per-chain namespace procedure contradicts.
• references/teardown.md:3 still states the file's governing rule as "patch spec.deletionPolicy to Delete … and land that patch before the removal merges", which :67 closes off for any Flux-owned SeiNetwork.
• references/teardown.md:482 now prescribes kubectl --context harbor delete seinetwork|seinode for a confirmed non-Flux object, but SKILL.md:381's confirmation taxonomy gates only seictl network|node delete, so the newly recommended command sits outside the documented approval gate.
• references/teardown.md:26 asserts SeiNetworkSpec carries "exactly three" immutability rules, while the PR body says four and seinetwork-crd.md:38 names two.
• references/cluster-inspection-recipes.md:198 leaves $ERRF in ${TMPDIR:-/tmp} with no cleanup.
• references/teardown.md:256 says to "source" the four helpers, but they live in a fenced block inside a markdown reference with no file to source.
• "Render new chains with Delete from the start" (references/teardown.md:81-90) is still the only preventive step and still sits in the teardown-time file; the spinup procedure is untouched, so every new chain renders Retain.
• The Delete enum literal remains uncited in this repo — the /kubernetes kit corroborates only the Retain branch — and the PR body's "inferred rather than verified" list still omits it, unlike the field path, attribution convention, and tag keys the file marks in place.
• references/teardown.md:467 asserts gp3-10k-750, gp3, and gp3-archive and their reclaim policies; those names appear nowhere else in the repo and carry none of the unverified marking the same file gives its other inferences.
• The orphan check (references/teardown.md:359, cluster-inspection-recipes.md:353) substitutes - when the sei.io/seinetwork label is absent, so the parent lookup runs against -.

3. Summary

This revision closed the status-gate mismatch and the namespace-sweep contradiction, and went further than I asked on both: the inventory now refuses to declare itself complete when a SeiNode resolves to no storage, which is the leak case, and the namespace path runs a real per-chain inventory instead of a display read. What still blocks is the one seam that has survived three revisions — teardown.md's own verify block is the copy an operator runs, and it is a generation behind the recipe it tells the reader to use: no status check, inlined $(cat …), ; record $?, a hardcoded inventory directory. Because the inventory now writes a truncated managed-claims.txt alongside an UNRESOLVED status when it aborts, that stale block will report TEARDOWN VERIFIED in exactly the case the new checks were added to catch. The fix is deletion and a pointer, not new material. Codex contributed no reading this dispatch — it reported reading no diff — so nothing was carried over or dropped from it here. The repository has no REVIEW.md on main.

_{seidroid review · decision request_changes · session 9e5542c4a82248afa23681c6eda59b44 · turn resp_claude_044fb88b1c6d2107a3b5aafe4d31de55 · item 629b1292390452ccb59fc6aef1c70d54}

Findings: 1 blocking | 13 non-blocking | 3 posted inline | 1 pre-existing

[cursor]

Stale Bugbot comment from a previous run.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are held'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 303 in 925fe40

If the poll runs out with objects still present, do not report the teardown as done and do not force the objects away. Read why they are held:

---

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'very' is a weasel word!

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 315 in 925fe40

"Destroy my namespace" means one of two very different things. Ask which before acting.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 34 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 335 in 925fe40

1. **List what is there, then inventory each chain properly.** The display read below is an overview, not an inventory — it produces none of the named-claim files the verifier consumes, so it cannot stand in for step 2 of the per-chain procedure:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 35 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 341 in 925fe40

Then discover the chain-ids **with the discovery's own status checked**. Piping `kubectl` into `sort` exits with sort's status, so a `Forbidden` becomes a successful empty list — and "no chains found" then reads as "nothing to do", which is the whole defect class this document exists to close:

---

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'usually' is a weasel word!

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 357 in 925fe40

Run `inventory.sh` **once per chain-id**, each writing its own `./teardown-inventory-<chain-id>`. A namespace usually holds more than one chain, and a single sweep cannot tell one chain's controller-managed claim from another's. Any chain whose `inventory.sh` exits non-zero writes no certificate, and its verification then reports `UNVERIFIED` — emptying a namespace on an incomplete inventory is how a leak becomes invisible. Claims no chain attributes land in each run's `unattributed-claims.txt`; take those to the leak sweep in step 5, not to a delete.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 357 in 925fe40

Run `inventory.sh` **once per chain-id**, each writing its own `./teardown-inventory-<chain-id>`. A namespace usually holds more than one chain, and a single sweep cannot tell one chain's controller-managed claim from another's. Any chain whose `inventory.sh` exits non-zero writes no certificate, and its verification then reports `UNVERIFIED` — emptying a namespace on an incomplete inventory is how a leak becomes invisible. Claims no chain attributes land in each run's `unattributed-claims.txt`; take those to the leak sweep in step 5, not to a delete.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 393 in 925fe40

**Empty the namespace first, through the steps above.** This is an operational preference, not a claim about a failure mode: the Kubernetes namespace controller does remove namespaced resources on its own. Emptying first keeps the `deletionPolicy` gate, the disappearance poll, and the leak sweep available while the objects are still there to inspect. Once the namespace is going away, a `Retain` SeiNetwork's orphans are much harder to reason about, and there is no inventory left to check them against.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 412 in 925fe40

Each line is a validator still running with nothing that will ever delete it. Confirm the parent is gone before treating one as an orphan:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 423 in 925fe40

- **EC2 `state: available` does not mean unowned.** It means unattached. A volume backing a live PV whose PVC is `Bound` reads `available` the moment its workload stops — a scaled-to-zero StatefulSet, a pod stuck `Pending`, a node drained mid-reschedule. Deleting on that signal destroys a disk somebody is coming back to.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is unwanted'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 424 in 925fe40

- **`Used By: <pod>` does not prove the pod belongs to an orphan**, and `Used By: <none>` does not prove the PVC is unwanted. `describe pvc` reports current pod attachment, not ownership.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 34 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 436 in 925fe40

Those tag keys are the EBS CSI driver's own convention rather than something this skill's repos set. To confirm they are present before trusting an empty result, describe **one volume you already know is live, by ID** — never re-run without `--filters`, which enumerates every volume in the account including other tenants':

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 462 in 925fe40

**Hop 2 is a scope gate, not just a lookup.** `kubectl get pv` is cluster-scoped, so the `claimRef` it returns can name *any* namespace. Assert it is this tenant's before inspecting further — a claim in another namespace is another tenant's disk, and this skill does not investigate those.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is unresolved'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 497 in 925fe40

The owner reference names the StatefulSet the controller created for the node, not the SeiNode directly. Map it back to a SeiNode by name and confirm that node is a **confirmed orphan** by the signature in [Orphaned SeiNodes](#orphaned-seinodes). If you cannot make that link, the hop is unresolved.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was stopped'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 502 in 925fe40

| Volume → PV → PVC → pod → a live, wanted workload | **Not garbage.** Leave it. `available` only meant the workload was stopped. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 503 in 925fe40

| Volume → PV → PVC whose claim is gone, PV `Released` | **Unresolved candidate.** Platform review required. Report the PV, PVC name, and reclaim policy; do not act on it here. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is told'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 509 in 925fe40

Only the first two rows are verdicts. Every other row is an escalation, and the platform team is told which row it came from.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 511 in 925fe40

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is namespaced'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 511 in 925fe40

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 511 in 925fe40

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 523 in 925fe40

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 523 in 925fe40

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 532 in 925fe40

**Never delete an EBS volume from this skill.** Even a volume the ownership walk resolved to a dead PVC goes to the platform team: `ec2:DeleteVolume` is outside the engineer's policy, the walk can be wrong, and an EBS delete is unrecoverable. Hand over the volume IDs, sizes, creation times, and the walk's verdict per volume — including every `UNRESOLVED` one, labelled as unresolved. Escalate through `#harbor-onboarding`. Do not report the cleanup as complete while any ID is outstanding.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 536 in 925fe40

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 536 in 925fe40

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 549 in 925fe40

**Every namespace-scoped command above names its namespace, and every destructive one names its context.** An unqualified `delete` deletes wherever the shell happens to point, and that is not a typo you can retry — it is a delete in the wrong place.

---

🚫 [vale] <write-good.ThereIs> _{reported by reviewdog 🐶}
Don't start a sentence with 'There is'.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 553 in 925fe40

**There is no `seictl` alternative for network or node deletion here, guarded or otherwise.** A `kubectl config current-context` check reads mutable state rather than pinning the config the delete then consumes, so it leaves a window between the check and the call — and it buys nothing, because `kubectl --context harbor delete` does the same deletion against the same CR with no window at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 43 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 553 in 925fe40

**There is no `seictl` alternative for network or node deletion here, guarded or otherwise.** A `kubectl config current-context` check reads mutable state rather than pinning the config the delete then consumes, so it leaves a window between the check and the call — and it buys nothing, because `kubectl --context harbor delete` does the same deletion against the same CR with no window at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 555 in 925fe40

Should some genuinely `seictl`-only destructive verb ever need documenting, the pin belongs on the invocation: hand it a kubeconfig that contains the harbor cluster and nothing else, via `--kubeconfig <harbor-only-file>` (a documented `seictl` flag). A file that cannot name another cluster cannot select one. Do not substitute a current-context check.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 559 in 925fe40

Before deleting anything imperatively, prove the object is **not** in the workspace repo. A search that fails must never read as "no manifest found" — `grep` exits 1 for no match and 2 or more for an error, and an unreadable or stale clone produces the same empty output as a genuinely absent manifest.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 47 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 575 in 925fe40

**Only exit status 0 from this block authorizes a direct delete.** Every branch used to end in a successful `echo`, so the block's own status was 0 whatever it found — a scripted caller could not tell "not in git" from "the search failed", which is the same class of defect as counting lines without reading an exit status. `1` routes to the PR path; `2` means the question was never answered.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 582 in 925fe40

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 582 in 925fe40

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 583 in 925fe40

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 584 in 925fe40

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 586 in 925fe40

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 32 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are recorded'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was written'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are matched'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 582 in ba2c5a0

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 583 in ba2c5a0

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 584 in ba2c5a0

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 586 in ba2c5a0

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

SKILL.md still calls old helpers

Medium Severity

Recipe #9 now says verify_teardown is the only entry point and changes poll_gone / expect_present to take the namespace first. SKILL.md step 9 still tells the agent to call poll_gone / expect_present / record directly. That contradicts the skill’s first surface: an agent following SKILL.md skips the certificate and named-claim gates, and the old helper signature binds kinds as the namespace so the check cannot see the cluster.

Additional Locations (1)

• .claude/skills/harbor-dev/references/cluster-inspection-recipes.md#L228-L236

 

^{Triggered by learned rule: Skill cross-file claim precision: taxonomy and authority statements must match everywhere}

^{Reviewed by Cursor Bugbot for commit ba2c5a0. Configure here.}

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 591 in 604b772

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 591 in 604b772

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 604 in 604b772

**Every namespace-scoped command above names its namespace, and every destructive one names its context.** An unqualified `delete` deletes wherever the shell happens to point, and that is not a typo you can retry — it is a delete in the wrong place.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 43 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 608 in 604b772

**No `seictl` alternative for network or node deletion belongs here, guarded or otherwise.** A `kubectl config current-context` check reads mutable state rather than pinning the config the delete then consumes, so it leaves a window between the check and the call — and it buys nothing, because `kubectl --context harbor delete` does the same deletion against the same CR with no window at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 610 in 604b772

Should some genuinely `seictl`-only destructive verb ever need documenting, the pin belongs on the invocation: hand it a kubeconfig that contains the harbor cluster and nothing else, via `--kubeconfig <harbor-only-file>` (a documented `seictl` flag). A file that cannot name another cluster cannot select one. Do not substitute a current-context check.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 614 in 604b772

Before deleting anything imperatively, prove the object is **not** in the workspace repo. A search that fails must never read as "no manifest found" — `grep` exits 1 for no match and 2 or more for an error, and an unreadable or stale clone produces the same empty output as a genuinely absent manifest.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 47 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 630 in 604b772

**Only exit status 0 from this block authorizes a direct delete.** Every branch used to end in a successful `echo`, so the block's own status was 0 whatever it found — a scripted caller could not tell "not in git" from "the search failed", which is the same class of defect as counting lines without reading an exit status. `1` routes to the PR path; `2` means the question was never answered.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 637 in 604b772

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 637 in 604b772

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 638 in 604b772

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 639 in 604b772

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 641 in 604b772

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is written'. ASD-STE100 asks for the active voice.

[seidroid]

Findings on the changed lines. The verdict and the summary are in this tool's comment on this pull request.

[seidroid]

suggestion — Steps 4-5 still inherit $chains and $VERDICT from step 1 across opening a PR, review, and a merge, so a fresh shell is the ordinary case. sweep_residual now keeps that from hiding a leak — a leftover claim or a lingering SeiNode still fails the run — so this is no longer blocking. What survives is narrower: with an empty $chains the per-chain loop runs zero times, expect_present never asserts the imported claims survived, and the summary at line 417 still prints 'every chain verified'. Re-derive $chains at the top of step 4 from the ./teardown-inventory-* directories on disk (treating an empty result as UNVERIFIED unless a discovery that succeeded in this shell says otherwise), and the assumption goes away.

[seidroid]

suggestion — This still points the agent at poll_gone / expect_present / record, but recipe #9 now makes verify_teardown and sweep_residual the entry points, with 'Do not copy pieces' written into the block. The always-loaded file names the parts the library asks callers not to assemble themselves. Point step 9 at verify_teardown, and mention sweep_residual for the namespace case.

[seidroid]

suggestion — The gate names the wrong side. It lands deletionPolicy: Delete in the surviving side's manifest, but the two steps below git rm the failed side's chain-<a-or-b>/ and the closing line says Flux prunes the SeiNetwork on the failed side. The network whose policy decides whether its validators are orphaned is the one being removed, so the gate belongs there; 'the failed side needs the same read' leaves the load-bearing case as a secondary check. The verb is correct — only the side needs swapping.

[seidroid]

review found nothing blocking.

Superseded: the latest review found nothing blocking in this change.

[seidroid]

What changed

The pull request moved to merge commit bc0c799; the diff is 1355 lines, and the delta from the revision I reviewed last touches only cluster-inspection-recipes.md and teardown.md (+184/−40).

My blocker is closed, though not by the fix I proposed. The namespace procedure still inherits $chains and $VERDICT across the merge wait, but a new sweep_residual now runs at the end of every namespace teardown: it lists PVCs, Jobs and ConfigMaps in the namespace, excludes the imported claims by name, and returns 1 for anything left over. That closes the path I described — a fresh shell with an empty $chains now still runs the unlabelled CR/pod check and the residual sweep, so a leaked claim or a lingering SeiNode fails the run instead of passing it, and a legitimately imported claim produces a false alarm rather than a false clear. The discovery step's transformations are now checked too (grep exit 1 distinguished from a real failure, sort status read), so the || true that could have manufactured an empty chain list is gone. Two smaller hardenings came with it: the library no longer installs a source-time EXIT trap or a shared temp dir — verify_teardown and sweep_residual are subshell functions owning their own mktemp -d and traps, with INT/TERM re-raising 130/143 and a catch-all verdict branch so an interrupt cannot end the run silently — and the orphan sweep separates the API read from the jq parse, so a failed read no longer reads as "no orphans". The remaining consequence of the shell assumption is narrower than blocking and is listed below.

Nothing new blocks.

1. Blocking

None.

2. Non-blocking

• references/teardown.md:380 still assumes steps 4-5 run in the same shell as step 1, across a PR merge wait. In a fresh shell $chains is empty, so the per-chain loop runs zero times and the summary at :417 prints "every chain verified" having verified none; the residual sweep keeps that from hiding a leak, but expect_present is skipped, so an imported claim that was wrongly deleted goes unreported, and the message overstates what ran. Re-deriving $chains from the ./teardown-inventory-* directories at the top of step 4 would remove the assumption.
• SKILL.md:272 still names poll_gone / expect_present / record while recipe chore(agents): add Output Discipline section to all agents #9 now makes verify_teardown and sweep_residual the entry points and says not to copy pieces of it.
• references/teardown.md:284 and :344 instruct . ./verify-lib.sh, which does not exist in references/; the reader must create it from the fenced block, which is the copy step the consolidation exists to remove.
• SKILL.md:265 inventories with a bare kubectl get pvc -n eng-<alias> and produces none of the named-claim files step 9 consumes.
• sweep_residual treats every ConfigMap except kube-root-ca.crt as a residual, so any other platform- or mesh-injected ConfigMap in eng-<alias> reports as leftover.
• references/teardown.md:409 truncates ./expected-survivors.txt with : > without checking that write, though the later appends into it are checked.
• The inventory's node-to-claim attribution still depends on a pod's first owner reference name equalling the SeiNode name; it fails safe, but if the controller's StatefulSet naming differs, inventory.sh exits 2 for every chain and the documented teardown cannot complete.
• references/comparative-bench.md:429 gates the surviving side while the steps it prefixes remove the failed side, which is the side whose policy decides whether validators are orphaned.
• references/teardown.md:3 still states the governing rule as "patch spec.deletionPolicy to Delete", which :67 closes off for any Flux-owned SeiNetwork.
• references/teardown.md:593 prescribes kubectl --context harbor delete seinetwork|seinode, but SKILL.md:381's confirmation taxonomy gates only seictl network|node delete.
• references/teardown.md:26 asserts "exactly three" immutability rules while the PR body says four and seinetwork-crd.md:38 names two.
• "Render new chains with Delete from the start" (references/teardown.md:81-90) is still the only preventive step and still sits in the teardown-time file; the spinup procedure is untouched.
• The Delete enum literal remains uncited in this repo, and the PR body's "inferred rather than verified" list still omits it.
• references/teardown.md:578 asserts gp3-10k-750, gp3, and gp3-archive and their reclaim policies with none of the unverified marking the file gives its other inferences.
• The orphan check's follow-up at references/teardown.md:470 still runs kubectl get seinetwork <seinetwork-label-value> against the - placeholder the jq emits when the sei.io/seinetwork label is absent.

3. Summary

The residual sweep is the right answer to the blocker I raised: rather than patch the shell-continuity assumption, it added the check that can contradict "the namespace is empty" — leftover claims, Jobs and ConfigMaps, with imported claims excluded by name — so the verdict no longer rests on a per-chain loop having run. With the discovery transformations now status-checked, the library's traps confined to subshells, and the orphan sweep's read separated from its parse, I have no blocking findings left; what remains are accuracy and consistency notes, chiefly that the namespace summary line still claims every chain was verified when the loop may have run zero times, and that SKILL.md still points at the sub-helpers rather than the entry points. Approving with those. Codex contributed no reading this dispatch — it reported reading no diff — so nothing was carried over or dropped from it here. The repository has no REVIEW.md on main.

_{seidroid review · decision approve · session 9e5542c4a82248afa23681c6eda59b44 · turn resp_claude_0ec6a439d7a236daa6e32b76554b3ac4 · item 5b65dfec44c950c5a2f1f719a2d02716}

Findings: 0 blocking | 15 non-blocking | 3 posted inline | 1 pre-existing

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 4 total unresolved issues (including 3 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 604b772. Configure here.}

[cursor]

EXIT trap zeros verifier status

High Severity

Converting verify_teardown and sweep_residual to subshell functions means return now exits a subshell and runs trap 'rm -rf …' EXIT. On dash (the documented target), that cleanup’s status replaces the function’s, so PRESENT or UNVERIFIED becomes 0. Callers then record a pass and report the teardown verified while objects or a failed read remain.

Additional Locations (1)

• .claude/skills/harbor-dev/references/cluster-inspection-recipes.md#L390-L435

 

^{Reviewed by Cursor Bugbot for commit 604b772. Configure here.}

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 589 in d0ca249

| Volume → PV → PVC whose claim is gone, PV `Released` | **Unresolved candidate.** Platform review required. Report the PV, PVC name, and reclaim policy; do not act on it here. |

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is told'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 595 in d0ca249

Only the first two rows are verdicts. Every other row is an escalation, and the platform team is told which row it came from.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 597 in d0ca249

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is namespaced'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 597 in d0ca249

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 597 in d0ca249

`kubectl get pv` is cluster-scoped and the per-engineer Role is namespaced, so `Forbidden` at hop 1 is the **normal** case for an engineer — an unresolved result, not a clean one. When it happens, hand the volume IDs to the platform team and let them walk the chain; do not substitute the tag data for the walk.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 609 in d0ca249

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 609 in d0ca249

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 618 in d0ca249

**Never delete an EBS volume from this skill.** Even a volume the ownership walk resolved to a dead PVC goes to the platform team: `ec2:DeleteVolume` is outside the engineer's policy, the walk can be wrong, and an EBS delete is unrecoverable. Hand over the volume IDs, sizes, creation times, and the walk's verdict per volume — including every `UNRESOLVED` one, labelled as unresolved. Escalate through `#harbor-onboarding`. Do not report the cleanup as complete while any ID is outstanding.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 622 in d0ca249

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 622 in d0ca249

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 635 in d0ca249

**Every namespace-scoped command above names its namespace, and every destructive one names its context.** An unqualified `delete` deletes wherever the shell happens to point, and that is not a typo you can retry — it is a delete in the wrong place.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 43 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 639 in d0ca249

**No `seictl` alternative for network or node deletion belongs here, guarded or otherwise.** A `kubectl config current-context` check reads mutable state rather than pinning the config the delete then consumes, so it leaves a window between the check and the call — and it buys nothing, because `kubectl --context harbor delete` does the same deletion against the same CR with no window at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 641 in d0ca249

Should some genuinely `seictl`-only destructive verb ever need documenting, the pin belongs on the invocation: hand it a kubeconfig that contains the harbor cluster and nothing else, via `--kubeconfig <harbor-only-file>` (a documented `seictl` flag). A file that cannot name another cluster cannot select one. Do not substitute a current-context check.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 645 in d0ca249

Before deleting anything imperatively, prove the object is **not** in the workspace repo. A search that fails must never read as "no manifest found" — `grep` exits 1 for no match and 2 or more for an error, and an unreadable or stale clone produces the same empty output as a genuinely absent manifest.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 47 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 661 in d0ca249

**Only exit status 0 from this block authorizes a direct delete.** Every branch used to end in a successful `echo`, so the block's own status was 0 whatever it found — a scripted caller could not tell "not in git" from "the search failed", which is the same class of defect as counting lines without reading an exit status. `1` routes to the PR path; `2` means the question was never answered.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 668 in d0ca249

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 668 in d0ca249

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 669 in d0ca249

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 670 in d0ca249

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 672 in d0ca249

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 65 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 42 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are handled'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are held'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'very' is a weasel word!

[github-actions]

⚠️ [vale] <write-good.Weasel> _{reported by reviewdog 🐶}
'usually' is a weasel word!

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'are reported'. ASD-STE100 asks for the active voice.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ******'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 613 in 2218e68

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 613 in 2218e68

The node's finalizer deletes its data PVC, and the `Delete` reclaim policy on `gp3-10k-750` (validators) and `gp3` (default) releases the EBS volume. `gp3-archive` is `Retain` by design — a volume on that class stays after its PVC goes, and its removal is an AWS-side decision, not a mistake to correct here.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 33 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 622 in 2218e68

**Never delete an EBS volume from this skill.** Even a volume the ownership walk resolved to a dead PVC goes to the platform team: `ec2:DeleteVolume` is outside the engineer's policy, the walk can be wrong, and an EBS delete is unrecoverable. Hand over the volume IDs, sizes, creation times, and the walk's verdict per volume — including every `UNRESOLVED` one, labelled as unresolved. Escalate through `#harbor-onboarding`. Do not report the cleanup as complete while any ID is outstanding.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 30 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 626 in 2218e68

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is left'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 626 in 2218e68

Deleting an orphaned SeiNode is the one cleanup with a paved road. The rest of what a workspace PR leaves behind needs its own handling, so nothing in the [what a workspace-repo PR removes](#what-a-workspace-repo-pr-removes) list is left with no next step:

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 639 in 2218e68

**Every namespace-scoped command above names its namespace, and every destructive one names its context.** An unqualified `delete` deletes wherever the shell happens to point, and that is not a typo you can retry — it is a delete in the wrong place.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 43 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 643 in 2218e68

**No `seictl` alternative for network or node deletion belongs here, guarded or otherwise.** A `kubectl config current-context` check reads mutable state rather than pinning the config the delete then consumes, so it leaves a window between the check and the call — and it buys nothing, because `kubectl --context harbor delete` does the same deletion against the same CR with no window at all.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 31 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 645 in 2218e68

Should some genuinely `seictl`-only destructive verb ever need documenting, the pin belongs on the invocation: hand it a kubeconfig that contains the harbor cluster and nothing else, via `--kubeconfig <harbor-only-file>` (a documented `seictl` flag). A file that cannot name another cluster cannot select one. Do not substitute a current-context check.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 649 in 2218e68

Before deleting anything imperatively, prove the object is **not** in the workspace repo. A search that fails must never read as "no manifest found" — `grep` exits 1 for no match and 2 or more for an error, and an unreadable or stale clone produces the same empty output as a genuinely absent manifest.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 47 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 665 in 2218e68

**Only exit status 0 from this block authorizes a direct delete.** Every branch used to end in a successful `echo`, so the block's own status was 0 whatever it found — a scripted caller could not tell "not in git" from "the search failed", which is the same class of defect as counting lines without reading an exit status. `1` routes to the PR path; `2` means the question was never answered.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 672 in 2218e68

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 672 in 2218e68

- **The removal PR merged while a SeiNetwork still read `Retain`.** The cascade is gone and no patch restores it. Do not re-apply the SeiNetwork to "reattach" the children — a fresh network under the same chain-id wedges at height 0 on the burned genesis artifacts. Go straight to [Find and clean up already-leaked resources](#find-and-clean-up-already-leaked-resources).

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is ********'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 673 in 2218e68

- **`kustomization <alias>` is `NotFound` in `eng-<alias>`.** The engineer's Flux wiring is missing, so no workspace-repo merge reconciles at all. Surface to the platform team; do not create the Kustomization.

---

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 27 words. ASD-STE100 allows 25. Split it.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 674 in 2218e68

- **`lastAppliedRevision` does not reach the merge commit within two reconcile intervals (~10 min).** Read the Ready condition's message (`cluster-inspection-recipes.md` recipe #8). A render error in `engineers/<alias>/kustomization.yaml` — most often a `resources:` entry pointing at the dir that was just removed — blocks every later apply in the namespace, not only this teardown.

---

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is fixed'. ASD-STE100 asks for the active voice.

sei-internal-skills/.claude/skills/harbor-dev/references/teardown.md

Line 676 in 2218e68

- **A verification read returned `UNVERIFIED`.** The API call failed, so the teardown state is unknown. Report it as unknown — never as verified-gone, and never as still-present. Re-run once the access problem is fixed; a teardown with an unverified check is not a finished teardown.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 29 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was written'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'was corrected'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 39 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'were deleted'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is gone'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is told'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 28 words. ASD-STE100 allows 25. Split it.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-Passive> _{reported by reviewdog 🐶}
Passive voice: 'is namespaced'. ASD-STE100 asks for the active voice.

[github-actions]

⚠️ [vale] <AgenticWriting.STE-SentenceLength-Description> _{reported by reviewdog 🐶}
Descriptive sentence has 26 words. ASD-STE100 allows 25. Split it.