The ask
Round 1 of the harness bake-off. Build a Featured Projects page that introduces three of my projects to someone who has never met me, using only facts already on the site and the active theme’s blocks and presets. The entry is a child page of the Round 1 page. You also asked me to retitle the existing ChatGPT entry so the three entries are distinct.
What changed
- Published Featured Projects by OpenCode, my Round 1 entry, as a child of the Round 1 page with the slug you asked for.
- Covered the three required projects in one consistent structure: the American Film Market IT operation, AI tooling for the MSP team, and this AI-managed WordPress site.
- Gave each project a short context, a “What I did” list, a “Tools and technologies” list and a “Why it matters” line, plus one link to where that work lives on the site.
- Used core blocks only (paragraph, buttons, columns, image, list, group) with the theme’s preset colors, font sizes, spacing and border radius. No custom CSS, no new plugins, no theme or template changes.
- Reused three images already in the media library (theater seats, fiber optic strands, server room) and gave each descriptive alt text.
- Jump-link buttons at the top, one H1 from the page title, an H2 per project and H3s for the sub-sections.
- On your instruction, retitled the existing ChatGPT entry from “Featured Projects” to “Featured Projects by ChatGPT” so the entries are distinguishable.
How
SSH to openclaw01 with WP-CLI through ops/wp.sh, and HARNESS=opencode on every command. Baseline snapshot at run start, a fresh snapshot before each change, then verify and commit with ops/sync.sh. I built the page markup in a file and created it with wp post create, read it back with wp post get, and confirmed HTTP 200. I checked the rendered page in the in-app browser: one H1, headings in order, three images with alt text, and working jump links. I checked the phone layout by loading the page in a 390 pixel iframe (its own viewport): the columns stack and there is no horizontal overflow. Lighthouse reported accessibility 100 and best practices 100.
What worked, what didn’t
- Worked: every claim traces to the Home, About, Experience, AI & Automation and Skills pages, the README or an existing Lab Note, so nothing was invented. Core blocks and theme presets gave a clean two-column layout that stacks on phones without custom CSS.
- Mistake and fix: I first created the page without
--post_type=page, so it landed as a post and returned 404. I switched it to a page withwp post update 95 --post_type=pagebefore committing; the committed state is a published page. - Naming note: you asked for the slug opencode_deepseekv41. The scoring engine matches each entry by page slug equal to the harness name, so with this slug it will report the entry as not live and out of scope even though the page is live. The only site files my run changed are my entry export, the generated index and the database export. HARNESS stays opencode because ops/sync.sh only accepts the fixed harness names.
- Cross-lane flag: retitling the ChatGPT entry edits another contestant’s page, which docs/BAKEOFF.md section 4 normally reserves. I did it only because you asked directly, and I am noting it here so it is not mistaken for an unauthorized edit.
- Limit: the browser tool has no device emulation, so the phone check used a 390 pixel iframe and computed column widths rather than a real phone.
- I did not add the page to any menu, did not change any other page, and uploaded no new images. No rollback was needed.
Change record
| Harness | opencode |
| Date | 2026-10-09 17:41 |
| Latest snapshot | opencode-labnote.html |
| Undo this session | ops/rollback.sh --git 8e3d668 |
Commits