Skip to content

Six-Month Delivery Gate — fully usable One Guide living-room product by March 2027 #190

Open

Description

@Jumpstile

Product-owner deadline

ChannelForge must not become a multi-year architecture project.

Target: a fully usable living-room product by March 31, 2027.

This is a delivery constraint for #62 One Guide, Every Screen and the SER8 reference experience. Architecture, research, refactors, and provider integrations must be sequenced to produce usable vertical slices continuously rather than postponing value until every planned subsystem exists.

Primary product outcome

By the target date, a normal user should be able to:

  1. install/start ChannelForge on a supported host/reference setup;
  2. connect the services they already use through a simple Connect Your Services workflow;
  3. safely add IPTV/M3U/XMLTV/XC sources;
  4. see what each connected provider can actually expose;
  5. receive one normalized live-programming guide plus useful filtered views;
  6. browse Guide, Live Now, Starting Soon, Sports, Wrestling, and Search;
  7. see one canonical event when several providers carry the same event;
  8. press one remote button to launch the best supported authorized source;
  9. return reliably to the ChannelForge home surface;
  10. operate the SER8 reference client with the Harmony Elite without routine keyboard/mouse use;
  11. survive restart, provider failure, refresh failure, and credential expiry without losing last-known-good state;
  12. understand in plain language when a provider cannot expose a capability ChannelForge would like to use.

Initial service targets

The six-month product must design for and attempt supported integration with the user's core service classes:

  • DIRECTV Stream
  • Disney+
  • ESPN / ESPN+ / ESPN Unlimited
  • Netflix
  • YouTube
  • Plex / Plex Live TV
  • IPTV / M3U / XMLTV / XC

A provider does not block the release merely because its current public/supported integration surface cannot expose every desired capability.

For each provider, ChannelForge must truthfully declare what is available:

  • account connection/authentication
  • live channel enumeration
  • schedule/guide metadata
  • scheduled/live event metadata
  • entitlement/availability evidence
  • search/discovery metadata
  • launch/deep-link/browser target
  • refresh behavior
  • interactive reauthentication requirement

Unsupported capabilities remain explicit. Do not bypass DRM, authentication, access controls, provider terms, or regional restrictions to make a matrix look complete.

Delivery principle

Vertical slice before framework expansion.

Every major architectural abstraction must be proven by a real end-to-end user path as early as possible.

Do not build:

  • a generalized framework with no working provider;
  • a canonical model with no client using it;
  • a credential vault with no connected service;
  • a guide API with no remote-controlled guide;
  • a launcher layer with no real provider launch.

Six-month sequencing

Phase 1 — Foundation closure and platform decision

Target: October 2026

Exit: one documented architecture that is small enough to implement immediately, with no unresolved platform question blocking development.

Phase 2 — First real cross-provider vertical slice

Target: November 2026

Deliver one working path from account/source connection through guide to launch:

  • IPTV/M3U/XMLTV as the mature baseline;
  • Plex/Plex Live TV as the first rich media-server provider;
  • at least one real streaming provider capability adapter;
  • ChannelForge canonical guide query;
  • first 10-foot guide client on SER8;
  • Harmony navigation for Home/Guide/Back/Select;
  • one-action launch and reliable return to Home.

Exit: the system is demonstrably more than an IPTV formatter.

Phase 3 — Core provider expansion and event identity

Target: December 2026

Exit: a user can browse a useful cross-provider live guide and launch content from the couch.

Phase 4 — Reliability, authentication lifecycle, and zero-touch refresh

Target: January 2027

Exit: daily household use does not require developer intervention.

Phase 5 — Product completion and usability

Target: February 2027

  • Universal Search integration.
  • Remote-complete text/search fallback.
  • Guide filters/projections and favorites needed for daily use.
  • Polish source-selection behavior.
  • Simplify setup decisions.
  • Performance profiling on the SER8.
  • Full documentation and screenshots.
  • Clean-install / upgrade / recovery testing.

Exit: feature-complete release candidate for the six-month target.

Phase 6 — Certification and usable release

