chore(oss): audit the root documentation
Correct the Python minimum to 3.10, list integrations, test, and the compose file in the project structure, drop every em-dash, label the SDK badges as mirror versions, and record this audit's server, migration, and SDK changes in the changelog. Claude-Session: https://claude.ai/code/session_01Agoc9bRVE9KL7mmWtey9Vq
This commit is contained in:
1 parent
f69350d709
commit
d8fd400cef
3 files changed
+46
-36
No files matched your search
+8
-1
@@ -10,7 +10,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
|
||||
- Console registration wizard synced with the hosted Console: native hook catalog with activation steps, a one-command install that embeds both credentials in owner-only files (created exclusively with `mktemp` on POSIX; created under `$HOME` and protected with `chmod 600` or an `icacls` owner-only ACL in PowerShell) and deletes them afterwards, and a never-expiring default API token.
|
||||
- Server issues opaque API tokens: `POST /v1/auth/token` honours `ttl_seconds` (`null` never expires), stores only SHA-256 hashes (migration 003), and resolves bearer values as API tokens before Better Auth sessions.
|
||||
- Server commits operations before enqueueing; a `seq_no` race now returns `400 PREV_HASH_MISMATCH` with the stored chain hash, and every queue producer names its durable message id.
|
||||
- SDK mirrors rebuilt from the released SDKs: Node 2.0.1, Python 2.0.2, Go v2.0.1 under `github.com/Elydora-Infrastructure/Elydora-Go-SDK/v2` (hook retry on `PREV_HASH_MISMATCH` within a 4-second budget, durable managed-file transactions, Kiro IDE adapter).
|
||||
- SDK mirrors rebuilt from the standalone repositories at Node 2.1.0, Python 2.1.0, and Go v2.1.0 plus the unreleased fixes listed below; npm serves 2.0.1 and PyPI serves 2.0.2 until the next publish. The mirrors live under `github.com/Elydora-Infrastructure/Elydora-Go-SDK/v2` (hook retry on `PREV_HASH_MISMATCH` within a 4-second budget, durable managed-file transactions, Kiro IDE adapter, shared managed-runtime modules).
|
||||
- Compose and Helm apply `packages/server/migrations` through one runner (`node dist/migrate.js`); migrations already recorded in `schema_versions` are skipped. Migration 004 restores the status constraints, the agent organization foreign key, and the 64-bit counters that the previous inline Compose schema carried.
|
||||
- Server emits `AGENT_REVOKED` and `KEY_RETIRED` instead of reusing `AGENT_FROZEN` and `KEY_REVOKED`, matching the hosted API and the protocol specification.
|
||||
|
||||
### Fixed
|
||||
- SDK `deepHealth()` returns the degraded report that the API sends with HTTP 503 instead of raising.
|
||||
- SDKs no longer replay non-idempotent requests after a 429, a 5xx, or a lost connection, so a retried token rotation cannot discard the replacement token.
|
||||
- `RotateApiTokenResponse` carries `previous_token_grace_until`, and agent IDs are percent-encoded in request paths.
|
||||
|
||||
## [0.1.0] - 2025-03-02
|
||||
|
||||
|
||||
Reference in new issue
Block a user