Release v3.1.0 — OmniCheck Auto-Approval + OmniCreate Authoring Guidelines · nexiouscaliver/OmniForge

What's New

omnicheck-gitlab auto-approval via bot user — new approve_mr MCP tool that approves a GitLab MR as a dedicated OmniCheck bot when OMNICHECK_BOT_TOKEN is set (falls back to the current glab user). Approval is pinned to the MR HEAD sha so it goes stale on new commits. The skill now branches into nudge (Branch A) or approve (Branch B), with Branch B appearing only when NOT_APPLIED + NEEDS_HUMAN = 0 and firing only on explicit user confirmation.
approve_mr MCP tool — MCP server now exposes 14 tools (was 13). run_subprocess gains an optional env param so the bot token is scoped to the single approval call only.
omnicreate-gitlab authoring guidelines — explicit rules for MR titles (conventional commit format, ≤72 chars, imperative tense) and structured descriptions (Summary, Changes, Testing, Related sections). Enforces fill=false with crafted content.

Event loop hygiene in test fixture — conftest.py autouse fixture now owns one loop per test and closes it in teardown. Full suite passes with -W error::ResourceWarning.
Plugin manifest version bump — plugin.json version field now correctly reads 3.1.0 (was stale at 3.0.0 despite the git tag). /plugin now reports the correct version.

9 new tests for approve_mr (bot-token approval, fallback, sha pinning, error cases, no-head-sha guard).

Full Changelog: v3.0.0...v3.1.0