[Task][RFC]: Qualify the effective manager runtime profile across sessions
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- python
- Bereich
- ai-infra-agents
Rechercherichtung
Read the canonical RFC and start with loopx/capabilities/manager_runtime/machine_profile.py, loopx/chat_manager.py, and apps/presentation/dashboard; coordinate with the current owners and #5187 before choosing an unowned acceptance gap. Verify the effective profile across the real supported endpoint and the affected CLI/frontend entrypoints, then report commands and passed, failed, and untested evidence against the acceptance checklist.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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: S1/S4/S9 · manager M1, 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.
The machine-level restricted/trusted_owner configuration, controller integration and focused tests are already recorded as shipped. The RFC explicitly separates that implementation from deployment and full M1 qualification.
Work remaining
- Verify the effective config, sandbox, prompt, workspace instructions and active upstream Session agree on the real supported endpoint.
- Finish restart/profile-change/downgrade recovery and existing settings readback without adding a second configuration source.
Ownership and ongoing work
Reuse #4339 and current manager/App work; coordinate with #5187 settings consolidation. This RFC owns profile consistency, not general handoff, outbox or a new permission system.
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
- Default/invalid config remains restricted with actionable repair; unsupported endpoints do not pretend to enforce trusted_owner.
- A material profile change rotates the upstream thread while preserving visible history; unrelated settings do not rotate it.
- External audiences remain restricted absent the existing scoped grant; protected operations retain their own authorization. CLI and actual frontend expose the effective Session profile.
- 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/capabilities/manager_runtime/machine_profile.py
- loopx/chat_manager.py
- apps/presentation/dashboard
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.
- Vorherrschende Sprache
- Python
- Sterne
- 6.2k
- Forks
- 596
- Ø Merge
- 5 Std. 33 Min.
- Gemergte PRs (30 T.)
- 933
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus loopx-project/loopx
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
loopx-project/loopx#6842 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
loopx-project/loopx#6108 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
loopx-project/loopx#5688 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 60/100
loopx-project/loopx#5632 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
loopx-project/loopx#5443 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in loopx-project/loopx
Ähnliche Issues
-
ReadQwen3PaperTask5 rejects correct answers that differ only in order, case, or underscore formEvtl. vergeben @Kingpython123 hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
Tongyi-MAI/MobileWorld#72 ·
-
_threads/application: Update typing annotations using `pyupgrade --py311-plus`Evtl. vergeben @gudnimg hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
Health probes return 401 when authentication is enabled and the API is served under /orbEvtl. vergeben @fgogolli hat das heute übernommen. Offenarea: api priority: p2 size: S type: bug
Schwierigkeit 2/5 Ein halber Tag Anfängerfreundlichkeit 75/100
finos/open-resource-broker#704 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
BCDA-APS/polar-bits#93 ·
-
bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 90/100
GoogleCloudPlatform/gce-rescue#218 ·
Maintainer antworten meist innerhalb von 2 Tagen