From 38373409d3ceb3b084ac931a1df2bb1cf1bd9d1b Mon Sep 17 00:00:00 2001 From: Mikhail Date: Wed, 22 Jul 2026 03:04:05 +0300 Subject: [PATCH] Document repository request lifecycle --- docs/1c-adapter-api-contract.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/1c-adapter-api-contract.md b/docs/1c-adapter-api-contract.md index 6330ef3..8d355e8 100644 --- a/docs/1c-adapter-api-contract.md +++ b/docs/1c-adapter-api-contract.md @@ -33,6 +33,15 @@ database: such a marker would not create a native repository lock. `repository.lock.confirm` can consume its `request_id`; confirmation always uses the immutable object set stored in the request. +Manual requests expire after `ONEC_REPOSITORY_REQUEST_TTL_SECONDS` (24 hours +by default) and may be explicitly cancelled with +`repository.lock.request.cancel`. Manual confirmations expire after +`ONEC_REPOSITORY_CONFIRMATION_TTL_SECONDS` (2 hours by default). After the user +releases the objects in Configurator, `repository.lock.close` closes the +confirmation and immediately blocks further SQL writes through that session. +The adapter keeps a bounded audit trail of request creation, confirmation, +cancellation, and closure and exposes it to the administrative requests view. + Both backends invoke standard Designer repository commands. A Karman/Filebox backend is an opaque native TCP transport and does not own credentials, object locks, or repository transactions. For configured bases, saved-state apply is