chore: add project context memory for hightower

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-21 06:43:50 -04:00
parent 2f1674ced9
commit 827492c5eb
2 changed files with 17 additions and 0 deletions
@@ -1,3 +1,4 @@
# Memory Index
- [project_hightower.md](project_hightower.md) — Hightower project context (custom Shannon deployment, naming conventions, MiniMax LLM)
- [reference_arc_runners.md](reference_arc_runners.md) — ARC self-hosted runners in farhoodliquor K8s cluster (`runners-farhoodliquor`)
@@ -0,0 +1,16 @@
---
name: Hightower project context
description: Hightower is a custom deployment of Shannon (upstream pentest agent) with K8s API server, Flux GitOps, and MiniMax LLM provider
type: project
---
Hightower is farhoodliquor's custom deployment of Shannon (upstream KeygraphHQ/shannon). The GitHub repo is `farhoodliquor/hightower`.
**Why:** The upstream Shannon CLI is Docker-based. Hightower adds a K8s-native REST API server, Flux GitOps deployment, and targets MiniMax as the LLM provider instead of Anthropic.
**How to apply:**
- The worker image (`ghcr.io/farhoodliquor/shannon`) is intentionally kept as a clean fork of upstream for easy backporting. Don't modify the worker package unless necessary.
- Custom components use the `hightower-*` prefix (API server, credentials, workspaces PVC, Temporal, worker jobs).
- Upstream Shannon names are preserved where they refer to the upstream codebase: `@shannon/worker` package, `.shannon/` directories, the worker Docker image.
- Namespace is `hightower`, managed by the cluster repo (`cpfarhood/kubernetes`), not this repo.
- LLM provider is MiniMax via `ANTHROPIC_BASE_URL` + `ANTHROPIC_AUTH_TOKEN` (custom base URL mode).