make concurrent

README.md

@@ -16,9 +16,11 @@ private OpenCode server on the same Docker network as Gitea.
 | PR | `/agent fix [message]` | Start a fresh one-shot fix session and push one commit. |
 
 The requester must have Gitea `write`, `admin`, or `owner` permission on the repository. Commands
-are durably sequenced when their webhook arrives, then authorized and executed in that receive
-order. Each command gets one Gitea comment, which is reconciled asynchronously through queued,
-running, and terminal states. Deleted comments are rediscovered by their hidden marker or recreated.
+are durably sequenced when their webhook arrives, then authorized and executed in receive order per
+issue or pull request. Up to `AGENTCI_MAX_CONCURRENT_JOBS` unrelated targets execute concurrently;
+the default is two. Each command gets one Gitea comment, which is reconciled asynchronously through
+queued, running, and terminal states. Deleted comments are rediscovered by their hidden marker or
+recreated.
 
 ## Deploy
 
@@ -131,7 +133,9 @@ sessions. Tea's Gitea token configuration is regenerated in an ephemeral tmpfs a
 SQLite stores the current job state, an idempotent event inbox, and durable listener tasks. State
 transitions and workflow creation/linking commit atomically; timestamps are storage metadata rather
 than reducer state. Control effects retry with bounded backoff. A delayed authorization blocks later
-workflow execution but not later control work.
+workflow execution for the same issue or pull request, but not other targets or later control work.
+Development environment installers remain serialized because they share the persistent tools
+directory.
 
 The OpenCode migration tags existing workflows as Codex-owned and preserves their session IDs for
 rollback, but OpenCode refuses to resume them. Follow-up commands against those workflows ask for a