docs: address jongio round 4 — add ai_model_quota check, shell→kind, fix IoC regression, update glossary

- provisioning-pipeline.md: add ai_model_quota as second preflight check
- azure-yaml-schema.md: shell→kind in hook example, add infracreate/infradelete hooks
- system-overview.md: fix IoC example regression (MustRegisterTransient→MustRegisterSingleton)
- glossary.md: update preflight description to match implemented checks

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: hemarina

docs/architecture/provisioning-pipeline.md

@@ -26,8 +26,9 @@ For Bicep, azd can generate a fully resolved deployment snapshot using `bicep sn
 Client-side validation that runs after compilation but before deployment:
 
 - **Role assignment permissions** — Checks if the user has required RBAC roles for role assignments in the template
+- **AI model quota** — Validates that sufficient AI model capacity is available in the target region
 
-The preflight framework is pluggable — new checks can be added via `AddCheck()`. Currently only role assignment permissions is implemented; additional checks (e.g., resource conflicts, quota validation) can be added as needed.
+The preflight framework is pluggable — new checks can be added via `AddCheck()`.
 
 **UX behavior:**
 

docs/architecture/system-overview.md

@@ -52,7 +52,9 @@ See [Command Execution Model](command-execution-model.md) for details.
 All services are registered in `cmd/container.go` using the IoC container (`pkg/ioc`). Services are resolved at runtime — never instantiated directly.
 
 ```go
-container.MustRegisterTransient(resolveFn any)
+container.MustRegisterSingleton(func(dep *Dependency) *MyService {
+	return &MyService{dep: dep}
+})
 ```
 
 ### Infrastructure Provisioning

docs/concepts/glossary.md

@@ -48,7 +48,7 @@ A hash-based mechanism that tracks whether the IaC template has changed since th
 
 ### Preflight Checks
 
-Client-side validation that runs after Bicep compilation but before server-side deployment. Checks resource availability, permissions, and potential conflicts to surface issues early.
+Client-side and server-side validation that runs after Bicep compilation but before deployment. Validates role assignment permissions and AI model quotas to surface issues early.
 
 ## Extensions
 

docs/reference/azure-yaml-schema.md

@@ -65,16 +65,16 @@ Hooks run user-defined scripts at lifecycle points:
 ```yaml
 hooks:
   preprovision:
-    shell: sh
+    kind: sh
     run: ./scripts/setup.sh
   postdeploy:
-    shell: sh
+    kind: sh
     run: ./scripts/smoke-test.sh
 ```
 
 Available hook points (each supports `pre` and `post` prefixes):
 
-- **Command hooks (project-level):** `provision`, `deploy`, `down`, `up`, `restore`, `package`, `publish`
+- **Command hooks (project-level):** `provision`, `deploy`, `down`, `up`, `restore`, `package`, `infracreate`, `infradelete`, `publish`
 - **Service lifecycle hooks (service-level):** `restore`, `build`, `package`, `publish`, `deploy`
 
 For example, `preprovision` runs before provisioning, `postdeploy` runs after deployment. Service-level hooks are defined under a service's `hooks` section in `azure.yaml` and apply only to that service.