Sample Page

This is an example page. It’s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:

Hi there! I’m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin’ caught in the rain.)

…or something like this:

The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.

As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!

Contact Page — Unblock Luna Writer and Resume Existing Migration

Act as the BricksGenius migration coordinator.

Current state

The Contact page migration is already audited.

Live page: /contact/
WordPress page ID: 39
Evidence report:
.omo/evidence/contact-stage-a-b/report.md
Flat-topology validator:
12/12 checks passed
No source, WordPress, metadata, or SFTP writes were made
No production email was sent

Confirmed defects:

Mobile icon overlap
Missing breadcrumb
Missing hero marker
Missing honeypot
Missing hidden source field
Source validation gaps

Objective

Restore the required Luna writer profile.
Verify Luna can start successfully.
Resume the Contact migration from the existing evidence report.
Apply the source and live fixes.
Stop after first-pass desktop/mobile QA.

Do not repeat the full audit.

Phase 1 — Repair Luna runtime availability

Inspect:

.codex/config.toml
.codex/agents/luna.toml
.agents/skills/bricks-migration-orchestrator/SKILL.md
working Codex agent profiles
current runtime profile registry
current workspace root
runtime startup logs

Confirm:

Luna profile file exists
runtime ID matches the orchestrator call
model name is valid
profile is registered/discoverable
required fields match a known working profile
a fresh Codex process is used after profile changes

Preserve:

multi_agent_v2 = false
max_depth = 1
flat topology
Luna as bounded writer
report-only agents remain read-only

Do not bypass or weaken the migration guard.

Runtime proof

Run Luna with a harmless bounded task:

Read .omo/evidence/contact-stage-a-b/report.md and return only the six confirmed Contact-page defects. Make no changes.

Proceed only when:

Luna starts
it returns the correct defects
it makes zero writes
it spawns no child agents

If Luna still cannot start, remain on HOLD and return the exact loader error.

Phase 2 — Resume Contact work

Read:

.omo/evidence/contact-stage-a-b/report.md
web/contact/index.html
actual Contact CSS/JS owners
live page 39 content
existing form settings

Do not repeat screenshot discovery already recorded in the evidence report.

Source fixes

Apply only the confirmed defects:

Mobile icon overlap

Correct the actual source structure or CSS owner.

Verify:

icons stay inside their intended wrappers
no overlap at 390px
no fixed positioning or negative-margin workaround
touch targets remain usable

Breadcrumb

Add the approved BricksGenius breadcrumb structure.

Use:

Home
Contact

Requirements:

left aligned
semantic navigation
correct separator behavior
mobile wrapping without isolated separators

Hero marker

Restore the missing approved hero marker/eyebrow detail from the local design system.

Do not redesign the hero.

Honeypot

Add the project’s existing honeypot approach.

Do not introduce a new third-party CAPTCHA service.

Hidden source field

Add a hidden field with value:

Contact page

Use a stable field name that is included in saved submission/email data.

Validation

Confirm:

Name required
Email required
valid email validation
required select fields cannot submit placeholder values
message/brief required only when approved by source
URLs validate correctly when supplied
success/error messages are honest
privacy link works

Do not send a real production email during visual QA.

Phase 3 — Source validation

Run:

local desktop QA at 1280×900
local mobile QA at 390×844
python3 tools/split_assets.py
php -l bricks-child/functions.php only if PHP changed
git diff --check

Verify:

no icon overlap
breadcrumb visible
hero marker visible
honeypot present
source field present
validation works
no console errors
no failed assets
no horizontal overflow
zero new !important

Phase 4 — Live backup

Before live writes, back up page 39:

_bricks_page_content_2
_bricks_page_settings
_bricks_editor_mode
SEOPress metadata
manual schema metadata
form settings/actions
post_modified
rendered HTML/head

Save under:

/var/www/html/wp-content/uploads/bxg-backups/

Return the exact backup path.

Phase 5 — Live implementation

Use Novamira for:

Bricks structure
form fields
hidden field
honeypot
form actions
page metadata

Use SFTP only for regenerated child-theme assets under /site/wp-content.

Patch page 39 only.

Do not rebuild unrelated sections.

Preserve:

page copy
section order
header/footer
SEO ownership
existing approved contact destination

After changes:

clear _transient_bxg_chunks_39_*
bump post_modified
clear relevant Bricks/page cache
reload /contact/

Phase 6 — First-pass QA

Check live at:

1280×900
390×844

Verify:

breadcrumb visible
hero marker visible
mobile icons do not overlap
honeypot exists
hidden source field exists
form validation works
select placeholders cannot submit as values
no production email sent
no console errors
no failed requests
no horizontal overflow
header/footer render once

Do not run prolonged ODiff.

Compact final report

Save detailed evidence to:

.omo/evidence/contact-stage-a-b/final-report.md

Chat response must include only:

Luna runtime repair result
Source files changed
Page 39 backup path
Form/honeypot/source-field result
Live defects fixed
Desktop/mobile QA
Remaining blocker, if any

Final status:

First-pass Contact page complete — user visual QA pending.