Skip to content

Refuse repaired or erased forge input bytes #495

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The forge observers can replace malformed UTF-8 during JSON decoding or erase literal NUL bytes during shell capture, then classify the altered observation as healthy or fully resolved.

Proposed direction

Repair the owning observation or output boundary, with a regression that fails on current main before changing the implementation. Preserve the existing conservative behavior and public interface.

Acceptance criteria

  • Validate original producer bytes before shell or JSON decoding can alter their identity.
  • Refuse malformed or incomplete inputs with UNKNOWN and empty stdout, including partial producer failures.
  • Keep valid Unicode and literal replacement characters valid; cover both CI-run classification and review-thread collection.

Size: S/M. Part of #223.

Activity

  1. added theissue type on Oct 4, 2026
  2. self-assigned this
    on Oct 4, 2026
  3. moved this from 📥 Backlog to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 4, 2026
  4. added a commit that references this issue on Oct 5, 2026
  5. devantler commented on Oct 5, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered by merged PR #503 at commit 3c7067e, with current-head native CI, independent review and installed-command evaluation recorded on the PR. Plugin 6.1.7 preserves original producer observations and assessment chronology; generated pins agree.

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