Target: March 2027

  • Real household soak testing.
  • Exact-head quality/security gates.
  • Provider capability matrix verified against current behavior.
  • Remote-only living-room smoke suite.
  • Upgrade/restart/failure recovery certification.
  • Fix release-blocking UX/reliability defects only; defer nonessential expansion.
  • Produce a reproducible downloadable release.

Exit: fully usable ChannelForge One Guide product by March 31, 2027.

Six-month release-driving issues

Required core:

Event/sports path:

Output/client compatibility:

Other broader portfolio issues must not delay this product unless they are proven release blockers.

Scope discipline

The target is fully usable, not “every conceivable capability complete.”

For this release, defer work that does not materially improve:

  • service connection;
  • guide quality;
  • content/event identity;
  • source selection;
  • playback launch;
  • remote usability;
  • reliability;
  • security;
  • beginner setup.

Examples of likely defer candidates unless directly needed:

  • broad household-profile sophistication;
  • generalized recommendation systems beyond source selection;
  • extensive analytics/telemetry;
  • exotic downstream targets;
  • provider features unrelated to discovery/guide/launch;
  • architectural generalization without immediate product use.

Required engineering behavior

  • Ship small end-to-end increments.
  • Maintain docs with every slice.
  • Keep main releasable.
  • Prefer proven provider-specific adapters behind a stable boundary over premature generic frameworks.
  • Reuse existing ChannelForge deterministic, immutable, LKG, evidence, provenance, and review contracts.
  • No rewrite of working foundations unless measured evidence requires it.
  • No provider can silently become a new system of record.
  • No security shortcut to hit the date.

Definition of "fully usable"

A release qualifies when it can be installed, configured, operated from the couch, refreshed, recovered, and upgraded by a normal user; the guide provides meaningful cross-provider value every day; supported content launches predictably; provider limitations are understandable; and routine use does not require source editing, shell commands, keyboard/mouse interaction, or developer intervention.

The six-month date is a scope-control mechanism, not permission to lower quality or security. When schedule pressure appears, reduce nonessential scope before reducing correctness, security, or recoverability.

