docs(roadmap): add EU positioning bundle + DACH accounting skills

[furukama]

Summary

Updates docs/content/internal/roadmap.md to reflect the EU positioning bundle filed in this session.

What's added to the roadmap

Connectivity — F6.6 Tailscale, F6.7 Cloudflare, R18.7 SIP, R24 SMS

Deployment — R25 EU deployment recipes (Hetzner / IONOS / Open Telekom Cloud)

Skills — R21.7 Hetzner DevOps, R21.8 SAP Analytics Cloud, R21.9 DATEV, R21.10 Lexware Office

Together the bundle covers the full German B2B story: "deployed on EU sovereign cloud, talking via SIP/SMS through German telcos, integrated with DATEV/Lexware accounting + SAP analytics + Salesforce/HubSpot CRM."

Why DATEV + Lexware specifically

• DATEV (#652, P1) — dominant German SME platform; Steuerberater exchange + bookkeeping. "Submit the receipts to my Steuerberater" is a daily SME chore that's manual today.
• Lexware Office (#653, P1) — sister-of/competitor-to DATEV in the smaller-SME segment.

Together they cover the German SME accounting market end-to-end. US-anchored agent platforms can't speak either — strategic moat for the German market.

Roadmap changes (no scope/priority shifts on existing items)

• Status snapshot adds an "EU positioning bundle" callout
• R21 row updated: 5 launch skills + 4 new skill families (R21.7 / 8 / 9 / 10). Status 1/6 → 1/10.
• R18 row notes R18.7 SIP addition
• F6 bullet notes F6.6 + F6.7 as additional providers
• R24 + R25 rows added to the main feature table (denominator updated)
• Closed count unchanged at 24; total grew from ~145 to ~151

Test plan

• Confirm roadmap renders correctly under the (unlinked) URL
• Confirm new rows display cleanly in the table
• Spot-check that R21.7/8/9/10 + R24 + R25 appear in the umbrella #466

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates the internal roadmap to reflect a newly filed “EU positioning bundle” focused on EU connectivity/deployment options and DACH accounting/analytics skills, aligning the status snapshot and roadmap table with the new initiatives.

Changes:

• Adds an “EU positioning bundle” callout to the status snapshot, describing connectivity, deployment, and skills items.
• Expands R21 (skills pipeline) description and adjusts its progress denominator to include newly filed skill families.
• Extends the main feature table with R24 (SMS via European operators) and R25 (EU deployment recipes), plus a note on SIP outbound under R18.

---

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

[Copilot]

For consistency with the Foundations section wording (“Tailscale Funnel” / “Cloudflare Tunnel”), consider using the full provider names here as well instead of “Tailscale” and “Cloudflare”, since the broader products have multiple components.

[Copilot]

The intro says “21 features”, but the main feature table now includes items #24 and #25 (and already spans beyond 21). Please update the stated feature count (or rephrase) so it matches what’s listed in the table.

[Copilot]

The Priority column is otherwise a single P0/P1/P2 value, but this row uses “P1 (Hetzner) / P2 (IONOS, OTC)”. To keep the table scannable and consistent, consider setting a single priority (e.g., highest/overall) and moving the per-provider breakdown into the Description column.

Suggested change

	| 25 | **EU deployment recipes (Hetzner / IONOS / Open Telekom Cloud)** | Operator guides for deploying HybridClaw on each EU cloud provider — Docker Compose, Terraform, secret-store setup, F6-tunnel vs cloud-native ingress, backup wiring (R23). DSGVO talking points for sales. *Principle X.* | P1 (Hetzner) / P2 (IONOS, OTC) | ⬜ |
	| 25 | **EU deployment recipes (Hetzner / IONOS / Open Telekom Cloud)** | Operator guides for deploying HybridClaw on each EU cloud provider — Docker Compose, Terraform, secret-store setup, F6-tunnel vs cloud-native ingress, backup wiring (R23). DSGVO talking points for sales. Hetzner is the P1 target; IONOS and Open Telekom Cloud remain P2. *Principle X.* | P1 | ⬜ |

[Copilot]

The status legend defines 🟡 N/M as children closed/total, but F6 is still shown as (2/5) while also calling out new children F6.6/F6.7. Consider updating the denominator (e.g., 2/7) or explicitly stating that the 2/5 only tracks the core F6.1–F6.5 milestones and excludes provider add-ons.

Suggested change

	**Foundations:** 5 of 11 fully done (F1–F5 ✅) · F6 + F8 partially done (2/5 each) · F6 also has 2 additional tunnel providers filed (F6.6 Tailscale, F6.7 Cloudflare) · F7, F9, F10, F11 not started.
	**Foundations:** 5 of 11 fully done (F1–F5 ✅) · F6 + F8 partially done (2/5 each) · For F6, the 2/5 tracks the core F6.1–F6.5 milestones only; provider add-ons F6.6 Tailscale and F6.7 Cloudflare are filed separately and excluded from that denominator · F7, F9, F10, F11 not started.

[Copilot]

“R9 peer-delegation” looks inconsistent with the feature name in the table (#9 is “Hierarchical swarm — HC1 delegates to HC2”). Using the same label here would make the status snapshot easier to map to the table.

Suggested change

	**P1/P2:** R10.1 (trajectory capture) just landed early per "data is the asset" rule. R8 brand voice + R9 peer-delegation + R23 backup CLI have PRs in flight.
	**P1/P2:** R10.1 (trajectory capture) just landed early per "data is the asset" rule. R8 brand voice + R9 Hierarchical swarm — HC1 delegates to HC2 + R23 backup CLI have PRs in flight.