Appendix
The commands, and what they printed.
Every number on the homepage is the output of a command rather than an estimate. This page names each command, where it was run, and the commit it was run at, and links the unedited output committed beside this page.
It is not proof. A reader can see what was printed, but for the private repositories they cannot re-run it themselves — so this page is a step above a bare assertion and a step below something checkable. Each row says which.
The build that fails on purpose is the most useful row here. A release build refusing when the signing key is absent is the safeguard working; a green build there would mean it had regressed.
private repository
220 Flutter tests — One Frame
- Command
flutter test- Where
- thun-viet/one-frame @ 290a9d8719ea
- When
- 2026-08-29
- Printed
+220: All tests passed!- Full output
- data/runs/one-frame-tests.txt
- Note
- Run in a clean worktree of main.
private repository
638 TypeScript tests — ThunViet V2
- Command
pnpm test- Where
- thun-viet/basic-system-v2 @ fa5081a93439
- When
- 2026-08-29
- Printed
# pass 638- Full output
- data/runs/bsv2.txt
- Note
- node --test. Excludes the 53 Playwright end-to-end specs and the Firestore rules lane, which need a browser and an emulator.
private repository
14 contract operations — ThunViet V2
- Command
count the operations in services/api/openapi/openapi.json- Where
- thun-viet/basic-system-v2 @ fa5081a93439
- When
- 2026-08-29
- Printed
operations: 14- Full output
- data/runs/contract.txt
- Note
- 11 paths, 14 operations, spec version v2-contract-1. Every operation is listed in the output.
private repository
the release build refuses without a signing key — One Frame
- Command
flutter build apk --release- Where
- thun-viet/one-frame @ 290a9d8719ea
- When
- 2026-08-29
- Printed
Release build refused: android/key.properties was not found.- Full output
- data/runs/signing-refusal.txt
- Note
- Run in a clean worktree of main, where android/key.properties is absent because it is gitignored. The build fails on purpose: BUILD FAILED, exit 1. A green build here would mean signing had regressed to the debug key.
local repository, not published
46 tests — Slack wake bridge
- Command
npm test- Where
- claude-slack-bridge @ ff52a7ee24ac
- When
- 2026-08-29
- Printed
# pass 46- Full output
- data/runs/bridge.txt
- Note
- Not published anywhere; this repository exists only on the author's machine.
public repository
79 tests run of 80 declared — First Week
- Command
flutter test --exclude-tags live- Where
- huypkc/first-week @ 3cba67474bcb
- When
- 2026-08-29
- Printed
+79: All tests passed!- Full output
- data/runs/first-week.txt
- Note
- 80 tests are declared; one is tagged live and hits a real endpoint, so the offline run is 79. This repository is public — the same command reproduces this output for anyone.
What this page cannot show.
Four of the six runs are from repositories that are not public. The output is real and committed, but a reader is trusting that it came from the command named above it. That is a genuine limit, and no amount of formatting removes it.
Source access on request — read access to
thun-viet/one-frame and thun-viet/basic-system-v2 can be
granted for a review or an interview. First
Week is public already: clone it and the command reproduces.
What is not claimed anywhere: no Play Store listing, no store release, no production users, no uptime figure, no iOS build, no TestFlight.