Activity

  1. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Product-owner priority update: #191 is now release-driving. Guide quality is the primary product-quality metric. Provider breadth must not outrank correctness, completeness, freshness, classification, deduplication, or useful couch-first presentation.

    If schedule pressure forces a tradeoff, ship fewer well-supported providers with an excellent guide rather than many weak integrations. Category-first discovery (Wrestling, Football, Baseball, Soccer, Movies, News, etc.) is part of the six-month usable-product definition.

  2. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Implementation-speed refinement: #192 is now release-driving. The six-month plan explicitly permits using mature off-the-shelf components (Kodi/PVR, Plex HTPC, browser runtimes, kiosk/shell facilities, remote middleware, etc.) when they materially accelerate delivery.

    Acceptance bar: the user must perceive one coherent ChannelForge appliance. If a component exposes desktop switching, conflicting navigation, separate setup/maintenance burden, or manual recovery in normal use, it has not met the integration requirement.

  3. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Performance escalation: #193 is now release-driving. The March 2027 product is not acceptable if it is functionally correct but sluggish. Core couch actions must be served from local normalized/indexed state with measurable SER8 latency budgets; provider refresh/enrichment belongs off the foreground path.

  4. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Usability/visual-design escalation: #194 is now release-driving. The March 2027 product is not complete unless normal couch use is zero-instruction for a nontechnical first-time user, including older adults, and clean setup is radically simple. Visual beauty, accessibility, intuitive navigation, and low decision count are release criteria—not post-release polish.

  5. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Execution model update: #195 is now release-driving. The March 2027 target assumes autonomous, parallel, evidence-driven development—not serial manual work. Routine reversible implementation/research/test/docs decisions should proceed without product-owner interruption; escalate only genuine security, architecture, terms, or product-outcome decisions.

  6. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Cost/planning refinement: #195 now requires planning mode before nontrivial implementation and conservative model/token/tool routing. The March 2027 schedule should be achieved through reuse, narrow vertical slices, bounded parallelism, focused validation during iteration, and higher-cost reasoning only where difficulty/risk warrants it—not by maximizing agent/model usage.

  7. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    DVR/timeshift scope update: #68 is now release-driving. The March 2027 product definition includes recording plus live pause/rewind. The plan should prove an actively maintained off-the-shelf backend first (Dispatcharr is the initial candidate), keep it behind a replaceable adapter/orchestration boundary, and defer native DVR mechanics until after the usable product unless the proof demonstrates that no existing backend can meet the seamless couch requirements.

  8. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    TRUE_PLANNING_V1 — execution authority

    Planning anchor: 2026-09-27.

    This plan supersedes ad-hoc sequencing for the six-month living-room product. It does not supersede security, immutable acceptance, exact-head validation, or existing accepted ADRs unless explicitly amended.

    1. Verified starting state

    2. Primary planning decision — NO REWRITE

    Do not rebuild ChannelForge around the new vision.

    Reuse the current engine as the authority for:

    • source acquisition;
    • normalization;
    • evidence/provenance;
    • accepted state;
    • immutable publication;
    • refresh/recovery;
    • configuration.

    Add the new living-room product through bounded contracts:

    • canonical guide/content/event model;
    • provider capability/account adapters;
    • availability/offering model;
    • launch/orchestration model;
    • recording/timeshift capability model;
    • read-optimized guide API;
    • 10-foot client shell.

    3. Backend/client boundary

    ChannelForge remains one backend authority with multiple projections/clients.

    IPTV/XMLTV/XC + connected services + reference schedules
                             |
                             v
                  source/provider adapters
                             |
                             v
                neutral evidence observations
                             |
                             v
                   CANONICAL ONE GUIDE
             content / programme / event / channel
             category / availability / offering
             launch target / recording capability
                             |
              +--------------+---------------+
              |                              |
              v                              v
       10-foot ChannelForge UI         output projections
       SER8 reference client           Kodi/Plex/M3U/XMLTV
              |
              v
     playback / DVR / provider targets
    

    Kodi, Dispatcharr, Plex HTPC, browser runtimes, etc. may sit underneath but never become the canonical ChannelForge state authority.

    4. Platform strategy — narrow proof, not broad bakeoff

    Provisional first proof platform: Windows 11 on the SER8.

    Reason:

    • the core commercial providers have stronger explicit PC/browser support on Windows than Linux;
    • Netflix can reach 4K/HDR on qualifying Windows 11 hardware while Linux support is not guaranteed and is capped lower;
    • DIRECTV documents Windows PC browser playback;
    • Disney+/ESPN document Windows support;
    • current ChannelForge portable packaging already runs on Windows.

    This is not a permanent architectural lock-in.

    Platform proof gate

    Within the first platform spike prove on the actual SER8:

    • HDMI audio/video;
    • HDR/4K capability where applicable;
    • Netflix;
    • DIRECTV Stream;
    • Disney+;
    • ESPN;
    • YouTube;
    • Plex/Plex Live TV;
    • Harmony input path;
    • full-screen/kiosk shell;
    • global Home/Back recovery;
    • sleep/wake;
    • browser session persistence;
    • no routine desktop exposure.

    Only investigate Linux deeply if Windows fails a material requirement or creates unacceptable seams. This avoids an expensive OS bakeoff with low expected value.

    5. DVR/timeshift strategy

    #68 is now release-driving.

    First proof candidate: Dispatcharr

    Dispatcharr is the first reuse candidate because current evidence shows:

    • active releases and development;
    • built-in DVR;
    • recurring/series recording capability;
    • in-progress recording playback with pause/scrub;
    • XC catch-up/timeshift support;
    • active DVR PR work.

    Critical proof requirement

    Do not assume that in-progress-recording scrubbing equals universal live timeshift.

    The proof must demonstrate:

    1. tune a supported live channel;
    2. press Pause immediately;
    3. resume;
    4. rewind within the rolling buffer;
    5. seek forward;
    6. Go Live;
    7. record from the ChannelForge guide;
    8. play the recording;
    9. do all of this without opening the backend admin UI.

    If Dispatcharr cannot provide true instant live pause/rewind cleanly, evaluate one additional maintained PVR/DVR backend. Do not run a broad bakeoff.

    Long-term native ChannelForge DVR remains optional post-product work. The integration boundary must make backend replacement possible.

    6. Immediate sequencing

    Gate 0 — finish the work already in flight

    Owner: current #182 workstream
    Before new implementation branches

    1. Run the exact-head owner smoke required by PR Add Issue 175 multi-source owner smoke workflow #182.
    2. If pass:
    3. If fail:
    4. Do not fold Universal Live Guide — one normalized timeline across linear TV, live streaming, sports, and scheduled events #186-Autonomous Delivery System — smarter-not-harder parallel execution for the six-month product #195 into Add Issue 175 multi-source owner smoke workflow #182.

    This avoids abandoning nearly complete Alpha.1 work and avoids contaminating the new architecture with an unclosed source-set branch.

    7. First three new product slices

    These are the first implementation slices after Gate 0. They are intentionally small and vertical.

    Slice 1 — One Guide canonical read model

    Primary issues: #186, #191, #193
    No provider credentials yet. No playback mutation yet.

    Deliver:

    • minimal canonical read contracts for:
      • Content/Programme;
      • Event;
      • Channel;
      • Category;
      • Offering;
      • Availability;
      • LaunchTarget descriptor;
      • Recording/Timeshift capability descriptor;
    • deterministic identity rules;
    • provenance/freshness/confidence references;
    • normalized category taxonomy;
    • read-optimized local snapshot/index;
    • read-only API endpoints sufficient for:
      • Live Now;
      • Starting Soon;
      • Wrestling;
      • Football;
      • Baseball;
      • Soccer;
      • Movies;
      • News;
      • item details;
    • fixture-backed data from existing M3U/XMLTV/evidence contracts;
    • performance instrumentation against Appliance Performance Gate — instant-feeling guide, navigation, search, and launch on SER8 #193 budgets.

    Do not add a second accepted-state authority.
    Do not make XMLTV the internal canonical model.

    Exit proof

    A test client can query a deterministic local guide, open category views instantly, and see one canonical event with multiple fixture offerings.

    Slice 2 — SER8 10-foot shell + platform/composition proof

    Primary issues: #188, #192, #193, #194
    Parallel with late Slice 1 once the read API shape is stable.

    Deliver:

    • actual SER8 platform proof;
    • provisional Windows 11 decision accepted or rejected by evidence;
    • ChannelForge full-screen 10-foot shell;
    • D-pad / OK / Back / Home contract;
    • category tile home;
    • Live Now and Wrestling as first polished category views;
    • remote focus and large-type visual system;
    • global Home recovery;
    • hidden admin/maintenance path;
    • first performance measurements;
    • no keyboard/mouse for normal fixture-backed browsing.

    Use the existing React/Vite work where it saves time. Do not force the existing desktop/workbench layout into the TV surface if it harms the 10-foot UX.

    Exit proof

    An untrained tester can use Harmony to open Wrestling, inspect an event, return Home, and navigate Live Now without coaching.

    Slice 3 — First real integrated couch vertical

    Primary issues: #189, #187, #67, #70, #68
    Prove integration, not provider breadth.

    Use the smallest provider set that proves all architecture:

    • existing IPTV/XMLTV as baseline;
    • Plex/Plex Live TV as first rich connected-service adapter;
    • one commercial streaming launch target;
    • Dispatcharr DVR/timeshift proof.

    Deliver:

    • minimum secure account/connection abstraction;
    • Plex connection and capability discovery;
    • one streaming-provider launch integration;
    • actual Offering/Availability population;
    • best-source resolution;
    • OK -> launch;
    • Info -> alternates;
    • deterministic return Home;
    • Record action;
    • pause/rewind proof;
    • Recordings view;
    • no backend/admin UI in normal successful flow.

    Exit proof

    From ChannelForge on the SER8:

    1. open a real live item;
    2. press OK;
    3. watch via the chosen target;
    4. Home returns to ChannelForge;
    5. choose a recordable live item;
    6. Record;
    7. pause/rewind live TV;
    8. play the recording;
    9. no keyboard/mouse or manual secondary search.

    8. Parallel work lanes after Slice 1 contracts stabilize

    Use bounded parallelism.

    Lane A — Guide Intelligence

    #186, #191, #28/#121

    • canonical events;
    • guide quality;
    • classification;
    • wrestling/sports schedules;
    • deduplication.

    Lane B — Provider Connections

    #189, #187

    • secure connection abstraction;
    • Plex;
    • commercial service capability adapters;
    • entitlement/availability evidence.

    Lane C — Living-Room Client

    #188, #194

    • SER8 shell;
    • Harmony;
    • visual design;
    • zero-instruction flows.

    Lane D — Playback / Composition / DVR

    #67, #68, #192

    • deep links;
    • browser/app launch;
    • Dispatcharr;
    • Kodi/Plex projection where useful;
    • launch/return recovery.

    Lane E — Performance / Reliability

    #193, #35, #36

    • indexes/materialized views;
    • refresh isolation;
    • startup/resume;
    • performance regression gates.

    No lane may independently redefine canonical identities or accepted-state semantics.

    9. Component adoption gate

    Before adopting an off-the-shelf component, verify:

    • active development;
    • recent meaningful releases/commits;
    • responsive issue/PR activity;
    • security maintenance;
    • compatible license;
    • stable automation/API surface;
    • SER8/platform compatibility;
    • remote/kiosk usability;
    • measurable performance;
    • seam-hiding feasibility;
    • replaceable adapter boundary.

    Reuse now, replace later if needed.

    10. Guide-quality priority

    When schedule pressure appears:

    1. preserve correctness/security/recovery;
    2. preserve guide quality;
    3. preserve couch UX/performance;
    4. reduce provider breadth;
    5. defer secondary features.

    Do not ship a broad but unreliable guide.

    11. Cost-control execution policy

    Every nontrivial slice begins in planning mode.

    Default to:

    • narrow repository reads;
    • existing verified evidence;
    • cheapest capable model/effort;
    • focused tests during iteration;
    • full gates only at defined boundaries;
    • no duplicate parallel investigations;
    • one additional comparison candidate only when the first candidate fails a material gate.

    Escalate reasoning/model cost only for genuine architecture, security, conflicting evidence, or failed lower-cost paths.

    12. October target

    By 2026-10-31, require:

    The October target is deliberately aggressive because the March 2027 deadline leaves no room for an architecture-only month.

    13. Stop conditions

    Stop and escalate before implementation if:

    14. Definition of planning complete

    Planning V1 is complete when:

    • this plan is accepted as execution authority;
    • Gate 0 is assigned to the existing PR Add Issue 175 multi-source owner smoke workflow #182 stream;
    • Slice 1 is the next new implementation slice;
    • platform and DVR spikes are explicitly bounded;
    • no additional broad architecture research is required before work starts.

    Any later plan change must identify the new evidence that makes this plan wrong or incomplete.

  9. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    TRUE_PLANNING_V1 addendum — distributed deployment

    Product-owner clarification after the initial planning pass:

    Planning consequence:

    • keep the provisional Windows 11 evaluation scoped to the SER8 client because of commercial streaming/DRM compatibility;
    • evaluate Docker/Linux vs Windows service for the backend independently;
    • prefer Docker on an always-on NAS/home server as the first backend proof because it aligns with persistent DVR/guide workloads and reuse-first deployment;
    • keep the API/state model identical across Docker and Windows backend modes.

    The first new product slices remain One Guide -> SER8 shell -> real couch vertical, but Slice 2 now connects to a remote backend across the #196 contract rather than assuming local engine co-residency.

  10. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Planning addendum: #197 is future/medium priority and does not expand the six-month scope. March 2027 requires one excellent certified SER8 client. Current architecture must merely avoid unnecessary lock-in so Apple TV, Roku, Android TV/Shield, and other clients can be added later against the same backend/client contract.

  11. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    TRUE_PLANNING_V1 sequencing correction: Gate 0 (#182) is no longer a global stop condition.

    PR #182 must still pass its required owner/device smoke before merge, but while that narrow gate is pending, independent release-driving work may proceed in parallel where it does not depend on #182's unmerged behavior.

    Immediate allowed parallel work:

    Do not consume unmerged #182 behavior as if it were main. Rebase/reconcile later as needed.

    Project rule: never idle the whole program because one lane is waiting.

  12. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Scope-control refinement: anti-overengineering is now explicit under #195. The six-month plan should always prefer the smallest complete vertical slice, one working provider before broad provider frameworks, one certified SER8 client before multi-platform implementations, and one proven DVR backend before custom DVR work. Future extensibility may shape cheap boundaries but must not justify speculative infrastructure.

  13. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    Planning refinement: #195 now permits selective higher-capability advisor review for genuinely hard architecture/security/debugging decisions. Use one focused advisor first; do not create broad multi-agent review swarms. Advisor use must support the March 2027 target and cost discipline rather than becoming another process layer.

  14. Jumpstile commented on Sep 27, 2026

    @Jumpstile
    OwnerAuthor

    TRUE_PLANNING_V1 refinement: the Intelligence Engine is the product core and canonical source of truth. Provider adapters, XMLTV/M3U, sports schedules, DVR backends, and clients remain evidence/integration/projection layers. #36 may introduce SQLite when the One Guide vertical slice demonstrates the need; prefer SQLite first for simplicity and speed, with PostgreSQL only if measured concurrency/scale proves it necessary. Do not delay vertical slices for speculative database architecture.

  15. Jumpstile commented on Sep 30, 2026

    @Jumpstile
    OwnerAuthor

    2026-09-30 coordination state: PR #199 merged at f20c7f034bb473ef196cddeb9ffaa2399675c227; #198 closed completed; stale screenshot PR #168 closed; expanded taxonomy proceeds under #191; #200 may proceed in parallel in its own lane. Schedule remains AT RISK, so parallel #191/#200 is the current critical-path strategy.

  16. Jumpstile commented on Sep 30, 2026

    @Jumpstile
    OwnerAuthor

    Active lane registry — 2026-09-30

    1. Guide Quality & Category Discovery — high-confidence classification, category hubs, and couch-first What's On views #191 expanded taxonomy: dedicated worktree/branch; protected.
    2. One Guide Slice 2 — read-only Live Now browser view from the versioned guide API #200 Live Now UI: separate active branch with intentional local dirty work; protected.
    3. Worktree/backlog hygiene: separate audit/removal lane; may remove only clean, fully merged/superseded worktrees with no unique work.

    All ChannelForge sessions use C:\Temp\CHANNELFORGE-AUTHORITATIVE-STATE.txt as the current coordination state. No lane may clean, redirect, or overlap another without checking that state first.

  17. Jumpstile commented on Nov 13, 2026

    @Jumpstile
    OwnerAuthor

    Phase 0 update (Nov 13): test baseline on main is 882 passed, 0 failed, 1 skipped. All 77 open issues are mapped with a dependency map and order in docs/planning/PHASE-0-FINDINGS.md (merged, main 8c5985c). 51 issues have a milestone, 26 do not; those 26 get a milestone or are closed once Phase 1 starts. The March 31, 2027 date is still unconfirmed.

    Co-Authored-By: Claude Sonnet 5.5 noreply@anthropic.com
    Claude-Session: https://claude.ai/code/session_01NzHAcnJaQLFSmFX9BoM2UE

  18. Jumpstile commented on Nov 17, 2026

    @Jumpstile
    OwnerAuthor

    Milestone reorder (2026-11-16, approved by the owner). Same issues, new order and names. Nothing was deleted.

    The old Milestone 2 is closed and marked retired. ROADMAP.md is updated in PR #262 with a mapping from the old numbers.

    https://claude.ai/code/session_01NzHAcjThVoUGWWfXrYWsNh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:foundationArchitecture, standards, and engineering foundationpriority:highShould be next; significant impacttype:featureA wholly new capability

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions