Retire #237 from startup; run orientation and mechanical top-five selection in parallel #520
Closed
opened 2026-07-21 01:04:17 +02:00 by timothy
·
3 comments
No Branch/Tag Specified
main
renovate/dotnet-monorepo
renovate/meziantou.analyzer-3.x
renovate/lucene.net
renovate/sqlitepclraw.bundle_e_sqlite3-3.x
renovate/cliwrap-3.x
913-scripted-playout-401
release/v26.15.0-notes
issue-806-guard-populations
scratch/767b-poisoned
scratch/767b-control
release/v26.14.0-notes
release/v26.14.0
docs/510-skill-logo-bug-policy
fix/510-watermark-resolution-policy
fix/629-verdict-classifier-falseopens
fix/609-decisions-edit-token-scope
issue-135-clear-to-none
release/v26.12.0-notes
fix/409b-lastscan-api-parity
fix/401-updatechannel-mirror-422
fix/327-playlist-rename-validation
fix/410-scancancel-log-level
fix/409-447-librariesscreen-neverscanned
fix/338-zap-exit-code
fix/367-plex-budget-message
fix/310-debom-legacy-cs
ci/604-lane-rebalance
feat/388-design-mirror
feat/247-test-ownership
feat/247-primary-action
feat/357-player-owned-playback
feat/357-jellyfin-plugin-poc
fix/289-mcp-hardening
issue58-mcp
feat/244-channels-extract
ci/auto-bump-prod-compose
feat/multi-rerun-collections-api
feat/collections-api
feat/quick-wins
feat/185-docs-part2
feat/140-collections-screen
feat/146-channel-edit
feat/147-classic-ui-link
issue22-renovate-dashboard
feat/91-cutover
feat/63-composite-create
feat/65-library-browse
feat/85-epg
feat/86-schedule-editor
feat/109-dashboard-data
feat/99-session-tracking
fix/dockerfile-node-tag
feat/59-spa-foundation
docs/59-ui-redesign-brief
feat/102-json-guide
feat/111-schedule-durations
feat/104-artwork-upload
feat/103-media-sources-api
feat/playouts-read-api
feat/108-health-api
feat/105-picker-list-endpoints
issue-97-channel-state-api
issue42-jellyfin-musicvideos
issue46-rest-api-error-contract
dependabot/nuget/ErsatzTV.FFmpeg.Tests/multi-d307a2e06f
qsv-improvements
hdr-vulkan-cuda-test
v26.16.0
v26.15.0
v26.14.0
v26.13.0
v26.12.0
v26.11.0
v26.10.0
v26.9.0
v26.8.0
v26.7.0
blazor-final
v26.6.0
v26.5.0
v26.4.0
v26.3.1
v26.3.0
v26.2.0
v26.1.1
v26.1.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.0
v25.1.0
v0.8.8-beta
v0.8.7-beta
v0.8.6-beta
v0.8.5-beta
v0.8.4-beta
v0.8.3-beta
v0.8.2-beta
v0.8.1-beta
v0.8.0-beta
v0.7.9-beta
v0.7.8-beta
v0.7.7-beta
v0.7.6-beta
v0.7.5-beta
v0.7.4-beta
v0.7.3-beta
v0.7.2-beta
v0.7.1-beta
v0.7.0-beta
v0.6.9-beta
v0.6.8-beta
v0.6.7-beta
v0.6.6-beta
v0.6.5-beta
v0.6.4-beta
v0.6.3-beta
v0.6.2-beta
v0.6.1-beta
v0.6.0-beta
v0.5.8-beta
v0.5.7-beta
v0.5.6-beta
v0.5.5-beta
v0.5.4-beta
v0.5.3-beta
v0.5.2-beta
v0.5.1-beta
v0.5.0-beta
v0.4.5-alpha
v0.4.4-alpha
v0.4.3-alpha
v0.4.2-alpha
v0.4.1-alpha
v0.4.0-alpha
v0.3.8-alpha
v0.3.7-alpha
develop
v0.3.6-alpha
v0.3.5-alpha
v0.3.4-alpha
v0.3.3-alpha
v0.3.2-alpha
v0.3.1-alpha
v0.3.0-alpha
v0.2.5-alpha
v0.2.4-alpha
v0.2.3-alpha
v0.2.2-alpha
v0.2.1-alpha
v0.2.0-alpha
v0.1.5-alpha
v0.1.4-alpha
v0.1.3-alpha
v0.1.2-alpha
v0.1.1-alpha
v0.1.0-alpha
v0.0.62-alpha
v0.0.61-alpha
v0.0.60-alpha
v0.0.59-alpha
v0.0.58-alpha
v0.0.57-alpha
v0.0.56-alpha
v0.0.55-alpha
v0.0.54-alpha
v0.0.53-alpha
v0.0.52-alpha
v0.0.51-alpha
v0.0.50-alpha
v0.0.49-prealpha
v0.0.48-prealpha
v0.0.47-prealpha
v0.0.46-prealpha
v0.0.45-prealpha
v0.0.44-prealpha
v0.0.43-prealpha
v0.0.42-prealpha
v0.0.41-prealpha
v0.0.40-prealpha
v0.0.39-prealpha
v0.0.38-prealpha
v0.0.37-prealpha
v0.0.36-prealpha
v0.0.35-prealpha
v0.0.34-prealpha
v0.0.33-prealpha
v0.0.32-prealpha
v0.0.31-prealpha
v0.0.30-prealpha
v0.0.29-prealpha
v0.0.28-prealpha
v0.0.27-prealpha
v0.0.26-prealpha
v0.0.25-prealpha
v0.0.24-prealpha
v0.0.23-prealpha
v0.0.22-prealpha
v0.0.21-prealpha
v0.0.20-prealpha
v0.0.19-prealpha
v0.0.18-prealpha
v0.0.17-prealpha
v0.0.16-prealpha
v0.0.15-prealpha
v0.0.14-prealpha
v0.0.13-prealpha
v0.0.12-prealpha
v0.0.11-prealpha
v0.0.10-prealpha
v0.0.9-prealpha
v0.0.8-prealpha
v0.0.7-prealpha
v0.0.6-prealpha
v0.0.5-prealpha
v0.0.4-prealpha
v0.0.3-prealpha
v0.0.2-prealpha
v0.0.1-prealpha
Labels
Clear labels
ad-hoc
api
bug
ci-cd
content
dependencies
enhancement
frontend
in-progress
jellyfin
parked
priority: high
priority: low
priority: medium
review
security
One-off / ad-hoc work not tracked by a dedicated issue
REST API / HTTP endpoints
Something isn't working
Build, test, deploy pipeline
Channel content / schedules / playlists
Dependency updates (Renovate)
New feature or improvement
ChicoryTV React SPA frontend
Claimed by an active session — do not pick up
Jellyfin tuner / IPTV integration
Excluded from automatic queue pickup; work only when explicitly selected
Adversarial review finding
Security / vulnerability fix
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: timothy/ersatztv#520
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The ChicoryTV arc tracker #237 is closed, but the current handoff and docs still tell fresh agents—and the fallback selector path—to read its body and recent comments during normal startup.
That is now both clunky and unsafe:
scripts/select-queue.shalready performs the live mechanical selection correctly;This issue comes from a bounded knowledge-retrieval audit in
timothy/adversarial-reviewer.Decision
Normal maintenance-mode startup has two concurrent tracks:
scripts/select-queue.sh 5.After both finish, resolve only the selected shortlist's judgment flags, choose/claim the top eligible issue, and retrieve a focused task-specific knowledge packet.
#237 remains closed archival history. It is not required reading and is not consulted for normal ranking. If a future ordered arc is created, it gets an explicit new active tracker/mechanism instead of silently reactivating #237.
Target startup flow
When the user names an issue
When the user does not name an issue
Start these concurrently:
AGENTS.md,CLAUDE.md, and the compactdocs/README.mdknowledge map;scripts/select-queue.sh 5.Then:
CLAIM?andUMBRELLA?rows and for the eventual winner.Knowledge retrieval rules
docs/README.mdshould map task signals to the minimum relevant sections.Infrastructure work to mirror Gitea history—including #237—into MemPalace is tracked by
timothy/server-management#642. This issue must remain usable before that dependency lands by documenting the exact-search fallback.Structured future closing record
Agents keep posting the closing record on the issue they actually worked. Do not introduce a second manually maintained per-session Markdown ledger.
Standardize a concise close-comment shape suitable for humans and later MemPalace export:
Durable decisions still go into the decision/convention Markdown in the same PR. The issue comment is evidence and implementation history, not the only home of an engineering rule.
Scope
docs/README.mdfrom a mandatory full reading order to a compact authority/task map.CLAUDE.mddocs-first guidance to require the map plus relevant sections, not the whole corpus.scripts/select-queue.shcomments/output so its active tiers begin with open milestones/review/priorities and no longer say "read #237."Out of scope
Done-when
scripts/select-queue.sh 5are explicitly concurrent when no issue is named.docs/README.mdmaps task signals to minimal authoritative reading instead of requiring the full corpus.Claiming (Claude Code, Opus 4.8). Working #520 + #521 together as one knowledge-retrieval arc: build #521's keyed decision-lifecycle schema + generated active catalog (docs/decisions/README.md) + lifecycle validator (replacing the append-only line guard while keeping its spirit; retiring the [decisions-edit] token), then rewire #520's startup/kickoff to point at the compact active view + parallel select-queue.sh, with a regression check that blocks re-treating #237 as live state. Full entry migration fanned out to subagents. Single [decisions-edit]-tagged PR.
Machinery for the retrieval side landed in PR1 (#526, merged
f4bebd77) — the generated active catalog (docs/decisions/README.md) +archive/wing that the #520 orientation block will point agents at.#520 itself stays open — its startup/kickoff rewrite is PR2: retire #237 from normal startup, parallel orientation ‖
select-queue.sh, thecheck-kickoff-guard.shregression guard, the## Closing recordtemplate, and the Knowledge-retrieval orientation block carrying the four bullets coordinated with server-management#642 (catalog-first;Gitea-ErsatzTV= evidence-not-authority; the breadcrumb rule — a file path named in a historical comment is a breadcrumb, not a live pointer, resolve by concept; catalog→rgfallback, MemPalace never authority). #642 confirms its 283-issue export is live + tiered and is retrievable-but-unreached until this block ships.Closing record
Outcome: Shipped via PR #527 (merged
063017584d7f09619162e818f2db922776bbbdd4). Normal startup no longer reads the closed tracker #237: two concurrent tracks when no issue is named (orientation ‖scripts/select-queue.sh 5), named-issue skips selection → focused retrieval.docs/README.mdis a task-signal map (not a mandatory 1–10 read); the kickoff carries the four server-management#642 knowledge-retrieval bullets (catalog-first; Gitea history = evidence-not-authority; the breadcrumb rule; catalog→rgfallback).## Closing recordstandardized as the per-issue durable artifact.scripts/check-kickoff-guard.sh(wired to CI) blocks any regression to treating #237 as live state.Root cause: n/a (enhancement). The underlying problem — status/queue-state asserted in append-only prose that drifts — is the same throughline as #521.
Decisions/conventions changed:
docs.queue-state-gitea-tracker(#237) superseded bystartup.parallel-orientation(reciprocal links; archived todocs/decisions/archive/startup.md). Pre-script selector lore demoted to a labeled archival section.Reusable knowledge: The load-bearing artifact for making mined knowledge reached is the startup orientation block — the export is inert without it (the #642 seam). A file path named in a historical comment is a breadcrumb, not a live pointer.
Verification: Startup cold-agent sim PASSED — a fresh agent with live Gitea access chose not to read #237, ran select-queue.sh, went catalog-first, understood the breadcrumb rule. kickoff-guard non-vacuity proven (fails pre-rewrite, passes post). Whole-branch adversarial review confirmed complete+correct.
Deferred: MEMORY.md
queue-protocol-gitea-trackernote update (operator auto-memory, not repo — done this session).Docs updated:
docs/handoffs/chicorytv-issue-queue.md,docs/README.md,CLAUDE.md,scripts/select-queue.sh,docs/decisions.md+docs/decisions/archive/startup.md.