TEKORI: WordPress output target on Lamoi WaaS
Imported from GitHub issue El-SaMa/tekori#18 by @El-SaMa.
Goal
A brief can produce a Lamoi WordPress site instead of a React site: same intake, same blueprints and brand system, built through the OMA MCP WaaS tools.
Tasks
- Job option
target: 'react' | 'wordpress'(+kind: site | shop); intake asks only when the user's wish is unclear (shop with WooCommerce defaults to WordPress, as the operator decided). - Designer: same DESIGN.md; writes design tokens; picks patterns per blueprint section (section ids map 1:1 to patterns, El-SaMa/lamoi-waas#12). Modes: safe and bold only.
- New role
builder-wp: tools = OMA MCPwaastools (no shell, no files); builds pages as drafts, sets menus, media, SEO, forms; shop setup via W17 ops. - Preview: the draft subsite URL (or staging network) shown in the TEKORI stage;
lookscreenshots that URL. - Publish = connector publish ops; "Deploy" button maps to it; later chat edits use the same tools with snapshots and undo.
- Images: TEKORI's image tool output imported with
media.import. - Costs and learning record like other jobs (target recorded in
job_outcomes). - Safety: TEKORI can never call destructive ops without the user's confirmation in the chat.
Acceptance criteria
- A nano/local mechanics run builds a 5-page site on staging. Paid quality runs only after operator approval.
Depends on
El-SaMa/lamoi-waas#12, El-SaMa/lamoi-waas#16, El-SaMa/lamoi-waas#17; El-SaMa/oma#173.
Plan key W20. Epic: El-SaMa/lamoi-waas#25.