[Jumpstile]

Summary

• Expand the One Guide built-in taxonomy to the owner-approved sports and content categories.
• Map generic Sports to other-sports only when no specific recognized sport category exists, including across grouped canonical-event offerings; continue omitting unknown XMLTV categories.
• Keep the category registry canonical across projection, schema, tests, and documentation.
• Preserve PR feat(one-guide): add read-only accepted-guide API #199's unavailable-guide HTTP 503 versus valid-empty HTTP 200 behavior.

Part of #191.

Verification

Current pushed head: 0055211fb2f11b3838ecc7a1c7b17726ffa0fb73 (verified 2026-10-01 UTC).

• Exact-head PowerShell CI run 36885417355: completed SUCCESS.
• The latest commit treats the explicit Other Sports alias as generic Sports for precedence and adds regression assertions for Other Sports alone and Other Sports with Football.
• Exact current-head delta review is pending. Earlier review and local QA below apply to 492e044a8ab1fa2253b79f126178c43062f6bf75; they are not a substitute for reviewing the later source/test change.

Earlier-head evidence retained for provenance

• OneGuide focused suite: 13 passed, 0 failed, under Pester 5.7.1 / PowerShell 7.6.6 / .NET 10.0.12.
• Full local Pester: 870 passed, 0 failed, 1 skipped.
• Hosted CI run 36852657473: 871 Pester, 101 GUI and 24 Rust tests passed. The tested merge commit 6d4adef had the same file tree as 492e044.
• All 23 categories returned expected items in bounded smoke checks; encoded JSON hashes matched repeated/reversed input checks.
• Eight paired base/head visual states had identical files and zero differing pixels. Six committed screenshot baselines failed identically on base and head; this is not demonstrated candidate-caused regression and is not a claim of committed-baseline conformance.
• Local GUI evidence used Node 26; supported Node 22 hosted evidence is identified separately.
• Bounded independent review accepted the core taxonomy behavior. Explicit Other Sports semantics and permanent membership coverage were follow-up questions under the written acceptance at that reviewed head. The explicit alias behavior has since changed in the current commit and requires its delta disposition.

Remaining gates and scope

• Finish the current-head delta review and document whether a separate mandatory committed-baseline pass applies.
• Preserve exact-head evidence and owner release/merge approval requirements; no merge or release clearance is claimed by this update.
• No SER8 performance certification is claimed by this taxonomy-only slice.

[Jumpstile]

Exact-head local gate and pending review — 2026-10-02

Accepted local full-suite evidence is for exact HEAD 0055211fb2f11b3838ecc7a1c7b17726ffa0fb73: 871 passed, 0 failed, 0 skipped; PowerShell 7.6.6 / Pester 6.1.0; exit 0; duration 00:32:19.142. Raw receipt: C:\Temp\cf191-full-pester-0055211.log and .exit. The verified UTC provenance record at C:\Users\EliSi\Documents\Codex\2026-10-01\task\CF-Verified-UTC-Gate-Provenance-20261001.txt records the same HEAD/origin before and after this local run (started 16:51:48Z; completed about 17:24:09Z). No suite rerun was performed.

Separate process disposition: docs/engineering/ENGINEERING_PRINCIPLES.md requires the full local suite before commit. The passing run was post-commit and does not retroactively satisfy that chronology; the pre-commit process miss remains for owner disposition.

The required exact-current-head independent review remains pending; no exact-0055211 verdict exists. The configured route is sol-escalation at openai-codex/gpt-6.1-sol:high in the existing C:\REPOS\ChannelForge\.omp definitions. This runner rejected that custom agent as unknown; no substitute reviewer/model was used. PR remains unmerged; this evidence grants no merge/release authorization.

[Jumpstile]

Correction to the review-status statement in #201 (comment): a generic PR201TaxonomyReview reviewer was briefly started and partially inspected the diff/source, then canceled before producing a verdict. It returned no findings and does not satisfy the configured exact-SHA Sol High review gate. Separately, an earlier direct sol-escalation dispatch failed preflight with Unknown agent and launched no Sol task. This correction records those attempts; it does not claim either was a completed review or verdict.

[Jumpstile]

Validation update for PR #201 / issue #191, 2026-10-02 UTC

Current GitHub head was rechecked before this update and remains 0055211. The PR is open and unmerged.

The configured independent escalation completed against that exact head, with the full result retrieved at 06:54 UTC. The bounded taxonomy-source review passed and found no source-change defect. Registry, schema, types, tests, and documentation match the owner-approved 23-category taxonomy. Generic Sports is suppressed when a recognized specific sport is present. This updates the pending-review status in the earlier comments; the earlier attempt/cancellation history remains part of the record.

New actual-server HTTP smoke evidence:

• Receipt: CF-201-OneGuide-Smoke-0055211-5e6c6d3cc0c6427daae3eb46f65a9e5c.json
• Run: 2026-10-02 07:17:06–07:17:43 UTC; PASS, 108 assertions
• Used Start-ChannelForgeWebServer on 127.0.0.1 with disposable fixtures
• Covered unavailable HTTP 503, valid-empty HTTP 200, all taxonomy routes, generic and grouped Sports precedence, deterministic repeats, invalid-category handling, and read-only GET behavior
• Six source hashes were unchanged before/after. The actual accepted pointer was absent before/after. The saved 07:19 UTC status confirmed cleanup of the disposable fixtures and runner; the receipt was retained

Evidence boundaries remain important:

• Previously verified full local Pester remains 871 passed, 0 failed, 0 skipped. That run was post-commit and does not cure the pre-commit chronology miss, which remains for owner disposition.
• Hosted CI run 36885417355 passed on synthetic merge 807499f, whose tree matches the PR head. It was not a literal checkout of 0055211.
• The review and smoke establish bounded taxonomy/API evidence. They do not establish cross-version occurrence-ID stability, full-product certification, physical SER8/provider certification, or committed screenshot-baseline conformance.
• This update grants no merge or release approval.

Hosted CI: https://github.com/Jumpstile/ChannelForge/actions/runs/36885417355

[Jumpstile]

Owner-approved one-time chronology exception — 2026-10-02 UTC

For PR #201 at the exact head 0055211, the full local Pester suite ran after the commit rather than before it. The owner approved accepting this specific chronology exception and merging this exact head.

Evidence recorded for disposition: the full local suite passed 871/0/0 post-commit; the bounded exact-head source review passed; actual-server HTTP smoke passed 108 assertions; hosted run 36885417355 succeeded on synthetic merge commit 807499f with a tree equal to the PR head, but was not a literal checkout of the head SHA.

This is limited to the pre-commit chronology requirement for this PR/head and is not broader product certification or release approval.