docs(rules): add 316-zero-trust and fix stale rule references

- Add rules/316-zero-trust.mdc (alwaysApply: true, priority 316)
  with Distinguished-Engineer voice covering identity, network,
  data, workload, AI/agent, and audit under Zero Trust
- Add skills/zero-trust/ playbook (SKILL.md plus 5 references:
  agent-design, mcp-hardening, injection-threat-model, hitl-gates,
  threat-model-template)
- Rename stale rule numbers across 27 files (docs, examples,
  commands, rule See-also sections) after the rules renumbering
- Rewrite mcp/cursor-rules-mcp/src/api/client.ts fileMap and
  listAvailableRules against actual rule filenames and priorities;
  add zero-trust entry under patterns
- Add 015-context-engineering.mdc and 316-zero-trust.mdc to the
  always-apply tables in README and docs/HOW-TO-USE.md
- Fix "Plan/Build/Review" to "Plan/Implement/Review" in README,
  HOW-TO-USE, and .cursorrules-example (matches 010-workflow.mdc)
- Update README Python floor 3.12+ to 3.14+ to match 200-python.mdc
- Register 316-zero-trust.mdc in rules/INDEX.md and README.md

Restores correctness of internal cross-references that broke when
the rules were renumbered, and adds a principles-first Zero Trust
rule intended to always load alongside 310-security.mdc.

Author: d-padmanabhan

.github/CONTRIBUTING.md

