v3.1.2 - Clearer Dokploy shared env layers

What changed

This patch release makes Code Mode guidance much clearer around Dokploy's two shared environment layers:

• project.env is now documented as the project-level shared environment shown on the project UI surface.
• environment.env is now documented as the separate environment-level shared environment.
• Search ranking now prefers the exact project.* or environment.* procedure family when a prompt names one of those layers.
• Regression coverage now verifies both read/update recommendations and the gateway's distinct /project.update vs /environment.update calls.

Why it matters

A prompt such as "project env update" could previously surface environment.update first, which made it too easy to write to the environment-level shared env while expecting the project-level shared env visible in the Dokploy UI. This release keeps those two surfaces explicit and safer to edit with a read-modify-write workflow.

Validation

• npm test - 554 tests passed
• npm run lint
• npm run typecheck
• npm run build
• npm run docs:check:facts
• npm run ci:budgets
• npm run smoke:mcp
• npm run smoke:search
• npm run smoke:execute
• node dist/index.js version reports @vibetools/dokploy-mcp v3.1.2

Full Changelog: v3.1.1...v3.1.2