Skip to content

friction log: scope declared per-cycle checks to applicable cycles instead of stamping n/a #76

Description

@geuben

Problem

A plan-declared per-cycle check that only applies to some cycle types is stamped on every cycle anyway, rendering as n/a noise on the rest. Observed: a plan declared an artifact-verification check relevant only to cycles that exercise a particular output format; all 19 cycles ran on a plain unit-test runner, so the log carries 19 × …_status: n/a (<runner> cycle) lines and the one place the check would have mattered is indistinguishable from the noise. (In that run the check consequently never actually executed against a real artifact — the n/a wallpaper hid that the plan's verification hook had zero effective coverage.)

Proposal

  • Let the contract scope a declared check to a subset of cycles: by explicit cycle list, by project, or by a per-cycle boolean — e.g.

    checks:
      - name: artifact_verify
        applies_to: [12, 19]   # or: projects: [device-suite]
  • Render only the cycles the check applies to; if a check applies to zero executed cycles, surface that as a warning in the run summary ("declared check never ran") instead of n/a lines — that inversion is the actually useful signal.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions