compiler validate

The invocation topaz compiler validate main.tpz --language-version 5.21 --format json is expected to exit with 1.

Arguments and rejection

Use topaz compiler validate <dir> with exactly one observation directory and no options.

Reject a missing or extra operand, every compiler, root, language, terminal or format selector, equals forms and all unknown options before loading the bundle.

Require the admitted observation bundle schema and all mandatory members. Reject malformed JSON or JSON Lines, unsupported schemas, duplicate or unsafe member paths, missing members, digest mismatches, nonregular members and symlinks.

Output

Write one human confirmation identifying the directory and its valid observation status to standard output only after the complete validation succeeds.

Write the first validation or input failure to standard error and emit no success confirmation for an invalid bundle. There is no stdout JSON report and --format json is rejected.

Validation covers the manifest, declared members, schemas and internal consistency. It does not claim the observed program compiles successfully or that two different compiler implementations agree.

Exit status

Exit 0 for a valid complete observation bundle, including a valid bundle that records a compiler rejection.

Exit 1 for command misuse, unreadable input, an invalid directory or any bundle validation failure.

Filesystem effects

Read the supplied directory without modifying, repairing or regenerating any member. Reject symlinked members rather than following them outside the bundle.

Do not allocate a compiler workspace, produce a new bundle, delete extra files or rewrite a digest.

Network access

Perform no network access and no lookup of missing schemas or source files from remote locations.

Reproducibility

The same bundle bytes and member paths under the same validator schema registry produce the same validity result. Directory enumeration order does not affect it.

Human paths and operating system error details are environmental output. A valid bundle does not depend on the original source tree still being available.

Packages and locks

Do not load a package from the current directory or regenerate package facts. Package and lock facts stored in the bundle are validated as evidence rather than resolved against a live registry.

The command does not create, verify against the caller package or rewrite its topaz.lock.