Skip to content

test: drop the removed entrance-grid assertion from the generated-site suite - #24

Merged
erinepshovel-code merged 1 commit into
mainfrom
claude/textbook-chapters-needed-jd2nht
Jul 31, 2026
Merged

erinepshovel-code merged 1 commit into
mainfrom
claude/textbook-chapters-needed-jd2nht

Conversation

@erinepshovel-code

Copy link
Copy Markdown
Contributor

Completes #23, which merged while this fix was still in flight. tests/generated-site.test.mjs:32 still asserts Return to Awakening in the rendered /home/ page — text that #23 removed — so npm run check currently fails on main, and the next Pages deploy is blocked until this merges (this was the CI failure on #23's PR run).

One-line change: drop the stale assertion, aligning the generated-site suite with the reduced home surface exactly as the site-contract suite already was in #23.

Testing: npm test — 25 passed. The generated-site suite passes in CI's online build; local offline runs of it fail on unrelated sandbox data-fallback artifacts, not this assertion.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E93Rxmrs8bXHtWjD7z94bi


Generated by Claude Code

…e suite

tests/generated-site.test.mjs still asserted 'Return to Awakening' in the
rendered home page after the entrance-card grid was removed; align it with the
reduced home surface, matching the site-contract update.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E93Rxmrs8bXHtWjD7z94bi
@erinepshovel-code
erinepshovel-code merged commit fcabc6e into main Jul 31, 2026
5 checks passed

Copy link
Copy Markdown
Contributor Author

Verification report — 2026-07-31

  • Pages #83 (push) and #84 (scheduled) on aaef8ef each had exactly one failure: generated deployment artifact contains the unified routes expected /Return to Awakening/. The other 25 unit/contract tests and 7 generated-site tests passed; subsequent Pages stages were skipped. No second blocker was present.
  • PR head c848294 changes one line only: it removes that stale assertion. No additional branch fix was needed.
  • PR workflow Fix WebMCP repository-first workflow #62 passed npm run check plus browser/accessibility verification.
  • Independent verification passed: npm run check (25 unit/contract + 8 generated-site tests), 19 Playwright browser/accessibility tests, workflow pin audit, live-source build, and Pages artifact/root/build-identity checks.
  • Final refresh found this PR had already been merged by @erinepshovel-code as fcabc6e at 2026-07-31 03:02:59 UTC. I did not merge or push. Pages #85 then passed build, deploy, Pages identity, and custom-domain identity verification.

hmmm: no unresolved site blocker; the only boundary is that the requested no-merge state had already changed externally before final reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants