docs: rewrite user-facing docs for StatusPro, strip Katana-era remnants

Follow-up sweep after the initial fork commit. The bulk rename caught
identifiers but left many docs/examples describing Katana's manufacturing
ERP domain. This commit rewrites them around StatusPro's actual surface
(7 endpoints, Orders + Statuses).

User-facing rewrites:
- README.md: drops the "Manufacturing ERP" framing; adds a correct "API
  Coverage" table listing the real 9 endpoints + conventions (Bearer auth,
  {data, meta} envelope, page/per_page pagination, per-endpoint rate limits).
- statuspro_mcp_server/README.md: documents the 9 tools and two-step
  confirm pattern.
- packages/statuspro-client/README.md: describes /orders + /statuses flows,
  switches package to @statuspro/client.
- statuspro_public_api_client/docs/{guide,cookbook}.md: rewritten with
  StatusPro-focused examples.
- packages/statuspro-client/docs/{guide,cookbook}.md: same.
- statuspro_mcp_server/docs/{index,README,examples}.md: StatusPro tool flows.
- docs/CHANGELOG.md + statuspro_public_api_client/docs/CHANGELOG.md: reset
  to a v0.1.0 baseline.
- CLAUDE.md: updated Known Pitfalls for StatusPro (per_page vs limit, mixed
  list envelopes, 7 endpoints).
- AGENT_WORKFLOW.md: replaced Katana example scenarios.
- mkdocs.yml: retitled description.
- examples/README.md: points at the per-package cookbooks; dropped
  references to deleted Katana example scripts.

Deletions (Katana-only):
- statuspro_mcp_server/docs/{architecture,implementation-plan}.md
- statuspro_mcp_server/docs/adr/0010-statuspro-mcp-server.md
- statuspro_public_api_client/docs/adr/0007-domain-helper-classes.md
- statuspro_mcp_server/src/statuspro_mcp/tools/{prefab_ui,tool_result_utils,decorators}.py
  (Katana-domain Prefab UI builders + cache-aware decorators; not used by
  the new simple tool implementations).
- scripts/{extract_all_statuspro_docs,create_mcp_issues,create_mcp_issues_from_json,analyze_api_documentation,validate_schema_consistency,test_mcp_resources}.py
  (Katana-specific tooling).

Code changes:
- statuspro_public_api_client/api_wrapper/_registry.py: resource registry
  reduced from 47 Katana resources to 2 StatusPro resources (orders,
  statuses). Only GET /orders, GET /orders/{id}, and GET /statuses fit
  the CRUD shape; mutation endpoints are exposed via domain helpers.
- statuspro_public_api_client/domain/base.py: example docstring rewritten
  around Order instead of StatusProVariant.
- statuspro_mcp_server/src/statuspro_mcp/__init__.py: package docstring
  no longer claims Manufacturing ERP tooling.
- scripts/regenerate_client.py: dropped Katana-specific
  receive_purchase_order.py post-processing step.
- Test dummy tool names updated from check_inventory to update_order_status.

Validation: `uv run poe check` passes (192 tests + lint + typecheck +
yamllint + mdformat).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: dougborg

AGENT_WORKFLOW.md

@@ -76,11 +76,11 @@ Each agent has domain-specific knowledge and follows project patterns.
 For straightforward tasks, use a specialist agent directly:
 
 ```
-@agent-dev implement the create_sales_order tool following the purchase order pattern
+@agent-dev implement the bulk_update_order_status tool following the update_order_status pattern
 ```
 
 ```
-@agent-test write comprehensive tests for the inventory helper functions
+@agent-test write comprehensive tests for the orders helper functions
 ```
 
 ```
@@ -198,7 +198,7 @@ Here's how multiple agents work together on a feature:
 1. **Planning Phase**
 
    ```
-   @agent-plan break down "Add sales order support" into implementation tasks
+   @agent-plan break down "Add richer comment filtering" into implementation tasks
    → Creates detailed plan with phases
    → Identifies dependencies
    → Creates individual issues
