Skip to content

docs: align Week 2 with Xcode GPU profiling - #166

Draft
skyzh wants to merge 4 commits into
skyzh/week2-human-ownershipfrom
skyzh/week2-gpudebug-evidence
Draft

docs: align Week 2 with Xcode GPU profiling#166
skyzh wants to merge 4 commits into
skyzh/week2-human-ownershipfrom
skyzh/week2-gpudebug-evidence

Conversation

@skyzh

@skyzh skyzh commented Jul 31, 2026

Copy link
Copy Markdown
Owner

This is stacked on #160.

Week 2 previously treated gpudebug as an Xcode beta tool on macOS 26. It is a macOS 27 operating-system tool, so the macOS 26 workflow now uses Xcode's graphical Metal debugger and reserves /usr/bin/gpudebug for the optional macOS 27 agent workflow.

This adds representative capture workloads for the Week 2 kernel families, defines one six-view Xcode capture contract, and makes every chapter handoff follow matched end-to-end and operator evidence. It also corrects the Day 5 dispatch workload, expands the Day 6/7 projection controls, and checks in the matched short-context benchmark result.

The complete Day 2–7 screenshot set still requires a GUI capture session. Partial or malformed images are deliberately not linked or published by the book.

Headless validation passes: mdBook and sitemap checks, Ruff formatting and lint, Python compilation, JSON parsing, and diff checks. Before the GUI session ended, the Week 2 reference suite passed 46 tests with 3 skips and the benchmark tests passed all 15 tests. GitHub's book-build and reference-solution checks pass on the synchronized stack.

AI-assisted: Codex.

@skyzh skyzh changed the title docs: make Week 2 GPU profiling agent-readable docs: align Week 2 with Xcode GPU profiling Jul 31, 2026
skyzh added 2 commits July 31, 2026 01:15
Assisted-by: Codex
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.

1 participant