logcompact-builtins
logcompact-builtins is the provider-neutral built-in parser pack for
logcompact-core. It recognizes common compiler, linter, runtime, and
test output without requiring a CI provider, build system, process runner,
database, or async runtime.
The repository develops three publishable packages together:
| Package | Responsibility |
|---|---|
logcompact-core |
Streaming scopes, parser lifecycle, provenance, policies, bounds, and finalization |
logcompact-builtins |
Fixed language/test parser pack, bounded problem matcher compiler, and batch compatibility API |
logcompact |
Incremental file/stdin input and human, JSON, JSONL, SARIF, and GitHub presentation |
Batch API
use ;
let result = reduce;
assert_eq!;
assert_eq!;
Streaming API
use ;
let mut session = new;
session.begin_scope;
session.push_chunk;
session.push_chunk;
session.end_scope;
let result = session.finish;
Chunk boundaries do not affect results. Each scope has an explicit end reason, and incomplete test segments do not emit structured blocks whose confirmation may have been truncated. The built-in plan has a fixed parser order; runtime plugin discovery is not part of the contract.
Paths are mapped before strings are redacted. Redaction covers messages, paths,
test names, framework names, and provenance before exact deduplication, ranking,
serialized-byte accounting, or return. Production consumers should normally
provide a Redactor instead of NoRedaction.
The generic pack does not understand provider workspaces, action mnemonics, build-event protocols, or provider-specific status messages. Those rules belong in downstream adapters, which can feed mapped findings through the same output-policy boundary.
Problem matcher API
Self-contained GitHub Actions and inline VS Code problem matcher definitions can be compiled before input begins and appended to a parser plan:
use ;
let mut registry = default;
registry.add_json.expect;
let plan = builtin_parser_plan_with_problem_matchers;
The registry performs no I/O. It validates all definitions and compiles their
bounded state machines atomically. A custom owner matching a stable built-in
owner replaces that built-in; other owners extend the plan. See the
repository's PROBLEM_MATCHERS.md for
compatibility details.
Run make boundary from the repository root to verify that no provider-specific
semantics or workspace-internal dependencies have leaked into these packages.