domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US02-05 — Build the Static Application Shell #12

New Issue
Closed
opened 2026-07-13 13:10:41 +02:00 by domverse · 0 comments
domverse commented 2026-07-13 13:10:41 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US02-05-frontend-shell.md

US02-05 — Build the Static Application Shell

Epic: E02

As a user, I want a fast, navigable application shell so all workflow views share one
consistent interface without server-generated operational HTML.

Acceptance criteria

  • index.html, CSS, and modular JavaScript are separate static files.
  • Shared API client, store, router, error handling, cancellation, and SSE/polling
    adapters are implemented.
  • Navigation routes restore current view and filters after reload.
  • HTML fallback never intercepts /api/v1 requests.

Automated tests

  • JavaScript tests cover API errors, store transitions, routing, and event fallback.
  • Browser tests assert asset loading, deep links, reload, JSON-only APIs, and no
    unexpected console/network errors.

Dependencies

  • US02-04
Source specification: [delivery_backlog/stories/US02-05-frontend-shell.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US02-05-frontend-shell.md) # US02-05 — Build the Static Application Shell Epic: [E02](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E02-unified-workflow-shell.md) As a user, I want a fast, navigable application shell so all workflow views share one consistent interface without server-generated operational HTML. ## Acceptance criteria - `index.html`, CSS, and modular JavaScript are separate static files. - Shared API client, store, router, error handling, cancellation, and SSE/polling adapters are implemented. - Navigation routes restore current view and filters after reload. - HTML fallback never intercepts `/api/v1` requests. ## Automated tests - JavaScript tests cover API errors, store transitions, routing, and event fallback. - Browser tests assert asset loading, deep links, reload, JSON-only APIs, and no unexpected console/network errors. ## Dependencies - US02-04
domverse added this to the E02 — Unified Workflow Shell milestone 2026-07-13 13:10:41 +02:00
domverse added the type/featurearea/frontendpriority/normal labels 2026-07-13 13:10:41 +02:00
domverse added a new dependency 2026-07-13 13:11:18 +02:00
#11 US02-04 — Expose Job APIs and Activity Events
domverse added a new dependency 2026-07-13 13:11:20 +02:00
#14 US02-07 — Automate Phase B End-to-End Acceptance
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:44 +02:00
domverse added the status/backlog label 2026-07-13 13:52:46 +02:00
domverse added status/done and removed status/backlog labels 2026-08-09 20:11:54 +02:00
domverse moved this to Done in Photo Analyzer Delivery on 2026-08-16 11:58:34 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/frontend priority/normal status/done type/feature
Milestone
No items
No Milestone E02 — Unified Workflow Shell
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#13 US02-06 — Deliver Workflow, Safety, Library, Analysis, and Stats Views
domverse/photoanalyzer
#14 US02-07 — Automate Phase B End-to-End Acceptance
domverse/photoanalyzer
Depends on
#11 US02-04 — Expose Job APIs and Activity Events
domverse/photoanalyzer
Reference: domverse/photoanalyzer#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?