@afix-ci/pcheck-win32-x64 0.1.0-rc.52

package/README.md

@@ -0,0 +1,60 @@
+# pcheck
+
+Precompiled pre-commit and pre-push checks for repositories that use `mx`.
+
+Run the standalone CLI with `pcheck pre-commit` or `pcheck pre-push`. The same
+commands are available through `mx pcheck`.
+
+On first use, pcheck materializes repository policy at
+`.config/pcheck/config.toml`. The configuration controls email and branch
+patterns, package-manifest newline policy, staged-file size limits and
+allowlisting, the slow-task warning threshold, and parallel/sequential host
+commands. Command entries use `CfgBinSpec`: repository-root paths start with
+`/`, config-relative paths contain `/`, and bare command names resolve through
+`PATH`. Pcheck validates both regexes, positive thresholds, and every configured
+command before starting hook checks.
+
+During `pre-commit`, pcheck snapshots staged, non-deleted Git paths once and
+writes them as UTF-8, NUL-delimited repository-relative paths. Every configured
+command receives the absolute manifest path in `PCHECK_STAGED_FILES_FILE` and
+an initially empty generated-path manifest in `PCHECK_GENERATED_FILES_FILE`,
+plus the absolute working-tree root in `PCHECK_REPO_ROOT`. Both manifests are
+UTF-8, NUL-delimited repository-relative paths. Paths are passed without shell
+interpolation; a staged path that cannot be represented as UTF-8 is rejected
+before host commands run.
+
+Before launching host commands, `pre-commit` validates the effective Git
+`user.email`. When there are no staged paths, it exits without workspace
+discovery or host command startup. Otherwise, it checks the final byte of the
+root and workspace-member
+`package.json` files and checks working-tree sizes for staged, non-deleted
+paths. Missing staged files are ignored, and oversized files are permitted only
+when their repository-relative path matches `file_size_allowlist`. Workspace
+manifests are discovered from tracked Git index entries without parsing their
+contents or walking the worktree; a spinner reports this initial discovery and
+a one-line message reports the repository scan time.
+
+For repository-scan profiling, `pre-commit --skip-index-check` bypasses staged
+index discovery, uses a full filesystem walk for workspace-manifest discovery,
+and forces the remaining checks to run with an empty staged manifest.
+`PCHECK_SKIP_INDEX_CHECK=true` provides the same behavior.
+
+Package newline and staged-file size checks run alongside every `parallel_cmds`
+entry. After all parallel work settles, `sequential_cmds` run in configured
+order even when an ordinary check failed, allowing formatters to repair files.
+Command construction and process-launch errors stop the remaining sequence.
+After the sequence, pcheck re-stages every originally staged path and each
+validated, deduplicated generated path reported through the generated manifest,
+then persists the Git index once. Generated entries containing absolute paths,
+traversal, or malformed records are rejected.
+Failed command output is buffered and replayed as one block; successful output
+is available at debug verbosity. Every completed task prints a one-line elapsed
+time, records its phase, elapsed time, and staged-file count, and emits a warning
+when it exceeds `slow_task_threshold_ms`.
+Run `cargo bench -p pcheck-cli --bench native_checks` to measure staged-input
+extraction, package-manifest newline checks, and staged-file allowlist matching.
+
+During `pre-push`, pcheck reads Git's standard four-field ref update records
+from stdin and validates every non-deleted `refs/heads/*` destination against
+`branch_regex`. Tag updates and branch deletions are ignored. When `TF_BUILD`
+is set, pre-push validation is bypassed for Azure Pipelines.

package/package.json

@@ -0,0 +1,18 @@
+{
+  "name": "@afix-ci/pcheck-win32-x64",
+  "version": "0.1.0-rc.52",
+  "license": "MIT",
+  "preferUnplugged": true,
+  "os": [
+    "win32"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "files": [
+    "cli.exe"
+  ],
+  "bin": {
+    "pcheck": "./cli.exe"
+  }
+}