@@ -207,7 +207,7 @@ Here's how multiple agents work together on a feature:
 1. **Implementation Phase**
 
    ```
-   @agent-dev implement sales_orders.py following purchase order pattern
+   @agent-dev implement a new tool for filtering by date range, following the list_orders pattern
    → Implements tool with proper patterns
    → Adds error handling and logging
    → Creates PR with changes
@@ -216,7 +216,7 @@ Here's how multiple agents work together on a feature:
 1. **Testing Phase**
 
    ```
-   @agent-test write comprehensive tests for sales_orders tool
+   @agent-test write comprehensive tests for new tool
    → Writes unit tests for all functions
    → Tests success and error paths
    → Verifies 90%+ coverage
@@ -225,7 +225,7 @@ Here's how multiple agents work together on a feature:
 1. **Documentation Phase**
 
    ```
-   @agent-docs document the sales_orders tool
+   @agent-docs document the new tool
    → Adds docstrings
    → Updates README
    → Adds cookbook example
@@ -234,7 +234,7 @@ Here's how multiple agents work together on a feature:
 1. **Review Phase**
 
    ```
-   @agent-review review PR #123 for sales orders
+   @agent-review review PR #123 for new tool
    → Checks pattern adherence
    → Verifies test coverage
    → Validates documentation
@@ -385,8 +385,8 @@ git commit -m "feat: your commit message"
 **Examples:**
 
 ```bash
-git commit -m "feat(mcp): add inventory resources"
-git commit -m "fix(client): handle null values in variants"
+git commit -m "feat(mcp): add status-history resource"
+git commit -m "fix(client): handle null status on orders"
 git commit -m "docs: update AGENT_WORKFLOW.md"
 git commit -m "test: add coverage for edge cases"
 ```
@@ -746,8 +746,8 @@ ______________________________________________________________________
 **Solution:**
 
 - Follow conventional commits format
-- Be specific: "fix(client): handle null variant names"
-- Include context: "refactor: extract helper for variant display names"
+- Be specific: "fix(client): handle empty viable-statuses response"
+- Include context: "refactor: extract helper for order status mapping"
 
 ______________________________________________________________________
 

CLAUDE.md

@@ -139,10 +139,10 @@ at the httpx transport layer — every endpoint gets it automatically.
 
 ## File Rules
 
-| Category      | Files                                        | Action          |
-| ------------- | -------------------------------------------- | --------------- |
-| **EDITABLE**  | `statuspro_client.py`, tests/, scripts/, docs/  | Can modify      |
-| **GENERATED** | `api/**/*.py`, `models/**/*.py`, `client.py` | **DO NOT EDIT** |
+| Category      | Files                                          | Action          |
+| ------------- | ---------------------------------------------- | --------------- |
+| **EDITABLE**  | `statuspro_client.py`, tests/, scripts/, docs/ | Can modify      |
+| **GENERATED** | `api/**/*.py`, `models/**/*.py`, `client.py`   | **DO NOT EDIT** |
 
 Regenerate client: `uv run poe regenerate-client` (2+ min)
 
@@ -260,7 +260,7 @@ tasks:
 | Commit standards  | [.github/agents/guides/shared/COMMIT_STANDARDS.md](.github/agents/guides/shared/COMMIT_STANDARDS.md)             |
 | File organization | [.github/agents/guides/shared/FILE_ORGANIZATION.md](.github/agents/guides/shared/FILE_ORGANIZATION.md)           |
 | Architecture      | [.github/agents/guides/shared/ARCHITECTURE_QUICK_REF.md](.github/agents/guides/shared/ARCHITECTURE_QUICK_REF.md) |
-| Client guide      | [statuspro_public_api_client/docs/guide.md](statuspro_public_api_client/docs/guide.md)                                 |
-| MCP docs          | [statuspro_mcp_server/docs/README.md](statuspro_mcp_server/docs/README.md)                                             |
-| TypeScript client | [packages/statuspro-client/README.md](packages/statuspro-client/README.md)                                             |
+| Client guide      | [statuspro_public_api_client/docs/guide.md](statuspro_public_api_client/docs/guide.md)                           |
+| MCP docs          | [statuspro_mcp_server/docs/README.md](statuspro_mcp_server/docs/README.md)                                       |
+| TypeScript client | [packages/statuspro-client/README.md](packages/statuspro-client/README.md)                                       |
 | ADRs              | [docs/adr/README.md](docs/adr/README.md)                                                                         |