Skip to content

[Quality] Enforce no-internal-JSON and prove binary-format migration E2E #19

Description

@wesleysimplicio

Dependencies

Objective

Make the repository migration release-blocking and prove that Loop inheritance, OSS task/contribution flows, queues, receipts, clean install and compatibility with the pinned Loop release work without JSON in any Simplicio-owned internal path.

Implementation steps

  1. Integrate the pinned shared scanner in baseline and strict CI modes.
  2. Check source, tests, fixtures, generated outputs, build/package contents and runtime state directories.
  3. Add an exact TOML exception registry; reject broad globs, missing owners, missing reasons and expired exceptions.
  4. Add unit tests for codecs/config models and corruption/bounds behavior.
  5. Add integration tests for HBP/HBI/TOML producers and consumers.
  6. Add system tests that restart processes, recover from interruption and verify semantic state.
  7. Add cross-repository E2E using released/installed packages rather than only source checkouts.
  8. Exercise clean install, legacy upgrade, rollback and mixed-version rejection/compatibility windows.
  9. Verify third-party JSON is accepted/emitted only in explicit adapters and cannot enter domain/storage types.
  10. Publish Markdown test summary plus HBP receipts; do not generate internal JSON evidence.
  11. Benchmark cold/warm behavior, file size, allocations and peak RSS on the same workload/hardware.
  12. Protect the release so missing/unobservable evidence is null with a reason and never treated as a passing zero.

Required test matrix

  • Linux, macOS and Windows where the repository ships support;
  • empty/minimal/large state;
  • legacy/current/future-version artifact;
  • corrupt/truncated/oversized/out-of-bounds artifact;
  • interrupted migration and concurrent access;
  • clean install, upgrade, rollback and restart;
  • source checkout and installed package;
  • online external adapter and offline internal workflow;
  • supported adjacent Simplicio producer/consumer versions.

Revisão complementar do projeto: simplicio-loop-oss

Responsabilidade avaliada: open source. Esta issue deve ser entendida no contexto da auditoria-mãe do repositório.

Objetivo específico

validar issue → plano → branch → patch → testes → PR

Fluxo de testes obrigatório

conflito, licença, segredo, dependência externa, rollback e escopo

  1. Registrar SHA/branch, ambiente, dependências e configuração.
  2. Executar o caminho feliz completo e capturar logs/receipts.
  3. Injetar entrada inválida, timeout, falha externa ou permissão ausente aplicável.
  4. Verificar retry, cancelamento, idempotência e rollback quando o fluxo suportar.
  5. Executar testes unitários, integração, sistema/E2E, regressão, segurança e desempenho aplicáveis.
  6. Reexecutar com os mesmos dados e comparar resultado/hashes.
  7. Confirmar que falha nunca vira sucesso e que recursos são liberados.

Evidências obrigatórias

  • PR/commit vinculado;
  • comandos e versões;
  • logs do caminho feliz e da falha;
  • testes/coverage/benchmark aplicáveis;
  • receipts, hashes e relatório de rollback;
  • limitações e próximos passos.

Regra de encerramento

Não fechar sem todos os critérios desta issue e da auditoria-mãe atendidos. Se faltar implementação, marcar como NEEDS-IMPLEMENTATION ou BLOCKED, nunca como concluída.

Execução

  • Implementar o objetivo descrito.
  • Fazer a implantação aplicável.
  • Executar e registrar os testes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions