6.4 KiB
6.4 KiB
Elydora Go SDK Engineering Contract
Scope
This repository owns the public Go SDK, the cmd/elydora CLI, local signing behavior, generated Node.js hook runtimes, and Go-specific agent adapters.
Integration Sources
- Verify every agent hook contract against current official provider documentation before changing an adapter.
- Treat
../Elydora-Open-Source/integrations/catalog.jsonas the cross-product provider inventory. - Keep adapter delivery claims aligned with executable tests in this repository.
- Synchronize completed provider behavior into the Node SDK, Python SDK, Open Source distribution, Console, Docs, and landing page through separate reviewed commits.
Hook Adapter Invariants
- Preserve unrelated user configuration and remove only Elydora-owned entries.
- Parse every affected user configuration before the first write.
- Surface malformed or unreadable configuration with contextual errors and leave the original file intact.
- Write configuration through a same-directory temporary file, flush it, and atomically replace the target.
- Resolve and quote the Node.js runtime and generated script paths for the host shell.
- Forward official hook JSON from STDIN without reshaping provider fields.
- Use the provider's documented blocking mechanism. Command-hook providers that define exit code
2must receive exit code2from the freeze guard. - Report installation as healthy only when a complete hook contract references both generated runtime scripts and both scripts exist.
- Write Cursor hooks only to
~/.cursor/hooks.json; keep project and enterprise sources read-only. Preserve user hooks, migrate the prior versionless Elydora contract, audit successful and failed tool calls, emit valid native JSON responses, retain PowerShell exit codes, and commit guard, runtime metadata, private key, audit runtime, and user hooks in one rollback-capable transaction. - Model stable, legacy, and early-access hook generations as explicit contracts. Keep their activation requirements visible in CLI output and README guidance.
- Select Kimi Code and legacy
kimi-clicontracts from runtime evidence. An emptyKIMI_CODE_HOMEuses~/.kimi-code; create no cross-runtime migration marker. - Preserve Kimi TOML comments and unrelated formatting through range-based edits, then parse the complete rendered document before writing it.
- Keep Grok Build writes inside its native global
$GROK_HOME/hooks/*.jsoncontract. Treat Claude Code and Cursor compatibility files plus project.grok/hooksas read-only integration sources. - Write Auggie hooks only to
~/.augment/settings.json; keep system and workspace settings read-only. Generate.cmdwrappers on Windows and.shwrappers on Unix because Auggie dispatches supported script paths, and express hook timeouts in milliseconds. - Write Cline hooks only to
$CLINE_DIR/hookswith~/.cline/hooksas the default; keep Documents and workspace hook roots read-only. Preserve official input byte-for-byte and translate guard exit code2into Cline's JSON stdout cancellation control. - Write GitHub Copilot CLI hooks only to
$COPILOT_HOME/hooks/elydora-audit.jsonwith~/.copilot/hooks/elydora-audit.jsonas the default. Migrate exact Elydora-owned entries from project.github/hooks/hooks.json, preserve native camelCase input, requiredisableAllHooksto be false, and commit runtime plus hook documents in one rollback-capable transaction. - Factory Droid
droid@0.175.0reads direct event maps from~/.factory/hooks.jsonor the legacy~/.factory/hooks/hooks.json;~/.factory/settings.jsonstores the same map underhooks. Select the active source per event, preserve JSONC syntax, and direct users to/hooksfor review. - Commit Factory Droid runtime config, private key, audit runtime, and affected hook documents in one rollback-capable transaction. Status requires an enabled
PreToolUse/PostToolUsepair with matching managed runtime files. - Qwen Code
0.20.0loads user hooks from$QWEN_HOME/settings.jsonwith~/.qwen/settings.jsonas the default; follow Qwen's.envprecedence and keep workspace settings read-only. Preserve comments, reject trailing commas and duplicate keys, express timeouts in milliseconds, and direct users to/hooksfor review. - Commit Qwen Code runtime config, private key, audit runtime, and user settings in one rollback-capable transaction. Status requires enabled
PreToolUseandPostToolUsehooks with matching managed runtime files.
Code Quality
- Preserve the minimum Go version declared in
go.mod. - Keep production source files at or below 500 lines.
- Keep functions focused on one ownership boundary.
- Return unexpected errors to the CLI boundary with operation and path context.
- Use documented defaults only for genuinely optional configuration.
- Avoid compatibility shims without a named public or user configuration contract.
- Resolve every agent runtime directory as one physical child of
~/.elydora; reject separators, traversal segments, cross-platform reserved names, symbolic-link directories, and linked identity configs before writes or recursive removal. Validate stored directory identity before changing host CLI configuration, and require an explicit agent ID when discovery is ambiguous. - Accept CLI install credentials through terminal-echo-disabled input or physical owner-only credential files. Keep credentials out of process arguments, reject legacy secret options with redacted errors, and require one UTF-8 line of at most 64 KiB.
- Commit runtime config, private key, and audit script through one rollback-capable transaction. Persist the signing key once with mode
0600; generated runtimes validate physical identity, size, and Unix permissions before reading config or key material. - Write the guard runtime through a flushed same-directory temporary file followed by atomic replacement. Surface permission, close, synchronization, commit, cleanup, and recovery failures.
Verification
Run the focused adapter test during development, then execute all release gates before commit:
go test ./cmd/elydora/plugins -run <Provider> -count=1
go test ./...
go test -race ./...
go vet ./...
go build ./cmd/elydora
govulncheck ./...
git diff --check
Provider adapter tests must cover installation, idempotency, official event forwarding, blocking behavior, status, missing runtime files, uninstall ownership, and malformed configuration preservation.
Commit and push one root issue before starting the next one.