briannadoubt

Update CHANGELOG.md with new entries following Keep a Changelog format

Run complete CI checks locally (build debug/release, run tests, check warnings)

Run the complete dev server test workflow for the Aura project

Rebuild the trebuchet CLI binary in release configuration

Create a new Trebuchet release tag following semantic versioning (without 'v' prefix)

Run AWS integration tests with LocalStack for local AWS service simulation

Run Trebuchet test suites using Swift Testing framework

Run UI tests for the Aura project to verify streaming functionality

AWS Lambda deployment with trebuchet CLI, DynamoDB state storage, CloudMap service discovery, WebSocket streaming via API Gateway, Lambda handler implementation, connection management, cost optimization, and production configuration. Use when deploying to AWS or implementing WebSocket realtime features.

Trebuchet CLI commands for initializing projects, deploying actors, checking status, local development, and infrastructure management. Use when users need to deploy, configure, or manage Trebuchet projects from the command line.

Serverless deployment architecture with CloudGateway, CloudProvider abstraction, ServiceRegistry, ActorStateStore, and local development setup. Use when users need to understand cloud deployment concepts or deploy actors to serverless platforms.

Best practices for defining distributed actors with @Trebuchet macro, method requirements, stateful actors, annotations, and error handling. Use when users need help structuring actors, managing state persistence, or understanding actor deployment configuration.

Installation, setup, and basic usage of Trebuchet distributed actors. Use when users need help starting a new Trebuchet project, creating their first actor, or understanding the fundamental server/client pattern.

Production-grade security with authentication (API keys, JWT), authorization (RBAC), rate limiting (token bucket, sliding window), request validation, and middleware integration. Use when securing actors, implementing access control, or preventing abuse.

Production-grade observability with structured logging, metrics collection (counters, gauges, histograms), distributed tracing, CloudWatch integration, and sensitive data redaction. Use when monitoring actors, debugging issues, or tracking performance in production.

Real-time state streaming with @StreamedState, @ObservedActor, stream resumption, filtering, and delta encoding. Use when users need automatic state synchronization, reactive UI updates, or bandwidth optimization for large state objects.

Plan, track, and report on multi-step work using the Scope kanban (local CLI + web UI). Use when the user asks you to scope/plan a project, list open work, mark a ticket done, link a branch/PR, or coordinate with other agents on shared state. Don't use for one-off questions or trivial single-edit requests.

Summarize the current Scope board, identify active work, and choose the next ticket. Use when starting a session, resuming work, or giving status.

Attach branches and PRs to Scope tickets and prepare handoff comments. Use when creating branches, opening PRs, finishing work, or handing work to another agent.

Coordinate multiple Codex agents working in one Scope workspace. Use when tasks are parallelized, handed off, blocked, or updated by several agents.

Break a user request into Scope epics, stories, and bugs before implementation. Use for feature work, refactors, investigations, and broad tasks that need visible progress.

Plan, track, and report multi-step work using Scope. Use when the user wants Codex to manage project state, open tickets, progress, bugs, branches, PRs, or agent coordination.

Create, edit, comment, link, prioritize, and close Scope tickets from Codex. Use when the user asks for ticket changes or when work progress should be recorded.

Implement and verify SwiftUI API parity for Raven UI components. Use when asked to audit missing or mismatched SwiftUI views/modifiers, add parity components, wire examples into `Examples/TodoApp`, validate rendering in a browser (including dark mode), and prepare branch/PR deliverables.

Create or extend Raven UI components and modifiers (rendering to VNode/DOM, wiring events, managing state), including JavaScriptKit interop guidelines (DOMBridge, JSClosure, @MainActor).

Generate and maintain deterministic SwiftUI-vs-Raven API parity reports and automation. Use when users ask to audit missing SwiftUI components/APIs, refresh coverage reports, reduce report noise, tune matching logic (owner-qualified names, constructors, operators), or update the weekly GitHub Actions PR workflow that publishes Reports/swiftui-api-gap/gap_report.md.

Raven development workflow for building, serving, testing, and debugging Swift WASM apps and Raven runtime changes.

Swift WASM development for setup, build, optimize, debug, and test workflows in Raven and related apps.

Swift WASM development with Swift 6.2 APIs. Use for setting up WASM toolchains, building for WebAssembly, optimizing bundles, debugging WASM apps, or troubleshooting Swift WASM issues.

Write, fix, or convert Rust in a project that uses Trust, the strict Rust dialect. Use when you see `cargo trustc` in build instructions, `[package.metadata.trust] strict = true` (or `[workspace.metadata.trust]`) in a Cargo.toml, a `#![strict]` inner attribute at the top of a .rs file, build errors with R-codes like R0042/R0001/R0014 (`error[R0042]: call to ... must use named arguments`), named-argument call syntax such as `f(width: 1920, height: 1080)`, the pipe operator `|>`, or `requires!(...)` preconditions in function bodies. Also use when asked to convert an existing crate to Trust or scaffold a new Trust project with `trust new`.

Run SurrealDB integration tests with automatic database setup and teardown. Starts SurrealDB if needed, runs tests with SURREALDB_TEST=1, and cleans up automatically.