The final review

One pass over the whole artefact before it is public. Course 2's four lenses, plus a fifth that only exists once other people can see the thing.

The five lenses

Leaks. The working tree and the history. Key never outside the proxy — and now CI checks that on every push, so this lens has become mechanical, which is what you wanted.

Cost. The budget split enforced server-side, cache TTLs set, pause-when-hidden working, monitoring not spending quota.

Lies. Every numeric column, and every timestamp. Ages shown, oldest surfaced, stale labelled. A number without a unit or an age is the failure this lens exists for.

Failure. Five panel states, four error kinds, boundaries reporting, health endpoint honest, rollback timed.

Comprehension — the new one. Can a stranger run it, understand it, and know what it does not do? This is the lens that only matters once the artefact is public, and it is the one you cannot check yourself.

Have someone else run it

The single most valuable thirty minutes in this course: give the repository URL to a person and watch them try to run it, saying nothing.

Every question they ask is a README bug. Every place they hesitate is a naming problem. Every thing you want to explain out loud is documentation you have not written. Say nothing until they finish — the instinct to help is exactly what destroys the measurement.

If nobody is available, your assistant reading only the README is a decent substitute, because its lack of context is genuine.

The limitations section is the review's output

By now you have four measured walls: freshness, breadth, history, real-time. Each produced a sentence about what your tool cannot do.

Collect them into the README. That section is the most credible thing in the repository, because anyone can claim a feature and almost nobody documents a boundary. A reader who sees four specific limitations concludes the other claims were written with the same care — which is a reasonable inference and, in your case, a true one.

Then stop

There is always more. At some point the tool is good enough to be public, and shipping it teaches you more than another week of polish.

The five lenses passing is a reasonable definition of good enough. Use it, ship, and let the next round of work come from actually using the thing.

Try it now

Run all five lenses and write the results in REVIEW.md with today's date. Then ship it. The date matters — in six months you will want to know when the artefact was last actually inspected rather than assumed fine.