maniator / maniator/verticopolis

[Feature]: [P3] Mobile distribution tail: E1d/E1e remainders plus untracked E2c/E2d/E3; resume-or-pause needs owner decision D-3

Open
#385 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Scope widened by the full repository audit (2026-07-21, findings AUD-019/035/036/037; report at _bmad-output/planning-artifacts/reviews/full-repository-audit-2026-07-21/). This issue is now the tracking home for the whole remaining mobile-distribution tail, not just E1d/E1e. Backlog row mobile-e1d-e1e-stream updated to match.

What the audit verified

  • E1a/E1b/E1c: done as claimed (src/platform/ exists, PWA gating on native mode shipped, --mode native works).
  • E1d: not done: no docs/distribution.md, and the public repo has zero git tags, so the PUBLIC_REF "tag" contract has nothing to point at. Consequence: verticopolis-mobile/PUBLIC_REF (f52489e1, 2026-07-07) is 1,099 commits behind main and predates E1a-E1c: a tree built at that pin has no platform seam at all (AUD-019).
  • E1e: diverged without a recorded decision (AUD-036): the /?src=twa marker that the TWA README and story E2a treat as load-bearing has no consumer; the shipped Vercel analytics has no platform dimension, so TWA sessions classify as web with or without the marker. Resolving this folds into the analytics-platform ruling (audit §19, D-1).
  • E2a: done as claimed (mobile PR #2; deliverables match the story).
  • E2b: correctly blocked (no assetlinks.json; production serves 404 as expected pre-E2b).
  • E2c/E2d, E3a-E3d: not started and previously tracked nowhere (AUD-037); the mobile repo's ledger is empty and no workflows exist, while mobile CLAUDE.md's layout section describes them as present (AUD-035, doc true-up rides the first PR of whichever path is chosen).

Blocked on

Owner decision D-3 (audit §19): resume the mobile epic or formally pause it. Until then this issue tracks the tail; no story below E1d should start. First PR on resume: PUBLIC_REF bump + E1d tag + mobile CLAUDE.md truth pass.

Acceptance (for closing this issue)

Either (a) D-3 = pause: epics doc and mobile CLAUDE.md marked paused/planned-vs-present, this issue closes as the record; or (b) D-3 = resume: each remaining story gets its own row/issue per the mirror convention and this issue closes in favor of them.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the audit report at _bmad-output/planning-artifacts/reviews/full-repository-audit-2026-07-21/ and the mobile CLAUDE.md layout section, then review the D-3 owner decision. Work cannot begin until the mobile epic is resumed or paused; on resume, the first PR must address PUBLIC_REF, the E1d tag, and the documentation truth pass. Close this tracker only after the pause or resume acceptance conditions are recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, git, typescript
Domain
documentation, mobile-dev, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.