docs: spec-kit pilot for state-sync component#1309
docs: spec-kit pilot for state-sync component#1309jeremyeder wants to merge 1 commit intoambient-code:mainfrom
Conversation
Behavioral specification and development context for the state-sync sidecar, piloting spec-driven development before rolling out to ambient-runner. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
|
@jeremyeder this is an excellent extraction of the runner spec. It has all the config/params for the runner and backend APIs required by it. I think it would be useful to also specify the runtime of the runner itself. It has multiple threads internally, acting as source and sink. There are bridges to other models besides Claude. We'll add gRPC to the spec as well (when we merge back from alpha). |
Summary
components/runners/state-sync/spec/spec.md).claude/context/state-sync-development.md) following existing patternPilots spec-driven development on the smallest runner component before rolling out to ambient-runner.
Test plan
hydrate.shandsync.shsourcebackend-development.md🤖 Generated with Claude Code