[no-ticket] Sync .cursor with suite root

Bring this repo's .cursor/ in line with the suite monorepo root .cursor/
so rules, skills, and autodev artifacts stay consistent across
submodules and sibling repos.

Co-authored-by: Cursor <cursoragent@cursor.com>

.cursor/skills/new-task/SKILL.md

@@ -136,11 +136,9 @@ The `<task_slug>` is a short kebab-case name derived from the feature descriptio
 1. Read the codebase documentation from DOCUMENT_DIR:
    - `architecture.md` — overall structure (the `## Architecture Vision` H2 is user-confirmed intent and must not be violated by the new task without explicit approval)
    - `glossary.md` — project terminology; reuse the user's vocabulary in task names, AC, and component references
-   - `components/` — component specs (one folder per Layer-3 service component)
-   - `modules/` — process-level documentation (Layer-4 WebApi lives in `modules/api_program.md`, not in `components/`; see `module-layout.md` § Documentation Layout — AZ-495)
+   - `components/` — component specs
    - `system-flows.md` — data flows (if exists)
    - `data_model.md` — data model (if exists)
-   - When the task touches WebApi (`SatelliteProvider.Api`), the documentation anchor is `modules/api_program.md` — do NOT reference `components/01_web_api/description.md` or any `components/*/web_api*` path; that folder is intentionally absent per the AZ-495 convention.
 2. If research was performed (Step 3), incorporate findings
 3. Analyze and determine:
    - Which existing components are affected