Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Task][RFC]: Complete automatic execution admission and cross-surface readback

Ouverte
  • Quelque chose ne va pas ?
#5,202 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
backend, cli, frontend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

direction/architecture-evolution

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

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.

Langage dominant
Python
Étoiles
6.2k
Forks
596
Merge moyen
6 h 33 min
PR mergées (30 j)
905

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de loopx-project/loopx

Toutes les issues de loopx-project/loopx

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.