guru-connect

azcomputerguru/guru-connect

Fork 0

Files

History

Mike Swanson 7ab87384a7

Build and Test / Build Server (Linux) (push) Failing after 3m42s

Details

Build and Test / Build Agent (Windows) (push) Successful in 7m39s

Details

Build and Test / Security Audit (push) Successful in 4m34s

Details

Build and Test / Build Summary (push) Has been skipped

Details

spec: add SPEC-009 feature-rich documented API

Everything the console does should be callable by API, documented and
discoverable. Adds: OpenAPI 3.x generated from code (utoipa) + Swagger/Redoc at
/api/docs (drift-proof, route<->spec parity test); long-lived revocable scoped
API tokens (connect_api_tokens, hashed like agent keys) distinct from the 24h
dashboard JWT and agent keys; an API-completeness gap audit (folds in SPEC-004/
006/007 endpoints); consistent pagination/filtering + versioning policy. Today
there is zero API doc tooling and no programmatic token. Depends on SPEC-008 for
the documented error envelope; distinct from the ADR-001 integration contract.
Large. Parallel guru-rmm SPEC-019. Requested by Mike 2026-05-30.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-30 16:35:57 -07:00

SPEC-001-operational-tooling-parity.md

feat: operational tooling — signing, versioning, changelog, roadmap (SPEC-001)

2026-05-29 07:19:29 -07:00

SPEC-002-v2-modernization-architecture.md

docs(spec): add SPEC-002 GuruConnect v2 modernization architecture

2026-05-29 18:08:23 -07:00

SPEC-003-machine-inventory.md

spec: add SPEC-003 full machine inventory in connection DB

2026-05-30 15:48:09 -07:00

SPEC-004-session-lifecycle-and-removal.md

spec: SPEC-004 add stable machine-derived identity as the primary fix