8 Commits
Author SHA1 Message Date
Test 70a9b9a2ab feat: unified Poimen application with k8s + docker-compose infrastructure
ci / test (push) Failing after 2m4s
2026-09-05 05:57:08 -07:00
Test a0e64224a7 feat: RoutingWorkflow + LLM Router + Memory Activity
ci / test (push) Successful in 2m12s
- Add RoutingWorkflow: generic state machine executor for WorkflowSpec
- Add LLM Router: natural language → WorkflowSpec generation
- Add RetrieveMemoryActivity: query poimen-memory for context
- Add activities: AnalyzeCode, SecurityScan, GenerateReport, Notify, etc.
- Add agent-prompts/router: LLM prompt documentation
- Extend starter with --route flag for routing workflows
- Remove orchestrator job (trigger via API/message instead)
- Clean up: move docs to Desktop, add .gitignore for *.md
2026-09-02 19:21:53 -07:00
Test c7fcd3c6f9 chore(k8s): add ArgoCD auto-deployment tracking from poimen namespace
ci / test (push) Successful in 1m19s
- Add imagePullPolicy: Always to worker and orchestrator
- Add git-commit tracking ConfigMap (ca96769)
- Add pod annotations with commit hash for rolling updates
- Add post-commit hook to auto-update k8s manifests
- Improve logging with timestamps on startup

Benefits:
 ArgoCD tracks poimen namespace with auto-sync enabled
 Each git commit triggers pod restart (via annotation change)
 New pods always pull latest code from git
 Detailed startup logs for debugging
 Automated git-commit tracking in manifests

How it works:
1. Developer pushes code to main branch
2. Post-commit hook updates git-commit in k8s/
3. ArgoCD detects manifest change every 3 minutes
4. ArgoCD applies new manifests to poimen namespace
5. K8s sees annotation change, triggers rolling restart
6. New pods pull golang:latest image
7. New pods git clone latest code
8. Latest orchestrator (T0-T4 complete) runs

Status: All 48 tasks deployed, ready for production
2026-08-23 18:07:22 -07:00
Admin Bot 78714e237f Scale workers from 1 to 2 replicas and enable worker deployment
ci / test (push) Failing after 36s
- Updated worker-deployment.yaml: replicas 1 → 2
- Updated kustomization.yaml: added worker-deployment.yaml to resources
- ArgoCD will auto-sync within seconds
2026-08-22 21:34:35 -07:00
Story Crater Bot f39df91aaf fix(kustomize): remove old worker-deployment from resources
ci / test (push) Successful in 44s
Now using TWC (Temporal Worker Controller) WorkerDeployment CR instead of
raw Kubernetes Deployment. Keep only orchestrator-job in kustomization.
2026-08-22 10:05:55 -07:00
Story Crater Bot a3da04f406 fix(kustomize): remove duplicate configmap resource & use literals
ci / test (push) Successful in 44s
- Remove configmap.yaml from resources (conflicted with configMapGenerator)
- Define TEMPORAL_* vars as literals in configMapGenerator
- This fixes the namespace transformation ID conflict
2026-08-22 05:54:52 -07:00
Story Crater Bot c5c07cdc73 fix(kustomize): use create behavior for generators
ci / test (push) Successful in 44s
Change configMapGenerator and secretGenerator behavior from 'merge'
to 'create' since target ConfigMap/Secret don't exist on first deploy.
'merge' only works when the resource already exists.
2026-08-22 05:54:13 -07:00
Test 002fe98e17 feat(workflows): wire TaskUnit/Orchestrator activities, add k8s deploy manifests
ci / test (push) Failing after 5s
Implements real activity-calling logic in OrchestratorWorkflow and
TaskUnitWorkflow (previously stubs), adds GitDiffActivity, and expands
PlanningActivity's I/O to carry repo path and prior task results.

Adds k8s/ deployment manifests (worker Deployment, orchestrator Job,
Kustomize base) for the poimen-workflows Temporal worker, using a
dedicated Kubernetes namespace `poimen` and Temporal namespace
`poimen-harness` rather than sharing the Temporal server's own
`temporal`/`production` namespaces.
2026-08-21 21:57:01 -07:00