fix: route DB Ops authoring execute through dbops prefix

[cursor]

Description

Fixes the DB Ops LLM authoring execute route so database_execute_llm_authoring_pipeline.run calls /dbops/v1/orgs/{org}/projects/{project}/llm-authoring/execute-pipeline instead of the bare /v1/... path that returns 404 in QA/prod routing.

Updated the DB Ops registry path and focused path assertions.

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other

Checklist

• pnpm test passes
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes (architecture guardrails — see docs/coding-standards.md)
• pnpm docs:check passes (if registry/tool counts changed)

Focused verification:

• pnpm exec vitest run tests/registry/dbops.test.ts tests/registry/toolsets/dbops.test.ts -t "database_execute_llm_authoring_pipeline"

Coding Standards (registry-driven MCP model)

If this PR adds or changes Harness API coverage:

• No new server.registerTool() calls — only toolset definitions in src/registry/toolsets/
• Toolset registered in ALL_TOOLSETS and ToolsetName union
• operationPolicy on every new/changed endpoint
• Shared response extractors from src/registry/extractors.ts (no raw passthrough on real endpoints)
• identifierFields and scope declared on new resources
• No console.log() in src/ (stdio JSON-RPC safety)

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}