Skip to content

feat(apps): add acquire_worker_slot with a per-app limit and timeout - #18360

Merged
iamwhatever merged 2 commits into
mainfrom
fix/limit-default-509
Oct 10, 2026
Merged

iamwhatever merged 2 commits into
mainfrom
fix/limit-default-509

Conversation

@bolichen97

@bolichen97 bolichen97 commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Apps that own agent sessions get a supported acquire_worker_slot helper, limited to one worker per app by default, with an acquire timeout.

Today an app that runs a background worker agent has to stamp private slot attributes (slot._app, slot.project, slot._trust) itself, and re-stamp them on every acquire because a restart or another create path rebuilds the slot without them. The app-dev skill documents this as a stopgap pending #509. There is also no bound on how many worker slots one app holds, and trust is often granted with no expiry.

Why it matters

Apps are coupled to private internals that can change under them, and a blanket permanent trust flag quietly exempts more and more sessions from interactive approval as apps copy the recipe.

Not a goal

  • Migrating the builtin apps (auto_research, issue_radar, spec_builder) onto the helper.
  • A manifest permission or AppContext field for the helper.
  • Persisting the per-app limit or lease count across restarts.

What changed (motivation → approach → change)

Gap → one seam that owns the stamping and the bounds → the new module kiro_crew.apps.worker_slots:

  • acquire_worker_slot(state, app, key, *, project, agent, model, trust, trusted_patterns, trust_ttl_secs, timeout) creates the slot if missing, re-stamps the app owner and working directory on every acquire (another create path, such as ChatEmbed's own POST, can create the slot without them), and returns a WorkerSlotLease (usable as async with).
  • Limit: each app holds at most 1 lease at a time by default; set_worker_slot_limit(app, n) changes it live (raising it wakes waiters; lowering it never revokes a held lease). The limit is advisory and self-set for a cooperating app.
  • One owner per slot: a slot key (requested or folded) is held by one lease at a time across all apps, and a slot owned by another app is refused, so one app's grant or working directory never lands on another app's worker.
  • Only app slots are adopted: an unowned slot a person or a cron job opened (_origin user or cron) is refused and left unchanged, under any spelling of its key; unowned app-origin or untagged slots are still re-stamped (the ChatEmbed case).
  • Lost leases are reclaimed: a lease whose slot was deleted or replaced is dropped (and its trust withdrawn) by the next acquire, so a lost lease cannot lock an app out.
  • Every acquire pushes a slot-list update so the dashboard hides the app's slot at once.
  • Timeout: an acquire that cannot proceed waits up to timeout seconds (default 30), then raises WorkerSlotTimeout: app 'x' already holds 1 of its 1 worker slot(s); waited 30s for one to be released. Release a lease (...) or raise the limit with set_worker_slot_limit(). A timed-out or failed acquire creates no slot and holds no lease.
  • Blanket trust is a scoped grant: trust=True never writes slot._trust (it does not expire and is cached as the session's "auto" policy that subagents read later). It activates a SafetyOverride scoped grant and sets slot._trust_scope, the same shape the task runner and issue_radar use: audited fail-closed, re-checked on every approval, never cached as a session policy. If the grant is refused, lease.trust_granted is False.
  • Patterns: trusted_patterns are added only after their audit row is written with critical=True.
  • Withdrawal: both end on release or after trust_ttl_secs (default 1h, max 24h); zero, negative, infinite or over-cap TTLs are refused. Only what the lease added is withdrawn; a human's session trust or another scope already on the slot is left alone.

The skill's Worker Slots section now shows the helper instead of the stopgap, and app-kit-platform.md gains section 23 with the contract.

Plain module function rather than an AppContext SDK: apps that own slots already hold the dashboard state, and this keeps the change free of manifest schema work. The default limit of 1 with a timeout is the maintainer's decision on #509.

Backwards compatibility

Compatible: the helper is new and opt-in. No existing caller changes, and slots acquired the old way behave exactly as before. The default limit of 1 only applies to code that calls the new helper.

Removes nothing: no code path, key or function is removed; only the skill's stopgap recipe text is replaced by the supported call.

Tests

test/test_apps_worker_slots.py (red on main: the module does not exist; 34 passed with the change):

  • default limit is 1; a second acquire times out with the app, limit, wait and remedy in the message and creates no slot;
  • one key is leased once even under a higher limit; another app cannot lease a held key; a slot owned by another app is refused; a folded key cannot alias a held lease; a deleted slot frees its lease;
  • a waiting acquire gets the slot once the first is released, and when the limit is raised;
  • the limit is per app and configurable; bad limits are refused;
  • app owner and working directory are re-stamped on a slot created without them;
  • release is idempotent and the async with form releases; a failed slot create frees the lease;
  • blanket trust writes _trust_scope, never _trust; _slot_is_trusted is True while held and False after release; _persistable_session_policy stays "";
  • a refused scoped grant leaves the worker untrusted; a failed pattern audit adds no patterns;
  • expiry is scheduled with the TTL (call_later spied) and withdraws both grants when fired, plus one short-TTL run awaited with async_wait_until;
  • pre-existing human trust and another scope on the slot are left alone; unbounded TTLs are refused;
  • a user/cron-origin slot is refused and left unchanged, including through a folded key on the real DashboardState; an untagged slot is still re-stamped.

Local gate: black, isort, flake8, mypy over the package, comment-history and brand gates, docs-lint, and scripts/local-gate.py backend (91 passed). The frontend step of local-gate.py could not run here (npm registry auth); this PR touches no frontend code.

Manual verification

N/A — the helper is pure slot bookkeeping with no UI; unit coverage drives every branch against a stand-in state.

Related Issues

Closes #509

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributed under the project's Apache-2.0 license.

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners October 9, 2026 06:13
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 9, 2026
@bolichen97
bolichen97 enabled auto-merge (squash) October 9, 2026 06:14
@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Advisory — does not block merge.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🟡 CONCERNS

Premise-level review of 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The helper has zero callers in the repo, and the builtin apps keep their own hand stamping, so this ships a second way to do the same thing.

Not justified as shipped

  • Item 1 — zero consumers: grepping acquire_worker_slot|worker_slots finds only the module, its test, the skill, the spec and test-infra lists. None of the 3 builtin apps that own slots uses it: spec_builder/backend/runtime.py:195 still sets slot._app = APP_NAME, and issue_radar/backend/crew_runtime.py:516-551 hand-rolls the same activate_scoped plus _trust_scope grant. The description excludes "Migrating the builtin apps" as not a goal.
    Clears when: one builtin app calls the helper in place of its own stamping, or a human accepts external apps as the only consumers.
  • Item 3 — zero consumers: grepping set_worker_slot_limit finds 0 callers outside the module, its test and the docs. The live-raise path (_notify_all, the loop check) exists only for this function.
    Subtraction: delete set_worker_slot_limit, _limits and _notify_all, and keep the fixed DEFAULT_WORKER_SLOT_LIMIT until an app needs more.
    Clears when: an app that runs several workers at once calls it.

What this change ships

Inventory (10 items) — 8 justified

Intent: let apps own a background worker session through a supported, bounded seam instead of setting private slot attributes by hand. ADDITION.

  1. Apps get a supported acquire_worker_slot helper — zero consumers: no in-repo caller
  2. By default each app gets one worker; a further acquire waits 30s, then errors — justified
  3. Apps can change their own worker limit while running — zero consumers
  4. A slot owned by another app, a person or a cron job is refused — justified
  5. Blanket trust becomes an audited, expiring scoped grant, never _trust — justified
  6. Trusted patterns are added only after the audit row is written — justified
  7. Trust lasts 1h by default, 24h at most; bad TTLs are refused — justified
  8. Leases whose slot was deleted are reclaimed automatically — justified
  9. The app-dev skill's stopgap recipe is replaced by the helper — justified
  10. The app-kit spec gains section 23 — justified

[FIRST-PRINCIPLES-REVIEWED] 6b71904

Description read

[DESCRIPTION-READ] 7f8ba3a398171d9c3f98bcb6caeda018b03e6d1cc1383d3e3be2469af1dc11b8

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — 🟡 CONCERNS

Design-level review of 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: CONCERNS

Leases and worker trust grants aren't tied to the app's lifecycle, so disabling or reloading an app leaves its auto-approve grant live and can lock the app out.

Watch

  • Lifecycle orphaning. The registry is a module global (_registry = _Registry()). Its only reclaim condition is _slot_is_gone(), meaning the slot was deleted or replaced. manager.disable_app / uninstall_app never call deactivate_scope for app:<name>:worker:*.

    • When the user disables an app, a turn already running in its worker slot keeps auto-approving tool calls until trust_ttl_secs runs out (default 1h, up to 24h). tool_approval._persistable_session_policy says revocation on "disable the app" is the property scoped grants exist for.
    • When an app's backend reloads in-process and drops its lease objects, the slot still exists. With the default limit of 1, every later acquire raises WorkerSlotTimeout until the gateway restarts.

    Clears when: app disable/uninstall (and backend reload, if apps reload in-process) releases that app's leases and deactivates its worker_trust_scope grants, with a test for each.

  • Adopting untagged slots goes against spec_builder._ensure_worker_slot. That function refuses any slot not already owned by the app, because "an UNSCOPED slot under our key is somebody else's conversation". This helper re-stamps unowned slots with an empty _origin, such as slots from openai_compat.get_or_create_slot(slot_name) or workflow slots. When the key collides, that chat's project gets repointed and it is pulled into the app, possibly with a trust grant. The PR doesn't say why the newer seam is looser than the built-in precedent.

    Clears when: the helper adopts only _origin == app slots (ChatEmbed's POST with app already tags them APP), or the spec records why untagged slots are safe to adopt.

[DESIGN-REVIEWED] 6b71904

Description read

[DESCRIPTION-READ] ebd8b1e22754f130ebbd87ed9c119d47abaef4dc2621f4e79b17efab3ce1f0f2

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 6b71904

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 6b71904

Verdict parsed from the review's SHA-scoped output markers for commit 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 6b7190493fa7d77d1ad2bd0ad8ee419230cce04c: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 9, 2026
@bolichen97
bolichen97 force-pushed the fix/limit-default-509 branch from bf4f7dd to d70863e Compare October 9, 2026 07:02
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 9, 2026
@bolichen97
bolichen97 force-pushed the fix/limit-default-509 branch from d70863e to 28eca9f Compare October 9, 2026 08:14
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 9, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

On the First Principles concern about the limit: the default limit of 1 with an acquire timeout is the maintainer's recorded decision on #509 (latest comment there). Moving the builtin apps onto the helper stays out of this PR's goal.

@iamwhatever

Copy link
Copy Markdown
Contributor

This adds a new public app-kit API, kiro_crew.apps.worker_slots.acquire_worker_slot (402 new prod lines plus 418 test lines). It gives a per-app lease limit (default 1), an acquire timeout, re-stamping of the slot's owner and project, and trust that is a TTL-bounded SafetyOverride scoped grant instead of the permanent slot._trust. I read the module and the lane results. Checks are green, the GPT/Opus/Design lanes have no findings, and the author answered First Principles' CONCERNS by citing the maintainer decision on #509. First Principles also noted the helper has zero in-repo callers. Trying to break it: the owner check only refuses a slot whose _app is a different app. So acquire_worker_slot on the key of any existing slot with no _app (for example a human's dashboard chat) takes it over: it stamps _app (hiding it from the sidebar), sets project, and can attach the app's scoped auto-approve grant (worker_slots.py, the owner and owner != app check in acquire_worker_slot). That re-stamping is on purpose so ChatEmbed-created slots work, but a maintainer should decide whether the helper may only adopt slots it created or that are tagged as app-embed. Apps already hold the dashboard state, so this is a guard-quality question, not a new privilege. I am holding because this is a new feature that changes trust/approval policy, which needs a human under the brief. — crew-pr-reviewer

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deep re-review of a held PR (I tried to break it). Adds a supported app-kit helper so apps stop hand-stamping slot._app/project/_trust; trust becomes a TTL-bounded audited SafetyOverride scope instead of the permanent _trust flag, which is a real improvement. Head 28eca9f is MERGEABLE, no CHANGES_REQUESTED, GPT/Opus/Design have no findings; First Principles CONCERNS (limit of 1, zero callers) was answered by citing the maintainer decision on #509. Attack tried: the hold's reason still stands and I proved it. get_or_create_slot (dashboard/state.py:7878) returns any existing slot, and the only owner check is owner and owner != app (worker_slots.py:374), so an unowned slot is adopted. A probe test with a human chat slot (_origin="user", project=/home/me/secret-repo) under acquire_worker_slot(trust=True) got _app="evil-app", project=/tmp/x and the app's auto-approve scope; after release the scope was withdrawn but the chat stayed hidden (_app) and stayed moved to /tmp/x, with nothing telling the user. Apps already hold dashboard state, so this is not a new privilege, but a supported helper should not make taking over a person's chat the easy path. Limit, timeout, folded-key and TTL paths look right. Requested change: src/kiro_crew/apps/worker_slots.py:372-375 -- before get_or_create_slot, read pre = state.get_slot(key); if pre exists with an empty _app and getattr(pre, "_origin", "") is SlotOrigin.USER or SlotOrigin.CRON, raise ValueError("slot ... belongs to a person/cron; an app may only adopt slots it created"). Keep the re-stamp for unowned APP/untagged slots (the ChatEmbed case). Add one test: a USER-origin slot is refused and left unchanged. On the owner decision: Allow the helper to adopt only slots it created or unowned APP/untagged ones, never USER or CRON origin. Reason: that keeps the ChatEmbed re-stamp case working and closes the takeover of a person's chat. Keep the default limit of 1 as #509 already decided. Risk: medium. — crew-pr-reviewer

@bolichen97

Copy link
Copy Markdown
Contributor Author

Done in 02f565c: an unowned user/cron-origin slot is now refused with ValueError and left unchanged; unowned app/untagged slots still re-stamp (ChatEmbed), the default limit stays 1, and test_a_person_or_cron_slot_is_not_adopted was red before the change.

@bolichen97
bolichen97 requested a review from iamwhatever October 9, 2026 19:04
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running labels Oct 9, 2026
@github-actions github-actions Bot added the readiness: action required A blocking check or review needs attention label Oct 9, 2026
@bolichen97
bolichen97 force-pushed the fix/limit-default-509 branch from 02f565c to 993d952 Compare October 9, 2026 19:44
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased onto main and folded the fix into commit 2; the previous head was 02f565ceecbb30824e4540508a735097a394d4f0.

GPT / Opus (worker_slots.py:378): fixed in 993d952. The person/cron check now runs on the slot get_or_create_slot returns, so a folded key (dashboard:chat-1, dashboard_chat-1) is refused too. New test test_a_person_slot_is_not_adopted_under_any_spelling_of_its_key uses the real DashboardState and was red on the previous head.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 9, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

E2E case 17b (session-tags-e2e.spec.ts) is a known flake tracked by #18529; this PR's diff is backend-only, and 17b passed on retry in all 3 runs.

w added 2 commits October 10, 2026 00:22
Apps that own agent sessions stamped private slot attributes by hand and
had to re-stamp them whenever another path created the slot first.
acquire_worker_slot owns that: it re-stamps the app owner and working
directory on every acquire, caps each app at one lease by default
(set_worker_slot_limit changes it) and one lease per slot key, waits up
to a timeout and raises WorkerSlotTimeout with a clear message.

Blanket trust is a SafetyOverride scoped grant on slot._trust_scope, not
the never-expiring slot._trust flag, so it is audited fail-closed,
re-checked per approval and never cached as a session policy. Trusted
patterns are audited fail-closed before they are added. Both end on
release or after a TTL of at most 24h.

Closes #509
An unowned slot a person or a cron job opened is refused with ValueError and left unchanged. Unowned app-origin or untagged slots are still re-stamped (the ChatEmbed case).
@bolichen97
bolichen97 force-pushed the fix/limit-default-509 branch from 993d952 to 6b71904 Compare October 10, 2026 00:22
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased onto main to pick up the E2E 17b fix (#18644, which superseded #18529); previous head was 993d952562500934f45b10e42dd116202e17c8a5, no code change.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 10, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

This adds a new public app-kit API, acquire_worker_slot, with a per-app lease limit, an acquire timeout and TTL-bounded SafetyOverride trust grants that replace the permanent slot._trust. iamwhatever's earlier request is addressed: worker_slots.py:383 now refuses an unowned USER- or CRON-origin slot, and it checks the slot get_or_create_slot actually returned, so a folded key spelling is refused too. Unowned APP/untagged slots still re-stamp for ChatEmbed. Tests were added for both, and I read the head code. The GitHub review decision still shows CHANGES_REQUESTED at 28eca9f, so iamwhatever needs to re-review. HOLD because this is a new feature (~400 prod lines) that grants auto-approve trust (permission surface). The Design CONCERNS on head 6b71904 also has no target=design disposition, and both of its points are real. First, disable_app/uninstall_app never release the app's leases or deactivate its worker trust scopes, so a running worker keeps auto-approving until the TTL ends, and a reloaded backend can lock itself out at limit 1. Second, adopting untagged slots is looser than spec_builder._ensure_worker_slot. Suggested fix: release leases and call deactivate_scope for app::worker:* on disable/uninstall, with a test, and either adopt only _origin == APP slots or document why untagged ones are safe. — crew-pr-reviewer

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at 6b71904.

This gives apps one supported call to own a hidden, project-scoped worker session, capped at one per app with a bounded wait, and replaces the permanent session trust flag with an audited, expiring scoped grant. The limit, timeout, folded-key, owner and TTL paths hold up, and the earlier request is fixed: worker_slots.py:383 refuses an unowned user/cron slot on the slot actually returned, before anything is stamped, with tests on the real DashboardState. Breaking that check, the other-app owner check, the failure-path reservation release, or trust withdrawal on release each reddens named tests in test/test_apps_worker_slots.py. CI on this head: 85 success, 13 skipped, 0 failing. I did not run the full suite locally.

Two things block, both raised in the earlier hold and not yet addressed:

  1. Untagged slots include people's channel conversations. Only user and cron are refused, so an unowned slot with an empty _origin is still adopted. Empty origin is what background create paths produce on purpose: dashboard/channel_slots.py:569 opens the Slack/Discord conversation tab untagged, and dashboard/state.py:8003-8015 names Slack, workflow inject and the OpenAI-compatible endpoint as untagged. Adopting one of those hides a person's conversation and repoints its project, the same harm as the USER case. The ChatEmbed reason does not appear to need it: chat-send stamps origin from the request (chat_handlers.py:852-855), and spec_builder's _ensure_worker_slot already refuses every unscoped slot. Please adopt an existing unowned slot only when _origin == SlotOrigin.APP (or not at all), add a test with an untagged channel slot, and correct the spec bullet "Only app slots are adopted" and the commit title, which currently overclaim.

  2. Disable/uninstall leaves leases and trust live. Nothing outside the module references it, so disable_app/uninstall_app never release an app's leases or deactivate app:<app>:worker:*. A disabled app's worker keeps auto-approving until the TTL (up to 24h), and a reloaded backend that lost its lease object while the slot still exists is locked out at the default limit of 1 until a restart. Please add a release-all-for-app call wired into disable/uninstall, with a test, and narrow the spec's "a lease the app lost cannot lock it out" to what is actually reclaimed.

Non-blocking follow-ups:

  • release() and the acquire failure path await the condition lock before touching the registry; a second cancellation while that lock is contended leaves the lease or reservation in place. The dict updates can be done synchronously, with only notify_all under the lock.
  • The spec says a failed acquire creates no slot, but a failure after get_or_create_slot (for example inside the trust grant) leaves the newly created, already stamped slot behind.
  • Pattern withdrawal can remove an identical pattern a person added while the lease was held.

@iamwhatever
iamwhatever merged commit 5052ddd into main Oct 10, 2026
103 checks passed
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 10, 2026
@bolichen97
bolichen97 deleted the fix/limit-default-509 branch November 20, 2026 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

apps: supported worker-slot seam (acquire_worker_slot) surviving rehydration

3 participants