Orientation for an AI agent working ON the magento-bricklayer source — how the codebase is laid out, how tools/prompts/resources are registered and auto-discovered, how to add or change one, the QA gates, and the design rule every change is judged against. This is for modifying Bricklayer itself, not for using it against a Magento store (that is the README + wiki).
Build and review Hyva Checkout Evaluation API results, frontend validators, forms, navigation tasks, messages, and frontend payment hooks while preserving the primary checkout flow.
Configure Hyva Checkout definitions, steps, conditions, layout handles, component placement, payment and shipping blocks, and Place Order Service DI. Use when editing hyva_checkout.xml or checkout layout XML, adding or moving components, or wiring payment and shipping integrations.
Build and review Hyva Checkout Magewire components with version-correct lifecycle, events, Evaluation API participation, layout independence, and safe quote state handling for Magewire V1 and V3 checkout lines.
Design, build, migrate, and review Hyva Checkout integrations in Magento 2. Use for checkout architecture, primary navigation, Evaluation API gates, Place Order Services, frontend payment methods, payment and shipping integrations, layout-independent components, Magewire version selection, and checkout extension decisions.
Extend and debug Magewire 3 internals in Magento 2. Use for runtime boot modes, Mechanisms, Features, Component Hooks, resolvers, structured layout arguments, snapshots, synthesizers, request flow, observer bridges, and deciding where framework-level behavior belongs.
Migrate Magewire V1 components onto Magewire 3 using the per-component backwards-compatibility layer. Use for activation precedence, memo.bc.enabled, PHP and JavaScript shims, Hyva Checkout defaults, V1-to-V3 API mapping, phased opt-out, performance, troubleshooting, and disabling the feature site-wide.
Review and harden Magewire 3 application code in Magento 2. Use for component boundaries, public state, lifecycle, layout XML, templates, security, authorization, events, dependency injection, serialization, performance, testing, naming, and code-review checklists.