Repository navigation
Tags
Tags
Move to Go 1.26.10 and x/net v0.60.0 to clear govulncheck findings (#50) govulncheck reported 9 reachable vulnerabilities in net/http, net/textproto and crypto/tls (fixed in go1.26.9) and in x/net's HTTP/2 code (fixed in v0.60.0). Bump the go directive, toolchain and the Docker builder images to 1.26 so the shipped binaries pick up the fixes. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Fix flaky ReleaseSupervisorWaitErrorShutdown test (#40) Replace the 1ms timing-based wait with m.Shutdown, which blocks until the background release goroutine has destroyed the supervisor. Same fix as fbea617 applied to the sibling OnDestroy test. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Feature/chat (#29) * Added Chat API scaffolding, including routes, handlers, middleware, and data structures * Refactored muEd into evaluate and chat * Added tests for chat * Implemented chat functionality, added request/response handling, and comprehensive tests for `ServeChat` and `ServeChatHealth`. * Added OpenAPI request/response validation middleware and integrated OpenAPI specification * Add embedded µEd OpenAPI specification Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Move µEd OpenAPI spec into runtime/schema Relocates the spec from api/ into runtime/schema/ alongside the existing JSON schema files, and renames it to mued_v0.1.0.yml to make the version explicit. Removes the api/ package; embed is now owned by runtime/schema. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Ignore .idea/ directory Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Make OpenAPI response validation strict for µEd routes Previously, responses that failed spec validation were only logged as warnings and forwarded anyway. Now a failed µEd response validation returns 500 to the caller. The legacy / route is unaffected — it has no matching path in the spec so the middleware passes it through unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add X-Api-Version header support to chat handlers Chat passes the µEd ChatRequest directly to workers (no legacy conversion). Adds checkMuEdVersion to reject unsupported API versions with 406, and sets the X-Api-Version response header on all /chat and /chat/health responses. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Removed unused µEd version handling logic and added ChatRequest/ChatResponse structs. * Add `Chat` and `ChatHealth` methods to `Runtime` interface and implementations. * Refactor chat and chat health handlers to use `Chat` and `ChatHealth` methods directly, removing legacy `Handle` logic. Update tests accordingly. * Replace direct `http.Error` calls with `writeMuEdError` utility in chat and chat health handlers for consistent error handling. * Return 503 status code when ChatHealth status is "UNAVAILABLE" and add corresponding test. * Add `chat` and `chat/health` command mappings to `Runtime` * Refactor chat data structures for µEd spec compliance Refactor `MuEdChatRequest`, `MuEdChatResponse`, and related health structures for compatibility with µEd spec. Replace typed fields (`user`, `context`, etc.) with freeform maps to ensure full data fidelity. Simplify worker response validation and default handling. Add regression tests to verify unaltered data passthrough. * Rename `CommandHealth` to `CommandEvaluateHealth` for consistency with function naming and improved clarity --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Fix Docker image not pushing on tag refs The push condition was missing the ref_type != 'tag' guard, causing the image to be built but not pushed when a version tag is created. Also enable QEMU for tag builds to restore multi-arch (arm64) support. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>