docs: rewrite README as landing page, add 8 user-facing doc pages

[digitarald]

Summary

Rewrites README from a detailed CLI reference into a concise landing page / pitch. Adds 8 new end-user documentation pages.

Changes

README.md — Landing page with:

• "Context engineering for AI coding agents" tagline
• Problem → solution intro (build/test/lint context, architecture, external services via MCP)
• Measure / Generate / Maintain sections with one command each
• "Works at every scale" table
• "What gets generated" table
• Compact docs table, troubleshooting section

New docs pages:

• docs/getting-started.md — Prerequisites and first run
• docs/concepts.md — Maturity model, readiness pillars, generation
• docs/commands.md — Full CLI reference (every command, every flag)
• docs/configuration.md — agentrc.config.json deep dive
• docs/policies.md — Custom readiness scoring, extras
• docs/at-scale.md — Batch processing, automated PRs, org-wide rollout
• docs/ci-integration.md — GitHub Actions + Azure Pipelines examples
• docs/extension.md — VS Code extension guide

Moved:

• docs/plugins.md → docs/dev/plugins.md
• docs/product.md → docs/dev/product.md

Updated: .github/workflows/daily-doc-updater.md paths

Review notes

• All factual claims (9 pillars, 5 maturity levels, model defaults, generated files) verified against source code
• Azure DevOps covered equally with GitHub across all pages
• All cross-links verified intact

[Copilot]

Pull request overview

This PR restructures AgentRC’s documentation by turning the README into a concise landing page and moving the detailed end-user CLI reference and guides into dedicated docs/ pages.

Changes:

• Rewrite README.md from a full CLI reference into a product-focused landing page with links to the new docs.
• Add a set of end-user documentation pages covering concepts, commands, configuration, policies, CI integration, and scaling workflows.
• Move developer-oriented docs under docs/dev/ and update the daily doc updater workflow references accordingly.

Reviewed changes

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

Show a summary per file

File	Description
docs/policies.md	New policy authoring guide and scoring/extras reference.
docs/getting-started.md	New quickstart covering prerequisites, first run, and next steps.
docs/extension.md	New VS Code extension usage/install/commands/settings guide.
docs/dev/product.md	Product brief moved under developer docs.
docs/dev/plugins.md	Plugin system architecture and API docs moved under developer docs.
docs/configuration.md	New agentrc.config.json deep dive for areas/workspaces/policies.
docs/concepts.md	New conceptual overview: maturity model, pillars, instructions, evals.
docs/commands.md	New full CLI reference (commands + flags) replacing README’s prior role.
docs/ci-integration.md	New CI guidance with GitHub Actions and Azure Pipelines examples.
docs/at-scale.md	New guide for batch processing and automated PR workflows.
README.md	Rewritten as landing page with docs navigation and troubleshooting.
.github/workflows/daily-doc-updater.md	Update workflow’s documented doc-path mapping to include new/moved pages.

Comments suppressed due to low confidence (2)

docs/policies.md:163

• This sentence says adding extras requires a TypeScript plugin because JSON can't express the detection function, but the current policy loader also rejects extras.add in JSON policies outright. Consider clarifying that adding extras is only supported via .ts/.js module policies (not JSON), and must be supplied via --policy (not via agentrc.config.json).

Adding new extras requires a TypeScript plugin — they need a detection function that JSON can’t express. See [Plugin System](dev/plugins.md).

docs/ci-integration.md:86

• Same issue in the Azure Pipelines example: agentrc eval requires Copilot CLI availability and authentication, but the pipeline snippet doesn’t show how to provide that in CI. Please add a setup step or a note clarifying the requirement for runners.

  - script: npx github:microsoft/agentrc eval --fail-level 80 --json
    displayName: Run eval
    env:
      GITHUB_TOKEN: $(GITHUB_TOKEN)
      # AZURE_DEVOPS_PAT: $(AZURE_DEVOPS_PAT)

</details>

[Copilot]

Pull request overview

This PR restructures the repo’s documentation by converting README.md into a concise landing page and moving the detailed reference material into a set of dedicated end-user docs pages (plus relocating dev-oriented docs under docs/dev/).

Changes:

• Rewrote README.md into a product landing page with a compact docs index and troubleshooting.
• Added new end-user documentation pages covering getting started, concepts, commands, configuration, policies, CI integration, at-scale usage, and the VS Code extension.
• Moved dev docs into docs/dev/ and updated the daily doc-updater guidance accordingly.

Reviewed changes

Copilot reviewed 10 out of 12 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
docs/policies.md	New policies guide (usage, chaining, scoring, extras)
docs/getting-started.md	New quickstart and first-run walkthrough
docs/extension.md	New VS Code extension user guide
docs/dev/product.md	Moved/updated product brief under dev docs
docs/dev/plugins.md	Moved/updated plugin system architecture doc
docs/configuration.md	New/rewritten configuration deep dive (agentrc.config.json)
docs/concepts.md	New concepts overview (maturity model, pillars, instructions, eval)
docs/commands.md	New full CLI reference (flags and commands)
docs/ci-integration.md	New CI guidance with GitHub Actions + Azure Pipelines examples
docs/at-scale.md	New batch/org-scale workflows guide
README.md	Rewritten as landing page + doc index + troubleshooting
.github/workflows/daily-doc-updater.md	Updated doc-location mapping to match new structure

[Copilot]

Pull request overview

Reworks the repository documentation structure by turning the README into a concise landing page and moving detailed end-user guidance into a set of dedicated docs pages (including new “dev” docs for internal/plugin architecture).

Changes:

• Rewrite README.md from a full CLI reference into a product/landing overview with links to deeper docs.
• Add new end-user docs pages for getting started, concepts, commands, configuration, policies, CI integration, at-scale usage, and the VS Code extension.
• Move plugin/product “developer” docs under docs/dev/ and update the daily doc updater guidance accordingly.

Reviewed changes

Copilot reviewed 10 out of 12 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
docs/policies.md	New policy authoring/usage guide (JSON vs module policies, scoring, extras).
docs/getting-started.md	New quickstart: prerequisites, first run, init/eval/readiness usage.
docs/extension.md	New VS Code extension usage guide (commands, views, settings).
docs/dev/product.md	New developer-facing product brief moved under docs/dev/.
docs/dev/plugins.md	New developer-facing plugin system documentation moved under docs/dev/.
docs/configuration.md	New agentrc.config.json deep dive (areas/workspaces/strategy/policies).
docs/concepts.md	New conceptual overview (maturity model, pillars, instructions, eval).
docs/commands.md	New full CLI reference (commands, flags, defaults).
docs/ci-integration.md	New CI guidance with GitHub Actions + Azure Pipelines examples.
docs/at-scale.md	New batch/org-scale workflows documentation.
README.md	Landing page rewrite + docs index table + troubleshooting.
.github/workflows/daily-doc-updater.md	Update doc-location guidance to point to the new docs layout.