Skip to content

LISTENER-01 — Rename EarlyBird runtime and contracts to Harmonic Beacon Listener #210

Description

@nicoechaniz

Objective

Make Listener the single active product/application namespace before the first public release, without carrying compatibility obligations for discarded experimental variants.

EarlyBirds may remain the historical Git branch/milestone/cohort name. Public product surfaces use Listener / Harmonic Beacon.

Pre-release policy

  • There has been no public release. Experimental clients, routes, cookies and runtime names are not supported contracts.
  • Prefer a direct, coordinated canonical cutover over dual-read/write support windows.
  • Existing experimental browser sessions may be invalidated and asked to sign in again.
  • Remove legacy aliases, fallback readers, bridge-only metrics and transition machinery once the canonical Google/session flow is verified.
  • Do not preserve old behavior merely to make an old experimental binary selectable as rollback. Recovery is stop/kill-switch and roll-forward repair.
  • Applied migration files and physical PostgreSQL early_bird_* tables/indexes remain unchanged because rewriting applied history is destructive. This is database integrity, not runtime compatibility.
  • Durable cross-repository wire IDs remain unchanged only until both repositories can switch atomically; do not run parallel authorities or byte-incompatible contracts.
  • Better Auth remains one authority and one store.
  • No namespace work changes event identity, LiveKit, staff capabilities, payments, Listener media/audio, live.harmonicbeacon.com or Proyección del Mito.

Already delivered

  • /listener and canonical non-media APIs exist.
  • Browser navigation and account-local non-media requests are canonical-first.
  • Listener edge/root and bounded runtime configuration are canonical-first.
  • Listener is isolated and deployed at listen.harmonicbeacon.com.
  • Existing compatibility code fails closed on ambiguous cookie/environment states and leaks no values.
  • Event, LiveKit, staff-capability and audio behavior stayed unchanged.

Remaining direct cutover

  • Inventory every remaining runtime EarlyBird route, cookie, environment key and browser emission; classify applied migrations/tables and cross-repo wire IDs separately.
  • Choose the single canonical Better Auth base path/cookie prefix/callback set and update Google configuration in one coordinated Listener-only release.
  • Remove legacy route aliases, cookie dual-write/read/clear, environment fallbacks and support-window observer code that exists only for transition.
  • Accept that pre-cutover experimental sessions sign in again; verify Google login, refresh, logout and two independent devices after cutover.
  • Coordinate any wire-contract rename byte-exactly with SairaAsua/proyecciones-mito and deploy both sides atomically; otherwise retain the wire ID as an internal historical identifier, not a public compatibility promise.
  • Keep current weekly quota policy, media authorization and approved audio unchanged.
  • Record exact SHAs, migration state, login evidence, kill switch and roll-forward recovery.

Non-goals

  • No migration-history rewrite or physical table rename.
  • No seven-day compatibility observation windows.
  • No dual auth authorities.
  • No event deployment, payment activation or audio/media change.

Parent #198. Cross-repo coordination: SairaAsua/proyecciones-mito#39. Aggregate Listener delivery: draft PR #203.

Activity

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

Metadata

Metadata

Assignees

Labels

cross-repo-integrationRegistration, payment, bot, and Beacon integrationearly-birdsEarlyBirds isolated Listener and 24/7 stream lane

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions