Update known issues

Author: webprofusion-chrisc

docs/hub/index.md

@@ -25,3 +25,4 @@ The product is available to try out as an release candidate version (shortly to
 ![Startup UI](/assets/screens/hub/hub_intro.png)
 
 
+- For info on current and future planned development see our [hub product roadmap](roadmap.md).

docs/hub/known-issues.md

@@ -8,6 +8,10 @@ title: Known Issues
 As we move development of *Certify Management Hub* towards a full release we will note issues that are commonly encountered here, and remove them as they are resolved.
 :::
 
+### Hub connections
+Instances of *Certify Certificate Manager* and *Certify Management Agent* services may need to be restarted (just the service, not the OS) to reconnect to a hub that has restarted or been updated. We recommend updating agents/ccm instances to the latest version corresponding to the hub when possible, although not strictly required for some minor updates.
+
+
 ### User Interface
 
 #### Errors when trying to login
@@ -32,4 +36,4 @@ Multiple instances of the Certify Agent or Management Hub service reading and wr
 Note: We do not provide general support for how to use different container technology and you will likely need to know more about your choice of container deployment technology than we do, if you are using containers at all. Certify Management Hub is our first product that supports deployment to containers, so we expect growing pains.
 
 ### Windows Specific Tasks
-If you will be commonly running PowerShell etc and interacting with Windows Server using Windows AAuthentication you should host the Management Hub on a Windows Server install. The hub *can* be used in containers (or hosted directly on Linux) but with reduced compatibility for Windows specific things like Windows Impersonation credentials.
+If you will be commonly running PowerShell etc and interacting with Windows Server using Windows Authentication you should host the Management Hub on a Windows Server install. The hub *can* be used in containers (or hosted directly on Linux) but with reduced compatibility for Windows specific things like Windows Impersonation credentials.

docs/hub/roadmap.md

@@ -0,0 +1,53 @@
+---
+id: hub-roadmap
+title: Product Roadmap
+sidebar_label: Roadmap
+---
+
+# Product Roadmap
+
+The roadmap highlights current focus areas for the Certify Management Hub. Timelines are indicative and subject to change as we gather feedback from production deployments.
+
+## Release Status
+
+| Track | Status | Notes |
+| --- | --- | --- |
+| Hub Release Candidate | ✅ Available | Production-suitable with staged rollout and known issues documented. |
+| Agent (Windows/Linux) | ✅ Available | Supports on-device certificate renewal with hub management and 3rd party ACME client reporting. |
+
+## Near-Term
+
+1. **Production GA packaging**
+   - Finalize installers and container images.
+   - Harden upgrade paths from RC builds.
+
+2. **Managed Instances**
+   - Better management UI
+   - Improved connection resilience
+   - Better synchronization
+
+3. **General Refinements**
+   - Responding quickly to customer feedback with releases for important issues etc.
+
+## Mid-Term 
+
+1. **Hub-native Managed Challenges**
+   - When working with managed challenges it should become simple or zero-config to use a managed challenge via the hub from any authorized instance including the hub itself.
+
+2. **Tagging**
+   - Enhanced ways to tag and categorized items in the hub for easier navigation and filtering when working with large numbers of items or instances.
+
+## Future
+1. **Pull certificates**
+   - Pull and deploy the latest certificate managed by the hub to an agent
+   
+## Recently Delivered
+
+- Web-based management UI with API parity to the desktop CCM experience.
+- Optional single sign-on through OIDC providers such as Azure Entra.
+- Centralized visibility of renewal status, including non-Hub ACME clients.
+- Integrated DNS challenge service to avoid distributing privileged DNS credentials.
+
+---
+
+Feedback helps prioritize items - contact support if a feature is critical to your deployment.