chore: archive v1.0 milestone

.planning/STATE.md

@@ -5,19 +5,24 @@
 See: .planning/PROJECT.md (updated 2026-06-14)
 
 **Core value:** Agent must NEVER mutate real infrastructure beyond what the limited IAM role permits
-**Current focus:** Phase 1 — Hermes Install & Provider Setup
+**Current focus:** Phase 4 — Skills & Integrations (final phase)
 
 ## State
 
-- **Status**: initialized
-- **Current phase**: none (ready for Phase 1)
-- **Last action**: Created PROJECT.md, REQUIREMENTS.md, ROADMAP.md
-- **Next action**: Execute Phase 1 — install Hermes, configure providers, Docker, AWS
+- **Status**: Phase 1-3 complete, Phase 4 skills created
+- **Current phase**: Phase 4 (Jira API token pending user setup)
+- **Last action**: Created custom skills (aws-diagnostics, jira-query, confluence-search, bitbucket-pr)
+- **Next action**: User sets JIRA_API_TOKEN, then all 22 requirements are met
+
+## What's Running
+- Hermes v0.16.0 CLI (Bedrock + OpenRouter fallback)
+- Telegram gateway (launchd service, PID in logs)
+- Docker terminal backend (config + SSO cache mounted)
+- 4 custom ngn-agent skills registered
 
 ## Notes
-
-- User picked Hermes Agent over NanoClaw after our research
-- Docker terminal backend for isolation
-- Limited AWS SSO role via project-local `./.aws/`
-- Bedrock primary → OpenRouter fallback
-- GSD config: yolo mode, coarse granularity, sequential execution
+- .aws/config: mounted ro, SSO cache: mounted rw
+- ngn-* scripts at ~/.hermes/scripts/ mounted to /usr/local/bin:ro in Docker
+- JIRA_EMAIL and JIRA_API_TOKEN forwarded into Docker via docker_forward_env
+- Telegram paired user 474440517 (Bapung)
+- Research docs: 7 files in .planning/research/hermes/