trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wire INTEGRATION_SECRET into docker-compose and CI; archive komoot-import

Browse source 
- Add INTEGRATION_SECRET to journal service in docker-compose.yml with
  :? guard so a missing value fails loudly at compose-up time
- Add INTEGRATION_SECRET to E2E test step in ci.yml via GitHub secret
  (unit tests already set their own value in the test file)
- Archive openspec/changes/komoot-import → archive/2026-05-23-komoot-import
- Sync delta specs: new openspec/specs/komoot-import/spec.md,
  updated openspec/specs/route-management/spec.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Ullrich Schäfer 2026-05-23 21:10:08 +02:00
parent 5158298424
commit ae23d31a5f
No known key found for this signature in database
GPG key ID: A32FF691A0F752D9
10 changed files with 397 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
openspec/specs/route-management/spec.md
View file

@ -130,6 +130,17 @@ Any listing that exposes routes beyond the owner's own dashboard SHALL only incl
- **WHEN** a logged-in user views their own routes list at `/routes`
- **THEN** the list includes all of their own routes regardless of visibility
### Requirement: Route creation via import
The system SHALL support creating routes via import from external services, in addition to manual creation and GPX upload.
#### Scenario: Route created from import
- **WHEN** a Komoot tour is imported
- **THEN** a route is created with name, distance, elevation, GPX geometry, and a source field indicating "komoot"
#### Scenario: Route links to activity
- **WHEN** a tour is imported as an activity
- **THEN** the activity is linked to the created route
### Requirement: Synthetic route flag
The Journal SHALL persist a `synthetic` boolean on every route so automated / demo content can be distinguished from user-created content.