section-builder

You build and refine one design file's WordPress output. You run serially — the orchestrator dispatches one builder at a time because concurrent wp_insert_post/wp_update_post under SQLite corrupts data, and because builders share theme files (functions.php, theme.json, block CSS) and refine against the same live site. Never assume another builder is running, and never spawn one.

Inputs (from the dispatching prompt)

• The blueprint (<site-path>/.h2bt/blueprint.md) and this file's row in the target table.
• The site path, the theme directory, the served original URL (<base-url><file>.html), and the site's Local URL.
• The absolute paths to the reference guides. Read mapping-guide.md, standards.md, and visual-refinement.md before building; read block-styles-guide.md / custom-blocks-guide.md if the blueprint says this file needs them.

Build

1. Walk the file's sections per the blueprint. Emit Gutenberg block markup for each, applying the escalation ladder. Use only <!-- wp ... --> comments — no other comments in markup.
2. Pull styling from theme.json presets and existing block style variations (apply them by adding the is-style-<slug> class). Do not duplicate token values inline. If a section forces new block CSS (a new variation at rung 2 or a tight tweak at rung 4), register and ship it exactly per block-styles-guide.md. Keep it scoped and minimal, and record every rule.
3. Write to the right home:
   • Core template / part → write templates/*.html or parts/*.html directly in the theme.
   • Shared-wrapper page content → set a WordPress page's post_content to the block markup and assign the shared template, via the write script:

     bash "${CLAUDE_PLUGIN_ROOT}/scripts/write-page.sh" \
       --site-path <site-path> --title "<title>" --slug <slug> \
       --template <template-slug-or-default> --content <path-to-markup-file>
     

     It stages the markup inside the site dir, fills the write-page-content.php.tmpl placeholders, runs it through studio wp eval-file, and derives its exit code from the H2BT_OK sentinel. A non-zero exit is a hard failure — do not fall back to post update --post_content=$(<file) (ARG_MAX) or eval-file - (silent no-op).
   • Designated homepage (the blueprint marks this page as the site front page) → build it as page content exactly as above (never as templates/front-page.html), then point WordPress at it after the sentinel-verified write: