Use agent verification artifacts

The agents-artifacts/ directory keeps the complete output from the final verification that follows an OpenSpec apply. Use these files to review a failed check, inspect reported findings, or confirm what the verification agent ran.

Run the commands on this page from the repository root.

Know which artifact to open

The verification agent runs all three checks independently. A failure in one check does not prevent the other checks from producing output.

Artifact	Command	What it contains
agents-artifacts/biome-lint-output.txt	npm run lint	Biome lint diagnostics and command output
agents-artifacts/biome-format-output.txt	npm run format	Files checked or changed by the Biome formatter and any formatter errors
agents-artifacts/semgrep-output.txt	semgrep scan --disable-version-check --config auto .	Semgrep scan progress, findings, and errors

Each run overwrites these files, so they describe only the most recent verification. The apply summary reports the exit status for each command; use that status together with the corresponding artifact.

Review the results

Open an artifact directly, or search all three for a path or diagnostic:

sed -n '1,200p' agents-artifacts/biome-lint-output.txt
sed -n '1,200p' agents-artifacts/biome-format-output.txt
sed -n '1,200p' agents-artifacts/semgrep-output.txt

rg -n "error|warning|finding" agents-artifacts

Interpret the results with these constraints:

• The exit status in the apply summary says whether the command completed successfully. A short or empty artifact does not prove that a check passed.
• Lint and Semgrep findings are reports, not authorization for the agent to change the affected code. Decide on any follow-up fixes separately.
• The repository's npm run format script runs Biome with --write. Review git diff after verification because this check can update formatted files.
• A successful Semgrep command means that the configured scan completed. Read semgrep-output.txt for findings instead of treating its exit status as a finding count.

Reproduce the artifacts

Install the repository dependencies and Semgrep before reproducing a run. Run each command separately, record its exit status immediately, and continue even when a previous command fails:

npm run lint > agents-artifacts/biome-lint-output.txt 2>&1
npm run format > agents-artifacts/biome-format-output.txt 2>&1
export SSL_CERT_FILE="${SSL_CERT_FILE:-/etc/ssl/cert.pem}"
export SEMGREP_LOG_FILE="${SEMGREP_LOG_FILE:-/tmp/template-harness-semgrep.log}"
semgrep scan --disable-version-check --config auto . > agents-artifacts/semgrep-output.txt 2>&1

The redirection replaces the previous artifact and captures both standard output and standard error. Do not join these commands with &&; doing so would skip later checks after the first failure.

The Semgrep environment variables preserve any existing overrides. Their defaults give Semgrep's native client a CA bundle on macOS and keep its runtime log in a location writable by sandboxed verification agents. Disabling the version check also prevents Semgrep from trying to update its user cache during the scan.

After the format command, inspect the working tree before deciding whether any formatting changes belong to the current work:

git status --short
git diff

For the broader change workflow that triggers this verification, see RuleSync and OpenSpec.