[mrz1836]

What Changed

• GO_PRE_COMMIT_GOLANGCI_LINT_VERSION: v2.14.0 → v2.15.0 (.github/env/10-pre-commit.env)
• MAGE_X_VERSION: v1.29.1 → v1.29.3 (.github/env/10-mage-x.env)
• MAGE_X_GOLANGCI_LINT_VERSION: v2.14.0 → v2.15.0 (.github/env/10-mage-x.env)
• Updated .devcontainer.json and .vscode/settings.json: the Go lint tool is now golangci-lint-v2, and the VS Code lint flag changed from --fast to --fast-only. The dev container image is now mcr.microsoft.com/devcontainers/go:2-1-trixie. The explicit mounts block was removed, and the magex install moved from postStartCommand to onCreateCommand.
• Removed the Nancy references and the Cursor Rules entry from .github/CODEOWNERS, .github/SECURITY.md and .github/docs/repository-features.md. Docs now point to OSV-Scanner for dependency scanning. Workflow links in SECURITY.md were made relative, and a reference to .github/workflows/release.yml became fortress-release.yml. The .github/actions/ CODEOWNERS pattern was also changed.
• Added a "do not include secrets" warning to the bug report and question issue templates. The bug report label changed from bug-p3 to bug-P3, and the Go version placeholder now says "output of go version".
• Changed .goreleaser.yml release prerelease from "false" to auto. Also updated a comment in 20-workflows.env and one in 10-mage-x.env, and made a large edit to .vscode/tasks.json (+7/-87) whose diff is not shown.

Why It Was Necessary

• Keeps tooling configuration, editor and dev container settings, and documentation consistent with the upstream source of these synchronized files.
• Removes outdated references (Nancy, Cursor Rules, old workflow file names) so the docs match the current CI setup.
• Encourages issue reporters to redact sensitive data, and lets GoReleaser mark pre-release tags automatically.

Testing Performed

• The changes are configuration, documentation and template edits, so no code paths were modified and no unit tests were affected.
• The diff was reviewed to confirm that only the listed files and values changed.
• The dev container's postCreateCommand (magex lint && magex vet && magex test) can be used to validate the setup after a rebuild.

Impact / Risk

• Low risk overall: no application or library code changes.
• Developers will need to rebuild the dev container to pick up the new base image and the onCreateCommand change. Dropping the explicit Docker socket and build cache mounts may change local container behavior.
• The prerelease: auto setting changes how GitHub releases are flagged on tagged releases. Pre-release tags will now be marked automatically.