Skip to content

Fixture catalog safeguards and shared Library policy (clean history) - #6

Draft
ksudo-dev wants to merge 2 commits into
mainfrom
review/fixture-catalog-clean-20261006
Draft

ksudo-dev wants to merge 2 commits into
mainfrom
review/fixture-catalog-clean-20261006

Conversation

@ksudo-dev

@ksudo-dev ksudo-dev commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

Scope

  • fixture-only monitor confirmation remains isolated from configured ARR transports
  • strict TVmaze poster validation and the explicit authenticated shared-Library policy
  • full reachable-ref public-safety scanning remains enabled

Historical fixture exception

Two synthetic historical discovery-catalog fixture forms matched generic deployment-data detectors. The scanner exception is pinned to the exact historical Git blob, file path, rule, and value for those forms only. It does not exempt future copies, a different blob or path, arbitrary private addresses, email-shaped values, tokens, or working-tree content. No history was rewritten.

Validation

  • public-safety full reachable-ref scan: passed
  • focused catalog/admin/security fixtures: 8/8
  • backend suite: 90/90
  • browser flows: 2/2
  • GitHub CI: all checks passed

Review relationship

PR #5 is preserved for audit and superseded for review by this clean-history PR. It has not been closed or deleted.

Limits

  • monitor execution remains fixture-only; no production ARR write path is enabled
  • no production runtime refresh or deployment is included

@ksudo-dev ksudo-dev self-assigned this Oct 18, 2026
@ksudo-dev
ksudo-dev force-pushed the review/fixture-catalog-clean-20261006 branch from 4159e5e to 207c3bd Compare November 15, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants