Elydora-Go-SDK/AGENTS.md

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.json as 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 2 must receive exit code 2 from the freeze guard.
• Report installation as healthy only when a complete hook contract references both generated runtime scripts and both scripts exist.
• Resolve Codex user hooks through $CODEX_HOME/hooks.json with ~/.codex/hooks.json as the default and canonicalize configured existing directories. Preserve additive TOML, project, plugin, and managed sources. Register exact PreToolUse and PostToolUse match-all command groups, retain the native payload, propagate freeze and revocation through exit code 2, keep guard lookup and audit delivery fail-open with observable errors, and commit user hooks plus all four runtime artifacts through one rollback-capable transaction. Require /hooks approval for both definition hashes.
• 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 from an explicit KIMI_CODE_HOME or an existing ~/.kimi-code home, and select legacy kimi-cli from an existing ~/.kimi home. An empty KIMI_CODE_HOME uses ~/.kimi-code; executable lookup is outside the activation contract, and equal stable and legacy config paths collapse to the stable contract.
• Preserve Kimi TOML comments and unrelated formatting through range-based edits, then parse the complete rendered document before writing it. Own only exact three-field hooks for PreToolUse, PostToolUse, and PostToolUseFailure; require one complete triple per runtime identity, use encoded PowerShell commands on Windows, and retain the native snake_case payload.
• Generate Kimi guard, config, private key, and audit runtimes together with every selected TOML document in one rollback-capable transaction. Preflight physical paths and existing runtime identity before creating state; status validates the complete runtime metadata, canonical private key, exact agent identity, and non-empty physical scripts.
• Write Claude Code hooks only to $CLAUDE_CONFIG_DIR/settings.json with ~/.claude/settings.json as the default; keep project, local, managed, plugin, skill, and agent sources read-only. Validate the complete shipped handler schema, including command exec form, async rewake metadata, HTTP, MCP tool, prompt, and agent handlers. Preserve the native snake_case payload, own one exact matchless PreToolUse, PostToolUse, and PostToolUseFailure triple, propagate freeze and revocation through exit code 2, and treat disableAllHooks as an explicit installation and health gate.
• Generate Claude Code guard, config, private key, and audit runtimes with user settings in one rollback-capable transaction. Validate the full official event and handler schema before writes, migrate only the exact prior Go command contract, require strict runtime identity for health, and direct users to /hooks plus claude doctor for effective-source verification.
• Write Gemini CLI hooks only to $GEMINI_CLI_HOME/.gemini/settings.json with ~/.gemini/settings.json as the default. Keep workspace, system defaults, system override, and extension settings read-only. Preserve JSONC comments and line endings, reject trailing commas and duplicate keys, validate the official event and command-handler schema, and treat hooksConfig.enabled plus hooksConfig.disabled as installation and health gates.
• Own one exact matchless BeforeTool/AfterTool pair named elydora-guard and elydora-audit with 10,000 millisecond timeouts. Generate guard, config, private key, and native-payload audit runtimes with user settings in one rollback-capable transaction. Use encoded PowerShell commands on Windows, emit {} for successful hook execution, propagate frozen and revoked agents through exit code 2, require strict runtime identity for health, and direct users to /hooks list for effective-source verification.
• Keep Grok Build writes inside its native global $GROK_HOME/hooks/*.json contract. Treat project .grok/hooks, plugin hooks, Claude Code, and Cursor compatibility files as read-only integration sources. Own only exact matchless three-field command groups for PreToolUse, PostToolUse, and PostToolUseFailure; accept official non-negative integer timeouts and string-valued environments; reject lifecycle matchers; and preserve native camelCase payloads.
• Generate Grok guard, config, private key, and audit runtimes with the user hook document in one rollback-capable transaction. Use encoded PowerShell commands on Windows, emit native deny JSON with exit code 2, preflight physical paths and runtime identity, and require one exact event triple plus strict runtime metadata and a canonical private key for healthy status.
• Resolve Auggie user hooks through ~/.augment/settings.json; keep system, workspace, local workspace, and alternate --augment-cache-dir settings read-only. Validate the shipped Auggie 0.33 hook schema: PreToolUse, PostToolUse, Stop, SessionStart, SessionEnd, Notification, and PromptSubmit; regex matchers belong to tool events, command handlers use string-array arguments and positive millisecond timeouts, and metadata flags are booleans. Generate .cmd wrappers on Windows and .sh wrappers on Unix, preserve the complete native snake_case payload, and propagate freeze and revocation through exit code 2.
• Validate Auggie matcher syntax during installation with Node.js new RegExp; keep status and uninstall independent from matcher validation so recovery remains available offline. Commit Auggie settings, both wrappers, generated runtimes, runtime config, and private key through one rollback-capable transaction. Require exact runtime identity, canonical private keys, physical files, and exact wrapper sources during status checks, then verify the effective configuration with auggie tools list.
• Cline CLI 3.0.46 discovers exact PreToolUse and PostToolUse file basenames across ~/Documents/Cline/Hooks, $CLINE_DIR/hooks with ~/.cline/hooks as the default, workspace .clinerules/hooks, and workspace .cline/hooks; Elydora owns the $CLINE_DIR/hooks pair and keeps the other roots read-only. Commit both wrappers, generated guard and audit runtimes, strict config, and canonical private key through one rollback-capable transaction. Preserve official input byte-for-byte, emit pure JSON cancellation control for guard exit code 2, reject linked managed paths, and require exact generated sources plus runtime identity for healthy status. Cline surfaces hook errors and continues the task, so wrapper stderr and runtime error.log are operational evidence.
• Write GitHub Copilot CLI hooks only to $COPILOT_HOME/hooks/elydora-audit.json with ~/.copilot/hooks/elydora-audit.json as the default. Keep repository, Claude-compatible, inline, plugin, and policy hook sources additive; migrate only exact Elydora-owned entries from project .github/hooks/hooks.json. Resolve disableAllHooks through legacy user config, user settings, Claude repository settings, and Copilot repository settings in official precedence order; settings accept JSONC and trailing commas, while hook documents remain strict JSON.
• Validate the complete GitHub Copilot CLI event and command, HTTP, and prompt handler schema before writes, then validate matchers with Node.js regular-expression semantics during install. Own one exact preToolUse, postToolUse, and postToolUseFailure triple, preserve native camelCase payloads, and propagate freeze and revocation through exit code 2. Generate guard, config, private key, and audit runtimes with both hook documents in one rollback-capable transaction guarded by read-only settings snapshots. Healthy status requires the enabled three-event contract, strict runtime identity, canonical private key, and exact generated runtime sources.
• Resolve Kiro IDE 1.0 hooks through the active workspace .kiro/hooks/elydora-audit.json. Preserve unrelated workspace hooks, validate the strict version: "v1" schema, and own one exact enabled PreToolUse guard plus PostToolUse audit pair with .* matchers and ten-second timeouts. Use encoded PowerShell commands on Windows, preserve Kiro's complete native payload, and propagate frozen or revoked state through exit code 2.
• Treat ~/.kiro/hooks/elydora-audit.kiro.hook solely as exact legacy Go adapter migration input. Commit its removal, workspace hooks, guard, strict runtime config, canonical private key, and native-payload audit runtime through one rollback-capable transaction with unchanged-source preconditions. Healthy status requires a unique exact pair, physical workspace and runtime paths, matching runtime identity, canonical private key, and exact generated runtime sources; verify both entries in Kiro's Agent Hooks panel.
• Factory Droid droid@0.175.0 selects one complete user hook source in this order: ~/.factory/hooks.json, legacy ~/.factory/hooks/hooks.json, ~/.factory/settings.local.json hooks, then ~/.factory/settings.json hooks. Write the current root { "hooks": { ... } } container, accept unknown future event arrays, preserve JSONC syntax, and remove exact Elydora entries from every discovered user source during migration or uninstall.
• Resolve Factory hooksDisabled through system, project, nested-folder, and matching settings.local.json extension-only precedence before user settings. Treat system allowManagedHooksOnly as an installation gate, snapshot every read-only policy layer as a transaction precondition, and direct users to /hooks for local and organization-managed review.
• Generate Factory Droid guard, strict config, canonical private key, and native-payload audit runtime with every affected hook document in one rollback-capable transaction. Windows commands use Factory's native PowerShell contract with explicit $LASTEXITCODE propagation. Healthy status requires one exact current PreToolUse/PostToolUse pair, strict runtime identity, physical files, and exact generated runtime sources.
• Qwen Code 0.20.0 loads user hooks from $QWEN_HOME/settings.json with ~/.qwen/settings.json as the default. Follow the official QWEN_HOME and QWEN_RUNTIME_DIR .env bootstrap, then resolve system defaults, user, trusted workspace, and system override settings in precedence order. Keep every non-user settings source and trustedFolders.json read-only and guard each source snapshot through the write transaction.
• Preserve JSONC comments, line endings, and unknown future hook fields. Reject trailing commas and duplicate keys, validate all 21 current events plus command, HTTP, and prompt handlers, reject settings-defined function handlers, and apply Node.js RegExp semantics only to the 15 matcher-enabled events.
• Own one exact named matchless PreToolUse, PostToolUse, and PostToolUseFailure triple with 10,000 millisecond timeouts. Generate guard, strict runtime config, canonical private key, and native-payload audit runtime with user settings in one rollback-capable transaction. Propagate frozen and revoked agents through exit code 2; require effective hooks to be enabled, one exact triple, physical runtime files, strict identity, and exact generated sources for healthy status; direct users to /hooks for review.

Shared Modules

• cmd/elydora/plugins/managed_runtime.go owns install-config validation, managed runtime paths, runtime config validation, runtime identity checks, and the strict and presence-only status contracts. managed_changes.go owns runtime config encoding, the four runtime file changes, and the shared directory-plus-commit writer.
• cmd/elydora/plugins/shell_command.go owns Node.js resolution, POSIX and PowerShell quoting, encoded Windows commands, the shell and encoded command builders and parsers, and the pre-2.1 quoted Windows parser.
• cmd/elydora/plugins/jsonc.go owns strict JSON object decoding, JSONC editing, and cloneJSONObject; managed_files.go owns physical file and directory inspection; transaction*.go owns the rollback-capable commit.
• Provider files keep only their hook document schema, ownership rules, rendering, and provider-specific preconditions. Add a provider-local helper only when the shared module cannot express the provider contract.
• jsonutil.go and legacy_hook_entries.go serve the Kiro CLI, Letta, and OpenCode adapters, which write settings without the managed transaction; moving them onto the managed model is a product decision.
• Recognizing pre-2.1 Elydora commands stays in place so elydora install replaces older entries during upgrades.

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.
• Read status cache, chain state, and error logs through physical descriptors with identity checks. Write cache and validated chain state atomically, and append error logs through no-follow owner-only descriptors. Preserve rollback artifacts when recovery cannot safely restore an original file and include the recovery path in the surfaced error.

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

The Linux test environment leaks provider config into $HOME; run the suite with HOME and XDG_CONFIG_HOME pointed at a scratch directory while GOPATH, GOMODCACHE, and GOCACHE keep their real values.

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.