Issues filed, fixed and verified on production for the Pubky shop and Pubchi, per release, with progress week by week. The evidence page under "P2P e-commerce is real now": it updates itself every hour.
Pubky app branding, taken from pubky.app's own theme: Inter Tight, dark only, page #05050a,
card #1d1d20, text #eeeef6, muted #89898f, border #303034, brand lime #c8ff03. The
chart uses the emphasis form: closed issues in brand lime, filed issues in muted grey. Weekly
change is green (#01ff5d) when more issues were closed than the week before and red
(#ff6467) when fewer, always with an arrow and the numbers, never colour alone. The brand
colours sit outside the usual chart lightness band by design; every contrast and colour-blind
check passes.
Not the vibes portal. vibes.pubky.app says whether each vibe is up. This page says whether
the software is working and getting better.
| What | Where |
|---|---|
| Shop issues | BitcoinErrorLog/pubky-marketplace |
| Pubchi issues | BitcoinErrorLog/pubky-app |
| Shop releases | shop-v* releases on BitcoinErrorLog/pubky-app |
- Filed on / closed on a release: the latest
shop-v*tag published before the issue was opened / closed. Tag time stands in for live time; a tag can go live later than it is cut. - Verified: a tester (
thisispav) comments "verified" on the issue. The build is the lastvX.Y.Znamed in the tester's comments from that comment on, so a later "Build correction" comment wins. Replace with a label once one is agreed. - Fix time: issue opened to issue closed.
- Weeks run Monday to Sunday (ISO, so "38w" matches the team's weekly reports). The current week compares the days so far with the same days of the previous week, so a Wednesday is never judged against a full week.
- Pubchi has no tags, so Pubchi issues appear in the totals and the list, not in the per-release table.
GITHUB_TOKEN=$(gh auth token) node scripts/fetch.mjs
npx serve site # or open site/index.html over any static server
.github/workflows/refresh.yml fetches hourly and publishes site/ to GitHub Pages.
No secrets: the workflow's own GITHUB_TOKEN reads public repos.