superzip-build-test

name	superzip-build-test
description	Build, test, benchmark, and security-scan the SuperZip native C++ AMD HIP project on Windows. Use when changing SuperZip C++ source, build scripts, security checks, GPU code, ZIP/SUZIP archive logic, or GUI behavior.

SuperZip Build/Test Skill

Start by asking the change-aware verifier what is relevant:

tools/verification_plan.ps1 -IncludeUntracked
tools/verify_changes.ps1 -IncludeUntracked

Use the full profile only when the plan escalates, the change is broad or unknown, verification tooling changed, or a targeted command fails:

tools/verify_changes.ps1 -IncludeUntracked -Full

For pushed commits, follow the plan's workflowWaitPolicy. During multi-commit feature work, use tools/wait_relevant_workflows.ps1 -Commit <sha> -Mode opportunistic only when deferral is allowed, and keep developing while runs are active. Before handoff or release, and always for workflow/verifier/MCP/skill or full-escalation changes, use -Mode final. The waiter resolves local refs to full commit SHAs and performs a GitHub CLI preflight before polling. If authentication, authorization, or gh run list fails, fix that root cause immediately; do not keep waiting on a state where every selected workflow appears missing. Fuzzing is long-running and must not be waited for during routine iteration. Use -Mode opportunistic -IncludeLongRunning to sample it periodically, and use -Mode final -FinalCommit for the final handoff or release commit.

Manual lanes remain available when the plan selects them:

1. Portable CI lane:

   tools/build.ps1 -Configuration Release
   tools/test.ps1
   tools/lint.ps1 -CppMode Changed
   tools/compatibility_interop_smoke.ps1 -Configuration Release
   tools/security_scan.ps1
   tools/github_post_push_audit.ps1
   

2. Local AMD HIP lane:

   tools/build.ps1 -Configuration Release -EnableHip -HipArch gfx1201
   build/Release/superzip_cli.exe gpu-info
   

Rules:

• Do not run broad checks merely because they exist. Run the plan-selected checks, then escalate automatically when evidence points to a wider problem.
• Enterprise-quality changes are not complete until the selected verifier proves the changed behavior, resource bounds, function-contract gate, and security invariants. Performance-sensitive claims must include input bytes, output bytes, compression ratio, CPU/GPU mode, and RAM-only/disk-write evidence.
• Do not launch the GUI unless the user has been warned first.
• Use CLI smoke tests for archive validation.
• Keep HIP_PATH, Visual Studio, and architecture configurable.
• Never commit build output, archives, binaries, logs, or secrets.
• Pinned upstream provenance archives under third_party/upstream/** are the only source-controlled archive exception. Do not commit extracted .dll, .exe, .obj, or package staging output.
• CPU/GPU performance benchmarks must use tools/bench.ps1 in its default memory-only mode. Required proof fields are memory_only=true and disk_write_bytes=0 for both forced-CPU and required-AMD-HIP lanes. Do not run multi-GB filesystem benchmarks during development; use tools/storage_smoke.ps1 or the 64 MiB-capped filesystem smoke only for the archive write/read path.
• CPU/GPU performance benchmarks must compare the same compression level and report input bytes, output bytes, and compression ratio. Use level 5 as the balanced release baseline unless the task is explicitly a level sweep.
• Block-size changes must validate every product option: -BlockSizeKiB 256,512,1024,2048,4096,8192,16384.
• .suzip required-GPU compression-level changes must preserve GPU-native semantics: static/adaptive GPU-prefix blocks are allowed, CPU Deflate/Zstd fallback is not. Tests must prove stronger levels can change ratio on a generated file-agnostic workload and still verify/extract with --require-gpu.
• Run security tests after touching extraction, archive metadata, paths, subprocesses, workflows, or Defender integration.
• Run tools/compatibility_interop_smoke.ps1 -Configuration Release after changing ZIP, TAR, compressed TAR, CPIO, CPIO.GZ, AR, or shared compatibility stream writers. Non-SUZIP create formats must be readable by independent standard readers, not only by SuperZip.
• Run tools/format_matrix_smoke.ps1 -Configuration Release after changing the archive-format registry, CLI format routing, create/extract capability flags, archive auto-detection, overwrite policy, or any adapter whose CLI support should be visible to users. The matrix is registry-driven and must fail when a supported format lacks create/extract coverage or rejects the wrong contract.