Skip to content

Attribute Node/BAML and resolver handoff outputs in closeout audit #1226

Closed as not planned

Description

@ViperJuice

Observed gap

While closing Consiliency/jev-assembler#10 in a newly created, initially clean owned worktree, the installed phase-loop-closeout-audit returned exit 1 for actual outputs of frozen npm installation, TypeScript build, the pinned BAML compatibility check and resolver-generated handoffs. Runtime source is release 0.7.21; the same classifier on merged Consiliency/agent-harness main recognizes Python caches and node_modules but has no measured producer mechanism for these outputs.

Actual buckets: runner_owned .phase-loop/; tool_cache node_modules/; unknown_ignored .baml/.gitignore, .baml/cache/, .baml/profiles-v1.lock, .baml/profiles-v1/, .cache/, .dev-skills/, dist/, generated/baml/. No contents, profile values or credentials were inspected. The target plan and actual sealed commands own/generated these outputs. All current source hashes and runner validation pass.

The module also ignores --help and audits the current directory instead, returning a failure without usage text.

Desired bounded fix

Add supported producer attribution for measured Node/BAML build outputs and resolver-owned handoffs, with deny-by-default path containment. Do not broadly trust arbitrary .cache contents or files/symlinks borrowing a cache name. Keep unknown user/private outputs blocking and add negative cases alongside the real tooling cases. Give --help an actual read-only usage response.

Current workaround

Preserve only this run's generated outputs in its declared .phase-loop/runs/... archive, recording original paths and producers; rerun the unchanged classifier. No classifier verdict, evidence seal, credential value or source code is changed. This is a separate runtime usability gap; it does not add source scope to the fixture repair.

Activity

  1. ViperJuice commented on Oct 2, 2026

    @ViperJuice
    CollaboratorAuthor

    Duplicate of #1139. The fresh Node/BAML reproduction, deny-by-default acceptance constraints and intact-output archive workaround have been added to that existing open issue. The separate --help observation is retained in the added evidence; this closure does not mark the underlying defect fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions