[Task][RFC]: Complete automatic execution admission and cross-surface readback
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 25/100
Direção de pesquisa
Read the linked RFC and coordinate with the current quota, scheduler, settings owners and PR #5187 before choosing an unowned acceptance gap. Starting points are loopx/control_plane/quota, loopx/control_plane/scheduler and apps/presentation/dashboard/src/features/personal-workspace; include affected CLI and Lark entry points. Done means closing only the accepted scope and reconciling the integrated revision, commands, test evidence and remaining gates here.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Outcome / 目标
完成自动执行准入与跨入口反馈。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.
Canonical design: RFC. Roadmap: S2/S4/S5/S7, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.
Current boundary
Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.
M1 owner floor and managed Turn admission shipped in #4921/#4929. The current RFC also records M3 settings and #5186 fixes Agent selection. Live timer-to-hook coverage, non-Turn launchers and next-eligibility parity remain distinct gaps.
Work remaining
- Complete real schedule apply/readback and trustworthy automatic-start identity on supported hosts; explicitly show unsupported launchers.
- Finish shared next-eligible/wait feedback across existing settings, CLI and Lark; preserve inherited Goal/Agent/automation policy.
Ownership and ongoing work
Continue the existing quota/scheduler/settings owners. PR #5187 changes capability-settings scope; coordinate that companion instead of adding another editor. Creating this task does not activate or rebind any automation.
Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.
Acceptance
- Concurrent starts admit once; reserved-but-unstarted crash recovery remains resumable and confirmed attempts cannot replay as fresh starts.
- Manual interval bypass affects only the interval and cannot bypass other authority/quota gates.
- Configuration target changes invalidate previews; restart, backoff/reset and downgrade preserve the documented v1/v2 boundary.
- Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.
Starting points and delivery boundary
- loopx/control_plane/quota
- loopx/control_plane/scheduler
- apps/presentation/dashboard/src/features/personal-workspace
Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.
- Linguagem predominante
- Python
- Estrelas
- 6.2k
- Forks
- 596
- Merge médio
- 6h 9min
- PRs com merge (30d)
- 940
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de loopx-project/loopx
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
loopx-project/loopx#6842 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
loopx-project/loopx#6108 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
loopx-project/loopx#5688 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 60/100
loopx-project/loopx#5632 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
loopx-project/loopx#5443 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de loopx-project/loopx
Issues semelhantes
-
Project submission:Aberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 72/100
slavakurilyak/awesome-ai-agents#845 ·
Mantenedores costumam responder em até 1 dia
-
tests: pin that the atomic writers in utils/paths.py stage the temporary file in the target's directoryTalvez já em andamento Um pull request vinculado a esta issue está aberto ou já foi mesclado. Abertadifficulty:2 enhancement good first issue
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 92/100
MakazhanAlpamys/Soup#2178 ·
Mantenedores costumam responder em até 1 dia
-
[BUG] dcg.waggr permutation p-values are folded twice, so near-zero scores get the smallest p-valuesAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
scverse/rapids-singlecell#854 ·
Mantenedores costumam responder em até 1 dia
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGLTalvez já em andamento @ninglinLiu assumiu hoje. Abertaarea:frontend backend:slang bug direction:input
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
Mantenedores costumam responder em até 13 dias