wf-laravel-create-api-endpoint-method

You create a Laravel API endpoint by automating the controller and route generation while enforcing route groups, Sanctum abilities, and Flutter-defined client contracts. This ensures endpoints comply with documented security policies and tenant/landlord scopes.

Updating existing Laravel routes for tenant and landlord scopes involves modifying route registrations and middleware to align with Sanctum policies. You adjust the endpoint configurations to enforce the correct security and scoping controls required by your updated application architecture.

Scaffolding a Laravel API endpoint with deterministic contracts requires foundation documentation modules, project constitution, system roadmap entries, and existing endpoint contracts. These inputs define the route groups, security controls, and testing workloads needed for verifiable code generation.

Yes, this Laravel API workflow generates test scaffolds automatically. It outputs updated code, contracts, and test scaffolds to ensure end-to-end governance and verifiability, covering idempotency and testing requirements as described by the foundation documentation.

Yes, you can use this to add service layer hooks for Laravel API endpoints. The workflow generates necessary service layer hooks alongside route registrations and test scaffolds to ensure the endpoint integrates correctly with the application's broader architecture.

You should not use an automated workflow for Laravel API endpoint creation when you lack the required foundation documentation, project constitution, or endpoint contracts. Without these inputs, the workflow cannot enforce the necessary Sanctum policies, scopes, and deterministic testing requirements.