Skip to content

Define diagnostics and artifact modeling for pipeline results #393

@DamianReeves

Description

@DamianReeves

Background:

  • Pipeline design calls for structured diagnostics and artifacts.

Scope:

  • Define Diagnostic and Artifact types with severity, code, message, location, and metadata.
  • Ensure data serializes cleanly for JSON output and analyzer use.

Acceptance criteria:

  • Diagnostic and Artifact types in pkg/pipeline (or subpackage).
  • JSON encoding tests cover severity and location fields.

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