Skip to content

Validate filter programs after the option terminator #513

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem and evidence

The read-only command guard stops inspecting filter content after an option terminator. An offline fixture demonstrates that a normally refused jq program is admitted in that form and can read a synthetic environment canary.

Expected outcome

Ending option parsing must not exempt the program operand from read-only classification. The same program must have the same classification in every supported argument form.

Acceptance criteria

  • Reproduce the admitted and rejected forms with the native filter command.
  • Validate the program after an option terminator.
  • Preserve supported literal filters and reject unresolved program operands.
  • Retain environment and file-access restrictions.
  • Run guard and installed adapter tests.

Rough size: S. Part of #223.

Activity

  1. added theissue type on Oct 5, 2026
  2. self-assigned this
    on Oct 5, 2026
  3. added a commit that references this issue on Oct 5, 2026
  4. devantler commented on Oct 5, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered in merged PR #519 (merge commit 08b218e). The exact reviewed head passed native required CI, the 425 guard regressions, raw JSON observations and surveyor adapter validation. The accompanying repairs now preserve option context and reject malformed original Unicode evidence before identity comparison.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions