[Bug]: `integration switch` leaves the manifest out of date when a preset overrides a core command
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 78/100
Línea de trabajo
Empieza por src/specify_cli/integrations/command_switch.py:380-389 y compara su flujo de registro de preajustes con _resync_manifest_after_registration en command_upgrade.py:352 y src/specify_cli/integrations/_helpers.py:486-505. Ejecuta la reproducción del issue e inspecciona tests/specify_cli/integrations/test_command_upgrade.py:1320-1385 para ver la expectativa de regresión existente. Se considera terminado cuando el hash del manifiesto coincide con el archivo de preajuste reescrito después del cambio y la actualización posterior se completa correctamente sin --force.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug Description
specify integration switch <target> installs the target integration and saves its manifest (src/specify_cli/integrations/command_switch.py:309-316). It then re-registers installed presets for the target (command_switch.py:380-389). A preset that overrides a core command rewrites a file the manifest already tracks, and the manifest is not re-hashed afterwards. As a result integration status reports the file as modified, and a later integration upgrade without --force refuses to run, even though the user changed nothing.
integration upgrade handles the same situation by calling _resync_manifest_after_registration (command_upgrade.py:352, added for #4696). switch does not call it.
Steps to Reproduce
From the root of a fresh clone, after uv sync, save the script below as repro.py and run it with uv run python repro.py.
import hashlib, json, os, tempfile
from pathlib import Path
from typer.testing import CliRunner
from specify_cli import app
tmp = Path(tempfile.mkdtemp())
project = tmp / "proj"
project.mkdir()
os.chdir(project)
run = lambda *args: CliRunner().invoke(app, list(args))
run("init", "--here", "--integration", "claude", "--script", "sh", "--ignore-agent-tools")
preset = tmp / "tasks-preset"
(preset / "commands").mkdir(parents=True)
(preset / "commands" / "speckit.tasks.md").write_text(
"---\ndescription: Tasks override\n---\nPreset tasks body\n")
(preset / "preset.yml").write_text("""schema_version: '1.0'
preset: {id: tasks-preset, name: Tasks Preset, version: 1.0.0, description: x}
requires: {speckit_version: '>=0.1.0'}
provides:
templates:
- {type: command, name: speckit.tasks, file: commands/speckit.tasks.md}
""")
run("preset", "add", "--dev", str(preset))
r = run("integration", "switch", "codex", "--script", "sh")
print("switch exit code:", r.exit_code)
rel = ".agents/skills/speckit-tasks/SKILL.md"
manifest = json.loads(Path(".specify/integrations/codex.manifest.json").read_text())
on_disk = hashlib.sha256(Path(rel).read_bytes()).hexdigest()
print("preset body in skill:", "Preset tasks body" in Path(rel).read_text())
print("manifest hash matches file:", manifest["files"][rel] == on_disk)
r = run("integration", "upgrade", "codex", "--script", "sh")
print("upgrade exit code:", r.exit_code)
print(r.output.strip())
The script initialises a project with Claude Code, adds a local preset that overrides speckit.tasks, switches to Codex, compares the manifest hash with the file on disk, and then runs integration upgrade codex without --force.
Expected Behavior
After the switch, the manifest hash for .agents/skills/speckit-tasks/SKILL.md matches the file that preset registration wrote, and integration upgrade codex succeeds. The docstring of _resync_manifest_after_registration (src/specify_cli/integrations/_helpers.py:486-505) says files rewritten by registration must be re-hashed "so check_modified() doesn't misreport a legitimate override as tampering", and names switch among the operations it serves. The regression test test_upgrade_force_syncs_manifest_hash_for_preset_overridden_skill (tests/specify_cli/integrations/test_command_upgrade.py:1320-1385) sets the same expectation for upgrade.
Actual Behavior
switch exit code: 0
preset body in skill: True
manifest hash matches file: False
upgrade exit code: 1
⚠ 1 file(s) have been modified since installation:
.agents/skills/speckit-tasks/SKILL.md
Use --force to overwrite modified files, or resolve manually.
Specify CLI Version
1.2.4.dev0 (main at 27d14e2)
AI Agent
Codex CLI
Operating System
Linux 6.18 (Ubuntu container)
Python Version
Python 3.12.3
Error Logs
⚠ 1 file(s) have been modified since installation:
.agents/skills/speckit-tasks/SKILL.md
Use --force to overwrite modified files, or resolve manually.
Additional Context
integration use (src/specify_cli/integrations/command_use.py) also re-registers presets without a manifest resync, so it looks affected in the same way, but I have not reproduced that path. Calling _resync_manifest_after_registration after preset registration in switch (and probably use) would likely fix it.
Also reproduced on macOS (Darwin 25.6, arm64) with Python 3.14.4 and uv run python -I repro.py against 27d14e2; the output matches the above.
AI Disclosure
Found and reproduced with Claude Code (model: Claude Opus 4.8), run autonomously under human supervision. The human reporter re-ran every reproduction above before filing.
- Lenguaje dominante
- Python
- Estrellas
- 149k
- Forks
- 13.4k
- Merge medio
- 1 d 5 h
- PR fusionados (30 d)
- 223
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
triage-must-have
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Workflow-step verifier test fixture breaks when the checkout path contains whitespace (4 failures on macOS)Posiblemente ocupada @mehdikarimi55 la tomó hace 3 días. Abiertotriage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
Parity tests fail under the documented direct pytest invocation when the ambient python3 lacks PyYAML (11 failures)Posiblemente ocupada @mehdikarimi55 la tomó hace 3 días. Abiertotriage-must-have
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug triage-out-of-scope
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
Todos los issues de github/spec-kit
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
glossyio/traffic-monitor#312 ·
Los mantenedores suelen responder en 1 día
-
local devenv exampleAbiertodocumentation enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
es-ude/elastic-ai.creator#1046 ·
Los mantenedores suelen responder en 3 días
-
ENH: permit cachetools >= 7Abiertofeature request
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
confident-ai/deepteam#306 ·
Los mantenedores suelen responder en 1 día
-
SslLibrary crashes with unhandled OSError: port/proto not found on non-standard SSL portsPosiblemente ocupada @himanchalkaushale la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
OWASP/Nettacker#1884 · 1 comentario ·
Los mantenedores suelen responder en 1 día