Repository navigation
docs: the deliverable checklist now matches what is actually live - #71
Merged
Merged
Conversation
Three boxes in the README were still unticked and one line was stale, which made the repo understate what exists — the worst direction to be wrong in for a submission a reviewer reads before the report. Ticked, each with the link that proves it: the dashboard is public at app.sterish.xyz and the landing has its own deployment at sterish.xyz, the demo video exists at sterish.xyz/demo.mp4, and the nine flow screenshots are in docs/evidence/demo/screenshots. Corrected while there: the API row named the old jameshub.fun hostname rather than the canonical api.sterish.xyz, and the report-hash claim still said 25 reports verified on 17 September. It is 36 on 28 September, and now reproducible from a clean clone since the missing eleven were committed. The adoption pack pointed outreach at app.sterish.xyz/landing, which became a 404 today, and quoted a registry count from two weeks ago. Both replaced with what production answered this morning: 35 shown of 43 on chain. The rehearsal finding that asked for the apex mapping gets a dated correction rather than an edit. It was right when written, the mapping now exists, and the URL it recorded is the one that died — worth stating in the same place someone would read the original.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #70. The README's Instawards checklist still had three unticked boxes for things that now exist, so the repo understated the work — the worst direction to be wrong in for a page a reviewer reads before the report.
Ticked, with the link that proves each one
app.sterish.xyzsince 24 Sep, plus the landing's own deployment atsterish.xyzsterish.xyz/demo.mp4, 2 min 54 s, 7 of 7 transactions re-checked on Horizondocs/evidence/demo/screenshotsCorrected while there
api-sterish.jameshub.fun; the canonical host has beenapi.sterish.xyzsince STE-54.docs/adoption/README.mdpointed outreach atapp.sterish.xyz/landing, which became a 404 today, and quoted a registry count from two weeks ago. Both replaced with what production answered this morning: 35 shown of 43 on chain, test namespaces hidden and counted.One correction rather than an edit
docs/rehearsal/FINDINGS.mdrecorded that the apex 404'd while the landing lived at a path, and argued carefully against the easy wrong sentence. That finding was right when written and the mapping it asked for now exists — so it gets a dated correction underneath, in the same place someone would read the original, noting that the URL it recorded is the one that died.cc @axel @fable @Nabil-Aufa