Skip to content

Peritus v0.1.12

Choose a tag to compare

@dollspace-gay dollspace-gay released this 26 Oct 21:31
· 42 commits to main since this release
6fd71b9

Peritus 0.1.12

Peritus 0.1.12 fixes candidate acceptance for Make-owned projects and data workspaces. A project
with a Makefile can now use an explicitly declared check, verify, or validate target instead
of stopping with the missing check-contract error reported in issue #155. Target selection prefers
the full check target; Peritus never selects a default or arbitrary Make target.

Otherwise unrecognized changed files receive scoped host-owned readability and JSON/YAML
structural checks. Those observations establish file readability and syntax where applicable;
they do not establish that arbitrary software behavior is correct. Existing language-specific
checks and the independent review workflow remain in place. Recognized Rust and other language
projects do not receive duplicate Make commands.

This release also includes the merged generic module runtime preparation changes. Source-built
modules can prepare application dependencies and request Bun within disposable laboratories,
using the same scoped module interface. Specialized Red Team behavior remains in the separately
distributed Module Market package.

The issue #155 campaign first reproduced incomplete coverage for a Makefile and modpack-data
paths. Its saved public API consumer then linked against the complete daemon build, read all
changed fixture files, selected make check, and observed the full command's successful output.
Additional real consumers exercised generic-file fallback, Makefiles without supported check
targets, and Rust projects containing Makefiles. The changed gate and product-runner packages
passed build/check, formatting, and strict Clippy.

Six native archives cover Linux, macOS, and Windows on x86-64 and ARM64. Package assembly validates
the complete payload and version metadata. Unix package jobs additionally install the archive and
operate the actual offline terminal with disposable data. No unit, mock, formal-verification, or
repository qualification suites are part of this release workflow. The private local Chrome
extension and local Red Team campaign artifacts are excluded from the published source.