docs: neutralize stale incident references

Author: bigboateng

boatstack/compiled_artifact_resolution_test.go

@@ -49,7 +49,7 @@ func TestFeatureEvidencePathResolvesBothLayouts(t *testing.T) {
 }
 
 // TestRecordGateResolvesCompiledEvidenceLedger is the proof of fix: a delivery whose
-// ledger lives ONLY at compiled/evidence.md (the taxweave state) must gate cleanly
+// ledger lives ONLY at compiled/evidence.md (the legacy repository state) must gate cleanly
 // with no explicit --evidence. This fails on the pre-fix recorder, which resolved
 // only the feature root.
 func TestRecordGateResolvesCompiledEvidenceLedger(t *testing.T) {

boatstack/next_test.go

@@ -204,7 +204,7 @@ func TestFeaturePlanCandidatesExcludesLockedAndShippedFeatures(t *testing.T) {
 	}
 }
 
-// TestResolveNextIgnoresShippedFeatureCandidates reproduces the taxweave scenario
+// TestResolveNextIgnoresShippedFeatureCandidates reproduces the linked-worktree scenario
 // through ResolveNext: one genuinely open feature plus several shipped dirs whose
 // state.json was destroyed by worktree cleanup must resolve to the single open
 // candidate, not AMBIGUOUS.

boatstack/repair_state_test.go

@@ -7,7 +7,7 @@ import (
 	"testing"
 )
 
-// writeMalformedDraft models the taxweave-roles failure: an agent hand-authored a
+// writeMalformedDraft models a legacy failure: an agent hand-authored a
 // feature directory with a prose plan.md but never let the helper register it, so
 // there is no plan.lock.json and no delivery state. CheckPlan fails on it, which
 // the guard escalates to INVALID_STATE and denies every product mutation.

boatstack/runtime_cache.go

@@ -416,7 +416,7 @@ func HydrateWorktree(repoPath string) error {
 // Because the guard downloads and runs the exact pinned release before calling
 // this, the running binary equals the repo's committed pin by construction. The
 // verifyGeneratedRuntime gate refuses to populate a slot for any other version,
-// so hydration can never write a mislabeled runtime (the taxweave incident's
+// so hydration can never write a mislabeled runtime (the original incident's
 // invariant), and installCommandRuntime's own post-write verify+rollback is the
 // backstop. The operation is idempotent and safe under concurrent first use.
 func RunHydrateRuntime(repoPath string) error {

boatstack/visual_publisher_test.go

@@ -14,7 +14,7 @@ func TestOriginRepoSlugParsesSSHAndHTTPS(t *testing.T) {
 	repo := t.TempDir()
 	runGit(t, repo, "init", "-b", "main")
 	cases := map[string]struct{ owner, name string }{
-		"git@github.com:millennialcpa/taxweave.git":      {"millennialcpa", "taxweave"},
+		"git@github.com:example-org/sample-app.git":     {"example-org", "sample-app"},
 		"https://github.com/operatorstack/boatstack.git": {"operatorstack", "boatstack"},
 		"https://github.com/operatorstack/boatstack":     {"operatorstack", "boatstack"},
 	}

release-notes/2026-08-09-remove-stale-internal-notes.md

@@ -0,0 +1,3 @@
+### Stale internal incident notes are removed
+
+Boatstack no longer includes resolved internal incident notes or project-specific labels in its public source and test fixtures. Runtime behavior does not change.