Skip to content

chore: delete archive graveyards - #1402

Merged
Aviator-Coding merged 1 commit into
mainfrom
fm/homeops-archive-tree-deletion
Aug 23, 2026
Merged

chore: delete archive graveyards#1402
Aviator-Coding merged 1 commit into
mainfrom
fm/homeops-archive-tree-deletion

Conversation

@Aviator-Coding

Copy link
Copy Markdown
Owner

Intent

Delete both archive graveyards: .archive/ (57 files, 2390 lines) and .github/archive/ (5 files, 5 files total). Pure deletion PR with no other changes. Git history remains as the archive for recovered reference. Re-verified zero inbound references across entire codebase before deletion.

What Changed

  • Removed the entire .archive/apps/ tree: retired manifests for ai-system/agentgateway, ai-system/grafana-mcp, gaming/filebrowser, gaming/space-engineers-ds (including its volsync instances/plugins subtrees), and openclaw (homeops-claw, my-claw, operator) - 57 files.
  • Removed the entire .github/archive/ tree: retired GitHub Actions workflow files flux-local.yaml, labeler.yaml, pre-commit.yaml, pre-pull-images.yaml, and test-runner.yaml - 5 files.
  • No other files were added or modified; this is a pure deletion of 62 files (3134 lines) with the removed content preserved in git history.

Risk Assessment

✅ Low: Pure, verified deletion of two orphaned archive directories with zero remaining inbound references and no changes outside those paths - matches stated intent exactly.

Testing

This is a non-UI, pure-deletion housekeeping change (removing two orphaned archive directories), so there is no rendered surface or unit-testable code path to exercise; the appropriate evidence is structural verification of the diff and reference-freedom, which was performed directly against git and the filesystem. The diff between base and target commits is confirmed to be exactly 62 file deletions (57 in .archive/, 5 in .github/archive/) with no other changes, and a full-tree search (both at the target commit and retroactively at the base commit) turns up zero references to either deleted path anywhere in the remaining codebase, confirming the stated intent (pure deletion, zero inbound references) is satisfied with no regressions.

Evidence: git diff --name-status (base -> target): all 62 changes are deletions, split 57/.archive + 5/.github-archive
$ git diff --name-status 12b2a76a...0ce15b1d | wc -l
62
$ git diff --name-status ... | grep '^D\s\.archive/' | wc -l
57
$ git diff --name-status ... | grep '^D\s\.github/archive/' | wc -l
5
$ git diff --name-status ... | awk '$1!="D"'
(empty - no non-delete changes)
Evidence: Full-tree grep for inbound references to .archive/.github-archive at target commit: zero hits
$ grep -rn "\.archive" --exclude-dir=.git .
(no output)
$ grep -rn "github/archive" --exclude-dir=.git .
(no output)
$ ls .archive .github/archive
ls: .archive: No such file or directory
ls: .github/archive: No such file or directory

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

  • git diff --stat 12b2a76a45986c7165b157ecbb44fc16d3267752 0ce15b1d05499df7a4aea4fcdba3d4cc41420cf7
  • git diff --name-status 12b2a76a45986c7165b157ecbb44fc16d3267752 0ce15b1d05499df7a4aea4fcdba3d4cc41420cf7 (verified all entries are 'D', counted 57 under .archive/ and 5 under .github/archive/)
  • grep -rn "\.archive" --exclude-dir=.git . (target commit, post-deletion tree)
  • grep -rn "github/archive" --exclude-dir=.git . (target commit, post-deletion tree)
  • git grep -n "\.archive" 12b2a76a45986c7165b157ecbb44fc16d3267752 -- . ':!.archive' (base commit, confirms no prior inbound references)
  • git grep -n "archive/" 12b2a76a45986c7165b157ecbb44fc16d3267752 -- .github ':!.github/archive' (base commit)
  • ls .archive .github/archive (confirmed absent post-deletion)
  • grep -n "archive" .gitignore .pre-commit-config.yaml .renovaterc.json5 (no stale references to clean up)
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

Remove .archive/ (57 files, 2390 lines) and .github/archive/ (5 files).
Git history remains the archive for recovered reference.
@mortyops mortyops Bot added the area/github label Aug 23, 2026
@Aviator-Coding
Aviator-Coding merged commit 585f728 into main Aug 23, 2026
1 check passed
Aviator-Coding added a commit that referenced this pull request Aug 26, 2026
…ference

Per captain follow-up: the ExternalSecret's 1Password item/field
(grafana-mcp / GRAFANA_SERVICE_ACCOUNT_TOKEN) is not a new design - it is
the exact same reference the original grafana-mcp deployment used before
it was archived and later deleted from Git (#1402). 1Password items are
independent of Git history, so that item may already exist with a valid
Viewer-scoped token. No grafana-operator or other declarative SA-token
minting path exists in this repo's plain grafana/grafana Helm deployment
(no operator, no usable token field in grafana's own ExternalSecret), so
there is no smaller mechanism to prefer over this reused reference.
Aviator-Coding added a commit that referenced this pull request Aug 26, 2026
* feat(ai): deploy mcp-grafana in-cluster and register with toolhive gateway

Restores the Grafana MCP tool server per captain decision D5 (grafana runs
in our cluster). Deploys docker.io/grafana/mcp-grafana as a toolhive
MCPServer in the ai namespace, pointed at the in-cluster grafana.monitoring
service, and registers it into the existing mcp-tools MCPGroup so federated
agents can reach it through the MCP gateway again.

Per captain decision A6, the Grafana token must be a Viewer-scoped service
account token; --disable-write is set as defense-in-depth on top of that
RBAC scope. The ExternalSecret expects a new 1Password item `grafana-mcp`
with field `GRAFANA_SERVICE_ACCOUNT_TOKEN` (not yet created).

* no-mistakes(review): Allow ToolHive Host on grafana-mcp

* no-mistakes(document): Point MCP inventory docs at kustomization

* docs(ai): clarify grafana-mcp secret reuses the pre-existing vault reference

Per captain follow-up: the ExternalSecret's 1Password item/field
(grafana-mcp / GRAFANA_SERVICE_ACCOUNT_TOKEN) is not a new design - it is
the exact same reference the original grafana-mcp deployment used before
it was archived and later deleted from Git (#1402). 1Password items are
independent of Git history, so that item may already exist with a valid
Viewer-scoped token. No grafana-operator or other declarative SA-token
minting path exists in this repo's plain grafana/grafana Helm deployment
(no operator, no usable token field in grafana's own ExternalSecret), so
there is no smaller mechanism to prefer over this reused reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant