Skip to content

armgit / Ix

Public Imported from GitHub
0

Understand any codebase instantly. System intelligence for codebases, built for humans and AI.

docs(security): document reset redirect refusal in the API reference

KageBinary1b2591fc7474
diff --git a/docs/api/README.md b/docs/api/README.md
index 178e840c..375f55e1 100644
--- a/docs/api/README.md
+++ b/docs/api/README.md
@@ -629,6 +629,12 @@ lowercase RFC-4122 UUID), then poll `/v1/reset/status/{opId}` every 2s up to
15 minutes. The status body repeats `opId`, and the client rejects a body
naming a different operation.
+The client never follows redirects on any reset request (`begin`, `status`,
+or either sync path): a 3xx stops with the same reconciliation warning rather
+than replaying the POST or treating a redirected 404 as an old backend, so a
+remote endpoint must be configured as the direct backend URL, not one a proxy
+redirects (e.g. `http://` behind an HTTPS redirect).
+
A 404 on `begin` falls back to the sync path (old backend). A 404 on `status`
does **not**: the op ledger is in-process, so a restart, a different replica or
eviction drops the entry while the reset itself may have completed. Reset is
diff --git a/docs/security/reset-outcome-reconciliation.md b/docs/security/reset-outcome-reconciliation.md
index 0e589248..248cbcba 100644
--- a/docs/security/reset-outcome-reconciliation.md
+++ b/docs/security/reset-outcome-reconciliation.md
@@ -34,16 +34,20 @@ trigger sync fallback. A refused redirect target also says nothing about whether
the initial reset ran. Redirect responses therefore require reconciliation, with
the original operation ID retained when known. Configure the direct backend
endpoint before any operator-approved recovery; do not repeat an uncertain reset.
+
Authentication errors at start remain errors. This patch does not add tenant
headers, credentials or an authorization bypass; the remote transport must
establish the expected verified caller identity.
-`ix-cli/src/client/reset-outcome.test.ts` executes the real client with synthetic
-HTTP responses and asserts the exact request sequence. It covers success for
-both reset kinds, invalid/foreign operation IDs, partial failure, transport
-loss, deadlines and local/older-server compatibility. Live authenticated
-remote transport and supported-release integration still need verification
-before claiming deployment acceptance.
+`ix-cli/src/client/__tests__/reset-outcome.test.ts` executes the real client with
+synthetic HTTP responses and asserts the exact request sequence. It covers
+success for both reset kinds, invalid/foreign operation IDs, partial failure,
+transport loss, deadlines and local/older-server compatibility.
+`ix-cli/src/client/__tests__/reset-redirect.test.ts` drives the same client
+against real loopback HTTP servers and asserts that no reset request is
+replayed or reinterpreted after a 3xx on any of the four request paths. Live
+authenticated remote transport and supported-release integration still need
+verification before claiming deployment acceptance.
Pro is an optional, separately installed private plugin; the OSS package does
not fetch it as a dependency. Its explicit runtime resolution is therefore