Skip to content

refactor: rename project to Longplay - #53

Merged
Hiepler merged 1 commit into
mainfrom
feature/rename-to-longplay
Aug 20, 2026
Merged

refactor: rename project to Longplay#53
Hiepler merged 1 commit into
mainfrom
feature/rename-to-longplay

Conversation

@Hiepler

@Hiepler Hiepler commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Rename from AI Journey DJ to Longplay across the monorepo:

  • packages: @ai-journey-dj/* -> @longplay/*, root package -> longplay
  • UI: header brand mark, document title, MediaSession and Spotify Connect device name, journey playlist names
  • outgoing HTTP: LRCLIB and Nominatim User-Agent strings
  • badge and issue-template URLs -> github.com/Hiepler/longplay

Rewrite the README around what the engine actually does, adding the drive-story acts, the journey-moment types, the charge-stop leg reset and the streaming-only telemetry signals that were missing, and replacing the two overlapping bullet lists with prose. Candidate scores are described as persisted in SQLite rather than exposed via the API, which is where they actually land.

Replace the production domain in docs/deployment.md and .env.example with the reserved longplay.example.com placeholder, so forks configure their own host.

Document ADMIN_API_TOKEN in the Coolify env list. The Traefik section exempts the Tesla admin routes from basic auth because they authenticate with a bearer token, but the token itself was never listed; it defaults to empty, which makes those routes answer 403 and blocks Tesla onboarding.

The SQLite path (data/ai-journey-dj.db) keeps its name to avoid a data migration with no upside.

What & why

Type of change

  • Bug fix
  • New feature
  • Refactor / internal
  • Docs

How was this verified?

Checklist

  • npm run typecheck passes
  • npm run lint passes
  • npm run test passes
  • npm run build passes
  • Mock mode still runs with no credentials
  • New behavior is covered by tests where it makes sense
  • New env flags are documented in .env.example
  • The deterministic core stays deterministic (LLM only resolves an already-fixed brief)

Rename from AI Journey DJ to Longplay across the monorepo:

- packages: @ai-journey-dj/* -> @longplay/*, root package -> longplay
- UI: header brand mark, document title, MediaSession and Spotify Connect
  device name, journey playlist names
- outgoing HTTP: LRCLIB and Nominatim User-Agent strings
- badge and issue-template URLs -> github.com/Hiepler/longplay

Rewrite the README around what the engine actually does, adding the drive-story
acts, the journey-moment types, the charge-stop leg reset and the streaming-only
telemetry signals that were missing, and replacing the two overlapping bullet
lists with prose. Candidate scores are described as persisted in SQLite rather
than exposed via the API, which is where they actually land.

Replace the production domain in docs/deployment.md and .env.example with the
reserved longplay.example.com placeholder, so forks configure their own host.

Document ADMIN_API_TOKEN in the Coolify env list. The Traefik section exempts
the Tesla admin routes from basic auth because they authenticate with a bearer
token, but the token itself was never listed; it defaults to empty, which makes
those routes answer 403 and blocks Tesla onboarding.

The SQLite path (data/ai-journey-dj.db) keeps its name to avoid a data
migration with no upside.
@Hiepler
Hiepler merged commit 0cee89a into main Aug 20, 2026
1 check passed
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