fix: parent-scoped list deep links and coding standards guardrail

[cursor]

Description

Coding standards review found that trigger and input_set list results could generate incorrect openInHarness deep links (child identifier substituted for parent pipeline_id). PR #756 fixes triggers; this change completes the pattern for input sets and adds an automated guardrail.

Changes:

• Add parentScopedListExtract / pipelineScopedListExtract in extractors.ts to inject parent scope onto list rows
• Apply to trigger and input_set list operations in pipelines.ts
• Fix trigger.delete to require pipeline_id as targetIdentifier query param
• Add parent-scoped-list-deep-links.test.ts regression tests
• Add coding-standards test blocking bare pageExtract when deepLinkTemplate needs a parent identifier field

Type of Change

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

Checklist

• pnpm test passes (2721 tests)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes (78 guardrail tests)
• pnpm docs:check passes

Coding Standards (registry-driven MCP model)

• No new server.registerTool() calls — only toolset/extractor changes
• Shared response extractors from src/registry/extractors.ts
• No console.log() in src/

Standards review summary

The repo enforces architecture rules via pnpm standards:check (77+ tests) in CI. All checks pass on main. This PR adds one more guardrail for parent-scoped list deep links.

  

[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.}