Repository navigation
fix(P0): bind local AMD/Intel and future internal agents symmetrically - #147
Merged
Rafa-Innerchispa merged 1 commit intoOct 12, 2026
Merged
Conversation
Rafa-Innerchispa
marked this pull request as ready for review
October 12, 2026 05:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P0: reparar la admisión de proveedores internos AMD / Intel, sin tocar producción
Se verificó en la definición de
agent_provider_registry.pyque la lista de proveedores internos conteníalocal-amd-5(forma con guiones) pero nolocal-intel-4; sin embargoagent_identity.canonical_mailboxnormaliza guiones a guiones bajos, de modo que la admisión por registro no coincidía plenamente conexecution_binding.normalize_provider. El binding también utilizaba una lista fija que omitía Intel, impidiendo que futuros proveedores registrados compartieran una sola política.Corrección aislada
register_internal_providerusa la identidad canónica al registrar proveedores.apply_create_ops_defaultsfijalocal_dev_swarmy permite auto-dispatch local por defecto, respetando una prohibición explícita.execution_bindingobtiene los proveedores internos desde el mismo registro, sin lista paralela hardcodeada.do_not_auto_dispatch=true.Justificación y aceptación
El canario local
ops_db977ed275b8se ejecutó a las 05:41Z, pero falló correctamente: Qwen describió cambios sin crear archivos objetivo. Temporal marcófailedconCompletion prohibited: required evidence missingyobjective_paths=[]. Esto confirma que existe un bloqueo en la materialización de cambios del ejecutor local: el presente PR corrige solo la admisión/binding, no afirma corregir esa materialización.Este PR no modifica vLLM, red, secretos, servicios o main directamente. Exigir CI PASS, inspección del diff y revisión del alcance antes de merge. No reutilizar ni reintentar
ops_db977ed275b8sin reconciliar; conservar su evidencia de fallo y no enviar dos ejecutores al mismo worktree.La implementación corresponde a la línea P0 preexistente
ops_f46a62594c73; no abre otro workflow de coordinación.