@@ -153,7 +153,7 @@ refactor(go): reorganize concurrency section
 ```
 cursor-engineering-rules/
  rules/              # All .mdc rule files
-    050-workflow.mdc
+    010-workflow.mdc
     100-core.mdc
     ...
     INDEX.md       # Rule catalog

README.md

@@ -56,6 +56,7 @@ Comprehensive, battle-tested Cursor IDE rules for professional software engineer
 ### Security & Testing
 
 - **[310-security.mdc](rules/310-security.mdc)** - OWASP Top 10, secret management
+- **[316-zero-trust.mdc](rules/316-zero-trust.mdc)** - Distinguished Engineer - Zero Trust (identity, network, data, workload, AI/agents)
 - **[300-testing.mdc](rules/300-testing.mdc)** - Unit/Integration/E2E testing strategies
 
 ### Patterns & Best Practices
@@ -70,6 +71,7 @@ Comprehensive, battle-tested Cursor IDE rules for professional software engineer
 - **[483-kafka.mdc](rules/483-kafka.mdc)** - Kafka / Confluent (schemas, semantics, DLQ, ops)
 - **[484-teradata.mdc](rules/484-teradata.mdc)** - Teradata SQL and performance patterns
 - **[810-documentation.mdc](rules/810-documentation.mdc)** - Documentation standards
+- **[815-reactflow-diagrams.mdc](rules/815-reactflow-diagrams.mdc)** - Interactive architecture diagrams (@xyflow/react / React Flow); playbook: [skills/reactflow-architecture-diagrams/SKILL.md](skills/reactflow-architecture-diagrams/SKILL.md) (symlink into `.cursor/skills/` in consumer projects)
 - **[820-open-source.mdc](rules/820-open-source.mdc)** - Open source project patterns
 - **[250-cli.mdc](rules/250-cli.mdc)** - CLI application patterns
 - **[110-configuration.mdc](rules/110-configuration.mdc)** - Configuration management
@@ -201,13 +203,15 @@ ln -s /path/to/cursor-engineering-rules/rules .cursor/rules
 
 | Rule | Purpose |
 | --- | --- |
-| `010-workflow.mdc` | Plan/Build/Review workflow |
+| `010-workflow.mdc` | Plan/Implement/Review workflow |
+| `015-context-engineering.mdc` | Prompt packing, retrieval, compaction |
 | `020-agent-audit.mdc` | Agent audit requirements |
 | `100-core.mdc` | Core coding standards |
 | `110-configuration.mdc` | Configuration management |
 | `120-utilities.mdc` | CLI tools |
 | `130-git.mdc` | Git conventions and signed commits |
 | `310-security.mdc` | Security best practices |
+| `316-zero-trust.mdc` | Distinguished Engineer - Zero Trust |
 | `800-markdown.mdc` | Markdown formatting |
 
 Other rules load based on file patterns or explicit request.
@@ -354,7 +358,7 @@ See [rules/INDEX.md](rules/INDEX.md) for complete categorization.
 
 ### Modern Standards
 
-- **Latest versions** (Python 3.12+, Go 1.25+, Node 22+)
+- **Latest versions** (Python 3.14+, Go 1.25+, Node 22+)
 - **Modern patterns** (async/await, generics, type safety)
 - **Current tools** (ripgrep, fd, fzf, just, jq)
 

SETUP_GUIDE.md

@@ -55,4 +55,4 @@ Workspace context files should live at:
 - `tmp/progress.md`
 - `tmp/project-brief.md`
 
-See `rules/050-workflow.mdc` for the workflow and file meanings.
+See `rules/010-workflow.mdc` for the workflow and file meanings.

commands/README.md

@@ -77,11 +77,11 @@ The AI will enter that phase and follow the corresponding workflow guidelines.
 
 Performs a full code review comparing your branch to `main`:
 
-- **6-phase structured review** following `100-core.mdc` and `050-workflow.mdc`
+- **6-phase structured review** following `100-core.mdc` and `010-workflow.mdc`
 - **Priority framework:** Critical → Recommended → Optional issues
 - **Language-specific tooling:** Runs appropriate linters (ruff, pylint, shellcheck, etc.)
 - **Security focus:** OWASP Top 10 checks, secrets scanning, dependency audits
-- **Audit integration:** Creates checkpoints and audit reports per `060-agent-audit.mdc`
+- **Audit integration:** Creates checkpoints and audit reports per `020-agent-audit.mdc`
 - **Automated fixes:** Applies formatters and re-stages files
 - **PR-ready output:** Structured report suitable for PR comments
 

commands/check-progress.md

@@ -4,7 +4,7 @@ description: Fix issues, summarize progress, run pre-commit, propose commit mess
 
 # CHECK PROGRESS MODE ACTIVATED
 
-Review current work progress without staging or committing. Fix issues, run quality checks, and propose commit messages following `100-core.mdc` and `110-git.mdc` standards.
+Review current work progress without staging or committing. Fix issues, run quality checks, and propose commit messages following `100-core.mdc` and `130-git.mdc` standards.
 
 > [!IMPORTANT]
 > **Fix mode.** Fix errors and formatting issues, then report what was fixed.
@@ -143,7 +143,7 @@ Provide a structured summary:
 
 **Only if no Critical issues found after fixes:**
 
-Propose **one primary commit message** following `110-git.mdc` format:
+Propose **one primary commit message** following `130-git.mdc` format:
 
 ```
 <type>(<scope>): <short summary>
@@ -242,6 +242,6 @@ If CodeRabbit is available and configured:
 **Integration:** This workflow aligns with:
 
 - `100-core.mdc` Coding standards and Priority Framework
-- `110-git.mdc` Commit message standards
-- `050-workflow.mdc` Review phase patterns
+- `130-git.mdc` Commit message standards
+- `010-workflow.mdc` Review phase patterns
 - Tooling baseline for all supported languages

commands/review.md

@@ -97,4 +97,4 @@ You are now in **REVIEW** phase.
 
 ## After Review
 
-If ready to commit, prepare commit message following 110-git.mdc standards.
+If ready to commit, prepare commit message following 130-git.mdc standards.

commands/self-review.md

@@ -237,4 +237,4 @@ If CodeRabbit is available and configured for the repository:
 - `010-workflow.mdc` Review Phase
 - `100-core.mdc` Code Review Mode standards
 - `020-agent-audit.mdc` Audit requirements
-- `110-git.mdc` Commit standards
+- `130-git.mdc` Commit standards