Skip to content

docs(evidence): ship-verify origin/main past 2e042258 so merged PRs #56 and #70 go live #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nish3451 merged 2 commits into from
Aug 11, 2026
Merged

docs(evidence): ship-verify origin/main past 2e042258 so merged PRs #56 and #70 go live #104

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3ce27d5
docs(evidence): ship-verify origin/main past 2e042258 so merged PRs #…
nish3451 Aug 11, 2026
2282d90
Merge branch 'main' into docs/evidence/ship-past-2e042258-2026-08-11
nish3451 Aug 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions docs/evidence/canonical-urls-2026-08-09.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,3 +163,48 @@ Finding 6631c0ab0454 ("Missing canonical URL on home") remains closed on the
code side (PR #29), in CI (`npm run check` guard), and against the deployed
site; this lane (2026-08-11) re-confirmed all three against current main and
found nothing further to change on the finding's page.

### Ship verification, "origin/main past 2e042258 so merged PRs #56 and #70 go live" (added 2026-08-11)

This section closes the deploy-lag item that tracked shipping main past
2e042258 so the merged PR #56 (clean `/audit` canonical/og:url/JSON-LD) and
PR #70 (homepage footer attribution) reach production. The deployment-lag
note above (point 3, recorded earlier on 2026-08-11) is hereby resolved.
Both halves of the item are verified true on this head (e6f42c1, current
origin/main):
Comment on lines +173 to +174

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Distinguish the deployed SHA from the current main head

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. Main is 25 commits past 2e042258 and both named PRs are in that history:
`git log --oneline origin/main --not 2e042258` shows 25 commits, including
`1cc7a4e` "point appraisal-page canonicals and JSON-LD @ids at the clean
/audit URL (#56)" and `f9f0b0f` "link Nish's daily reads from the homepage
footer (#70)" — plus every later public-facing merge (#86 footer tap
target, #96 tablet form, #100 retired-hosts truth, #99 docs).

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
Comment on lines +183 to +185

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the malformed live-comparison command

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 👍 / 👎.

differences on every page. The live audit page serves the clean
`https://tinystudio.io/audit` canonical and og:url, JSON-LD WebPage
`@id`/`url` `https://tinystudio.io/audit#webpage`/`https://tinystudio.io/audit`,
and `curl -I https://tinystudio.io/audit` returns HTTP 200 with no
`Location` header (no 307); the live home page head contains the
`Nish's daily reads · inish.in` footer line from #70.

3. Ship mechanism and release state: the armed fleet-release pipeline
(policy "on") shipped this head at 2026-08-11T10:49:53 IST from a clean
detached worktree of the exact sha, accepted against the live URL
("live HTTP 200, marker ok"), and `release-state-tinystudio-io.json` now
pins `e6f42c1`, strictly past 2e042258. The round also carried the two
commits that had landed after the previous 08:38 deploy of 872fd23 — #100
(app/api 410 messages now name The Website Appraisal, verified live on
both hosts) and #99 (docs).

4. Source and CI on this head: `npm run check` passes ("TinyStudio.io checks
passed"; the canonical guard enforces exactly one link per page), the full
`npm test` suite passes (headings 6/6, sitemap 7/7, worker 55/55, ui 16/16,
contract 8/8), and GitHub Actions `verify` and `Gitleaks` both report
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

@coderabbitai coderabbitai Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 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.

Suggested change
#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

on this item remains to ship.
Loading