Skip to content

Report-only XMLTV guide comparison and channel profiles - #205

Draft
Jumpstile wants to merge 6 commits into
mainfrom
feature/issue-191-expanded-one-guide-taxonomy
Draft

Jumpstile wants to merge 6 commits into
mainfrom
feature/issue-191-expanded-one-guide-taxonomy

Conversation

@Jumpstile

@Jumpstile Jumpstile commented Oct 3, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Add deterministic, report-only XMLTV comparison with same-channel findings, cross-channel event correlations, taxonomy-normalized profiles, freshness, and provenance.
  • Add contextual alias proposals and revisioned knowledge-state plans with explicit apply, import, export, and restore workflows; scheduled comparison emits plans but never applies them.
  • Add opt-in GuideComparison to the existing scheduled refresh path. It consumes validated source results and eligible fresh cache payloads without another acquisition.
  • Bound scheduled XMLTV parsing and candidate generation; reject unsafe free text and sensitive report fields; use handle-relative no-follow knowledge-store operations.

Evidence

  • Invoke-Pester -Path tests/unit -Output Normal: 935 passed, 0 failed, across 81 files.
  • Focused regressions cover parser programme limits, 256/257 observation and candidate boundaries, alias evidence integrity, embedded UNC and quoted-credential rejection, inactive-context suppression, and stale report invalidation.
  • Independent final functional review: PASS.
  • Independent final security review: PASS.
  • Architecture and docs/user/ limitations documentation updated.
  • gitleaks is unavailable locally; hosted secret scanning remains pending with CI.

Required Checks

  • Relevant tests pass locally.
  • CI is pending on this draft PR.
  • Repository and user documentation updated.
  • ADR/contracts reviewed; no ADR change required.
  • Independent functional and security reviews completed (PASS).
  • Regression and bug sweeps completed.
  • Release impact reviewed; this is not a release.

Risk

The comparer remains report-only. It does not acquire sources, merge channels, publish guides, or mutate accepted state. Scheduled comparison is opt-in, uses exact approved bindings, fails closed above documented limits, and leaves all generated knowledge plans unapplied for explicit review.

@Jumpstile

Copy link
Copy Markdown
Owner Author

Formatting correction: commit 03e40ea changes only Prettier formatting in the five schemas identified by run 37148029478. Prettier 3.9.6 targeted check passed; Validate-ConfigSchemas passed; focused Pester passed 76/76 across KnowledgeState, ScheduledGuideComparison, ScheduledRefreshPlanner, ScheduledRefreshRun, and SourceRefreshExecutor; parsed JSON values matched HEAD for all five files; git diff --check passed. Run 37148029478 failed at head 9c639b0 on that formatting step (secret-scan passed). No hosted result is claimed for 03e40ea; exact-head CI follow-through remains with the owner. PR stays draft and behind main; no rebase or merge.

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.

1 participant