advanced-delivery-method

# Advanced delivery method Workflow reference selection is optional; choose actual work from identity, capability and evidence. Preserve RequirementSet and ContractGraph traceability through architecture, implementation, tests, interface evidence, and independent review. Every declared workflow node runs once, and every dependency is mandatory. Parallel work is permitted only across a real ready frontier: branches have complete shared input, disjoint mutable ownership, independently reviewable outputs, and no dependency on facts another branch has not produced. Their typed Artifacts are the only handoff into downstream joins. Shared files, generated authorities, integration checks, final review, and delivery converge serially. Investigators remain read-only. The package-owned implementation and interface roles own mutations in their declared scope. Reviewers inspect exact current artifacts and source revisions instead of trusting model summaries. A terminal result requires the selected workflow's positive checks and, for graphical work, real rendered-page interaction and human-inspected screenshots. For a browser responsibility, use already callable tools directly. Discover missing Browser Model Context Protocol (MCP) actions with `capability_search` (for example `queries=["browser click"], kinds=["mcp_tool"]`), copy returned exact refs into `exact_refs`, then invoke the revealed tool using its actual schema. Read `search_window`, availability and next owner before declaring a blocker. Browser Preview captures persisted evidence; it is not an interaction tool. Use the role's actual permission/coordination path for a missing grant or configuration and include the exact failed operation and tool result. An operating-system file error is not a missing user request, and an already supplied Task must not be requested again to repair it.