Repository navigation
Conversation
O passo mecânico das skills rodava `flux preflight <verbo> [alvo]` sem --repo e descartava o bloco PREFLIGHT RESOLVIDO que a CLI já tinha montado. Sem o repo, o preflight ancorava no cwd, tomava o alvo por slug e devolvia exec_fallback nulo, lentes vazias e nível THIN, mesmo com a CLI tendo resolvido tudo antes. - step0-cli.md: novo Passo 0 lê o bloco da invocação; o preflight passa --repo <slug> da linha de invocação; o bloco vence o JSON nos campos em comum, inclusive harness. - review, peek, iterate e chain: linha de uso com [--repo <slug>]. - Cinco manifests em 1.46.1. Co-Authored-By: Claude <noreply@anthropic.com>
This branch has not been deployed
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
1 participant
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.
Problema
Com
flux review 87 --repo flux --harness codex, a CLI resolvia tudo certo (repo, lentes L2,exec_fallback: flux-engine-flux) e abria o Codex. Dentro da sessão, o Step 0-cli da skill rodavaflux preflight review 87 --jsonde novo, sem--repo, e ignorava o blocoPREFLIGHT RESOLVIDOda invocação. Sem o repo, o preflight ancorava no cwd, tomava o alvo87por slug e devolviaexec_fallback: null, lentes vazias e nívelTHIN. A sessão rodava degradada embora a CLI tivesse o contexto completo.Mudança
shared/step0-cli.md: novo Passo 0 lê o bloco da invocação e guarda seus campos como fatos (perfil, âncora,flux_root,exec_*, lentes, avisos, harness).flux preflight <VERBO> [ALVO] [--repo <slug>] --json, com o slug tirado da linha de invocação, que a CLI acrescenta sempre que resolve o repo.holistic,kit_roots,degradations, nível).HARNESSvem doharness:do bloco.review,peek,iterateechain: linha de uso com[--repo <slug>].cli/) não foi alterado.Plano de testes
scripts/check-manifests.sh: 5 manifests em flux@1.46.1.scripts/check-codex-agent-contract.sh: contrato Codex íntegro.flux preflight review 87 --repo flux --jsondevolve âncora no repo,exec_fallback: flux-engine-fluxeFULL-tentativo; sem--repodevolveTHIN.flux reviewno Codex com esta versão. A mudança é só de instrução em Markdown.Fora do escopo: o
flux_rootdo bloco ainda aponta para o cache do Claude quando o harness é Codex.Conflito esperado: a #87 também bumpa para 1.46.1; quem entrar depois precisa rebumpar.
Summary-en: The mechanical preflight step now passes --repo and keeps the CLI's resolved block, so Codex sessions stop degrading to THIN.
Summary-pt: O preflight mecânico passa --repo e preserva o bloco resolvido pela CLI, e as sessões no Codex deixam de degradar para THIN.
🤖 Generated with Claude Code