vizuh Verify ClickTrail
Use the host project's own environment and documented commands.
- Read project instructions and
../../references/clicktrail-safety-contract.md. - Inspect every proposed command and the underlying package script before running it. Announce read-only registry metadata requests before making them.
- Ask before any command that can call a live service, access a network other
than read-only package metadata, mutate persistent state, or run an unclear
e2e, deployment, publication, or integration script. - Confirm installed package versions and registry dist-tags without changing them.
- Run focused consent, withdrawal, redaction, destination, retry, and tenant boundary tests before the full test suite.
- Run approved typecheck, lint, and build commands using the project's package manager.
- Inspect packed artifacts when the task concerns publication. Confirm license, manifest, expected files, exact internal versions, and absence of secrets or internal documentation.
- Use a clean-room import when verifying a package release.
- Do not call a live collector by default. A user must name and authorize a safe test endpoint explicitly.
Return a compact evidence table with command, result, and artifact or log path. Separate local readiness from remote CI, registry ownership, and publication authorization.