docs(evidence): ship-verify origin/main past 2e042258 so merged PRs #56 and #70 go live - #104
Conversation
…and #70 go live The deploy-lag item named 2e04225 as the stuck release sha with merged PR #56 (clean /audit canonical/og:url/JSON-LD) and #70 (homepage footer attribution) unreleased. The armed fleet-release pipeline shipped current main e6f42c1 (2026-08-11T10:49:53 IST); release-state pins e6f42c1, all five public pages diff byte-identical against live, /audit serves the four clean URL strings with 200/no-Location, / serves the #70 footer line, the round also carried #100 (retired app/api hosts now name The Website Appraisal) and #99, and npm test + both required GitHub checks pass on the head.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
📝 WalkthroughWalkthroughThe change adds deployment-verification evidence for live-page parity, clean ChangesDeployment verification
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/evidence/canonical-urls-2026-08-09.md (1)
183-190: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick winMake the live parity evidence reproducible.
The documented
curlcommand does not show the per-route output files or thecmp/diffmapping to eachpublic/*.htmlfile. The no-redirect check usescurl -I, which testsHEADinstead of theGETused for page parity. Record per-routeGETchecks that assert HTTP 200, rejectLocation, and compare each response with its corresponding source file.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/evidence/canonical-urls-2026-08-09.md` around lines 183 - 190, Update the live parity evidence in the documented section to include reproducible per-route GET commands that save each response, assert HTTP 200, reject any Location header, and compare the saved response with its matching public/*.html file using cmp or diff. Replace the curl -I audit check with the same GET-based validation, covering all five routes and their corresponding source files.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/evidence/canonical-urls-2026-08-09.md`:
- Line 209: Update the line beginning with “#70” in the document so the
reference is prefixed with “PR”, preventing Markdown from parsing it as a
heading while preserving the sentence’s meaning.
---
Nitpick comments:
In `@docs/evidence/canonical-urls-2026-08-09.md`:
- Around line 183-190: Update the live parity evidence in the documented section
to include reproducible per-route GET commands that save each response, assert
HTTP 200, reject any Location header, and compare the saved response with its
matching public/*.html file using cmp or diff. Replace the curl -I audit check
with the same GET-based validation, covering all five routes and their
corresponding source files.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 37ff7cab-9c62-4eb3-a3b5-b386b50469d2
📒 Files selected for processing (1)
docs/evidence/canonical-urls-2026-08-09.md
| success on e6f42c1. | ||
|
|
||
| The item is satisfied: origin/main is past 2e042258, the merged PRs #56 and | ||
| #70 are served live (along with everything merged since), and nothing further |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the Markdown lint error.
Line 209 starts with #70. markdownlint-cli2 reports MD018 because this is parsed as an ATX heading without a space. Prefix the reference with PR.
Proposed fix
-#70 are served live (along with everything merged since), and nothing further
+PR `#70` are served live (along with everything merged since), and nothing further📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #70 are served live (along with everything merged since), and nothing further | |
| PR `#70` are served live (along with everything merged since), and nothing further |
🧰 Tools
🪛 markdownlint-cli2 (0.23.2)
[warning] 209-209: No space after hash on atx style heading
(MD018, no-missing-space-atx)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/evidence/canonical-urls-2026-08-09.md` at line 209, Update the line
beginning with “#70” in the document so the reference is prefixed with “PR”,
preventing Markdown from parsing it as a heading while preserving the sentence’s
meaning.
Source: Linters/SAST tools
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3ce27d5528
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 2. The live deployment now matches origin/main byte-for-byte on all five | ||
| public pages: `curl https://tinystudio.io/{/,/audit,/agents,/pricing,/specimen}` | ||
| diffed against the `public/*.html` files on this head shows zero |
There was a problem hiding this comment.
Running the command exactly as recorded expands it into https://tinystudio.io//, https://tinystudio.io//audit, etc., because both the base and every brace alternative contain a slash; it also writes all five response bodies sequentially to stdout, so it cannot directly establish a separate zero-difference result for every public/*.html file. The curl --manual GLOBBING section confirms that brace lists select multiple URLs, while the --output section confirms stdout is the default. Use single-slash URLs and show the per-page output/diff loop so this deployment receipt is reproducible.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2282d90868
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Both halves of the item are verified true on this head (e6f42c1, current | ||
| origin/main): |
There was a problem hiding this comment.
In the reviewed commit, the parent is already 1e78ecf, with e6f42c1 one commit behind it; correspondingly, git rev-list --count 2e042258..64e1c815^ returns 26, not 25. Keeping e6f42c1 as the deployed release is valid, but calling it the current origin/main head makes this deployment receipt internally stale before it is added; record the newer source head/count separately from the deployed SHA.
Useful? React with 👍 / 👎.
1 participant
Closes the deploy-lag item "Ship origin/main past 2e04225 so merged PRs #56 (clean /audit canonical/og:url/JSON-LD) and #70 (homepage footer attribution) go live".
What happened
e6f42c1at 2026-08-11T10:49:53 IST (deploy from a clean detached worktree of the exact sha, accepted against the live URL: "live HTTP 200, marker ok").release-state-tinystudio-io.jsonnow pinse6f42c1, 25 commits past2e042258, including1cc7a4e(fix(public): point appraisal-page canonicals and JSON-LD @ids at the clean /audit URL #56) andf9f0b0f(fix: link Nish's daily reads from the homepage footer #70).Live verification (2026-08-11)
/,/audit,/agents,/pricing,/specimen) diff byte-identical between live andpublic/*.htmlon this head./auditserves canonicalhttps://tinystudio.io/audit,og:urlhttps://tinystudio.io/audit, JSON-LD WebPage@idhttps://tinystudio.io/audit#webpageandurlhttps://tinystudio.io/audit;curl -Ireturns 200 with noLocation(no 307)./head contains theNish's daily reads · inish.infooter line (fix: link Nish's daily reads from the homepage footer #70).Checks
npm run checkpasses ("TinyStudio.io checks passed").npm testpasses: headings 6/6, sitemap 7/7, worker 55/55, ui 16/16, contract 8/8.verifyandGitleaksboth success one6f42c1.Summary by CodeRabbit
/auditURL and the verified deployment revision.