Skip to content

L01-11 — Stop isolated over-limit ink regions passing ink coverage #116

Closed

Description

@mberrys

Outcome

ink-coverage reports every over-limit region above a physically justified minimum size.

Parent and boundary

Parent: #2. Owner: LoopLibCore. This issue owns one bounded slice of Evidence Core; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Grounding

  • Preflight coverage backlog row ink-coverage-raster-tac (P2, open, unfiled): ink-coverage is a raster probe that suppresses regions below min_region_area_pct, so an isolated over-limit element passes clean.
  • P2 means the named limitation can turn a defective document into a clean pass, which contradicts the L01 exit gate.

Acceptance

  • A regression-class fixture that reproduces the defect is committed first and is shown to pass clean before the change.
  • The suppression floor is expressed in physical area (mm²) tied to press behavior, not a percentage of page area; regions below probe resolution report incomplete.
  • The check then reports a finding, or check-incomplete where a residual limitation remains; it never reports a clean pass on the fixture.
  • docs/preflight-check-catalog-overlay.json moves ink-coverage-raster-tac to landed (or narrows its gap text), the corpus-coverage map lists the fixture, and python scripts/generate-architecture-catalogs.py --check passes.
  • Failure case: a small rich-black element far above the total-area-coverage limit on a large page must not pass clean.

Required proof

Before/after report snapshots for the new fixture and the unchanged golden corpus. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap · Gap review of the issue suite against the approved roadmap, 2026-09-27.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Promotion stage

    Stable present

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions