stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Capture unfiled work from a cold offline mobile launch #301

New Issue
Closed
opened 2026-08-08 12:29:17 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-08 12:29:17 +00:00
Member
Copy Link

User problem

A cold-launched installed dashboard can render its offline shell and expose the mobile New action, but issue capture is disabled because the minimized offline snapshot intentionally contains no repository catalog. Operators cannot record work during a tunnel, flight, or Gitea outage even though offline capture is advertised.

Evidence

  • frontend/dashboard.js populates repositories only from live context and rejects repository-less submission.
  • frontend/offline-work.js intentionally omits private repository catalogs.
  • frontend/issue-outbox.js correctly requires repository and confirmed account identity, so unfiled notes need a separate durable draft stage.
  • Historical issues #159, #211, #226, #228, #232, and #250 provide the composer, draft inbox, offline shell/snapshot, and delivery outbox but do not support cold-offline capture.

Acceptance

  • Offline New permits title/body capture without a repository and makes no network/outbox mutation.
  • Up to 20 distinct Needs filing captures survive reload and appear in Drafts.
  • Reconnecting under the same confirmed account lets an operator resume, choose a live repository, and use the existing durable issue delivery flow.
  • A different account cannot file the capture; only copy/discard is available.
  • Mobile controls are at least 44px, fit at 320px, and expose status through existing live regions.
  • Focused behavioral tests and the full suite pass.
## User problem A cold-launched installed dashboard can render its offline shell and expose the mobile New action, but issue capture is disabled because the minimized offline snapshot intentionally contains no repository catalog. Operators cannot record work during a tunnel, flight, or Gitea outage even though offline capture is advertised. ## Evidence - `frontend/dashboard.js` populates repositories only from live context and rejects repository-less submission. - `frontend/offline-work.js` intentionally omits private repository catalogs. - `frontend/issue-outbox.js` correctly requires repository and confirmed account identity, so unfiled notes need a separate durable draft stage. - Historical issues #159, #211, #226, #228, #232, and #250 provide the composer, draft inbox, offline shell/snapshot, and delivery outbox but do not support cold-offline capture. ## Acceptance - Offline New permits title/body capture without a repository and makes no network/outbox mutation. - Up to 20 distinct Needs filing captures survive reload and appear in Drafts. - Reconnecting under the same confirmed account lets an operator resume, choose a live repository, and use the existing durable issue delivery flow. - A different account cannot file the capture; only copy/discard is available. - Mobile controls are at least 44px, fit at 320px, and expose status through existing live regions. - Focused behavioral tests and the full suite pass.
timmy was assigned by rockachopa 2026-08-08 12:29:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#301
No description provided.
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?