chore: update projectops docs

[mnkiefer]

• Updated ProjectOps page with practical workflow examples and best practices for secure and effective project board management (agentically).

[Copilot]

Pull request overview

This PR updates the ProjectOps documentation page with a significantly restructured and more concise set of instructions, replacing the previous broad overview with a practical "how it works" walkthrough that includes two concrete workflow examples (a read-only board summarizer and a write-enabled board maintainer). It also adds a deep-research-report.md file at the repository root.

Changes:

• Rewrote project-ops.mdx: replaced lengthy feature-list-style sections with a focused, example-driven guide including a "Project Board Summarizer" (read-only) and a "Project Board Maintainer" (write operations) workflow.
• Removed standalone sections (Available Safe Outputs, Key Capabilities, Common Challenges, Additional Resources) and consolidated them into shorter "How it works" and "Best practices" sections.
• Added deep-research-report.md at the repo root containing an AI-generated research document about agentic project board management.

Reviewed changes

Copilot reviewed 2 out of 6 changed files in this pull request and generated 2 comments.

File	Description
docs/src/content/docs/patterns/project-ops.mdx	Restructured documentation with practical examples, updated prerequisites, and a new "How it works" section
deep-research-report.md	New research document (raw AI-generated output with unprocessed citation markers) added to repo root

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Hey @mnkiefer 👋 — great work refreshing the ProjectOps page! The restructured "how it works" section, the two-phase Summarizer → Maintainer walkthrough, and the new board screenshots are all clear improvements that make the pattern much easier to follow.

A couple of things to flag before this lands:

• Process check — The CONTRIBUTING.md specifies that PRs should be created by core team members (those listed in CODEOWNERS). Your name does not currently appear in CODEOWNERS (@dsyme @eaftan @pelikhan @krzysztof-cieslak``). If you are part of the core team but not yet listed, that's worth a quick clarification from a maintainer. If you are not on the core team, the expected path is to open an issue with an agentic plan and have a core team member create the PR.
• No test signal — The diff is documentation-only (.mdx + images), so there is nothing to unit-test. That said, the project's make test suite does run on all PRs; confirm that CI is green before merging.

Generated by Contribution Check · ◷