Add development and participation workstream docs

docs/.vuepress/config.js

@@ -1159,8 +1159,8 @@ module.exports = {
             ['features/deployment', 'Deploying Mojaloop'],
 			['features/security', 'Mojaloop Security'],
             ['features/engineering', 'Engineering Principles'],
-            ['features/invariants', 'Invariants']
-          ]
+            ['features/invariants', 'Invariants'],
+            ['features/development', 'Continuous Development']          ]
         }
       ]
     }

docs/product/features/development.md

@@ -0,0 +1,40 @@
+# Ongoing Development
+Mojaloop V17.1.0 is not a finished product - of course! There are always new features to be considered, new APIs to be implemented, new portals to be added, and of course there is always ongoing maintenance, and security requires constant vigilance.
+
+The Mojaloop Roadmap addresses and prioritises these needs, placing them on a timeline, and defines them as a set of workstreams. Each of these work streams has a workstream lead, responsible for defining, managing and delivering the workstream to the Mojaloop Community. The workstream lead is supported by a number of contributors, who may be engineers helping to implement a feature, or those who can document the feature, or people helping to define the requirements.
+
+## Active Workstreams
+The current active workstreams are:
+
+- [Participation Tools](./workstreams/participation.html)
+- [Participation Tools for Fintechs](./workstreams/fintech_participation.html)
+- [Deployment Tools](./workstreams/deployment.html)
+- [QA Framework](./workstreams/qa.html)
+- [Dispute Management](./workstreams/dispute.html)
+- [LEI Addressing](./workstreams/lei.html)
+- [ISO 20022 Refinement](./workstreams/iso20022.html)
+- [Mojaloop Evolution](./workstreams/evolution.html)
+- [Performance](./workstreams/performance.html)
+- [Platform Quality and Security](./workstreams/pqs.html)
+- [Core and Releases](./workstreams/core.html)
+
+Click on each to find out details of the workstream, such as objectives and which community members are contributing.
+
+## Candidate Workstreams
+As well as the currently active workstreams, we have a number of candidate workstreams that are "fast followers" behind them - that is, these have been identified as high priority, but as things stand there is insufficient capacity within the Community to address them. These are:
+
+- Implementation of PISP V2.0
+- Operator Portal enhancements - improving the UI, addressing perceived gaps in functionality
+- Merchant Payments - extending the current relatively simple solution for merchant registration and merchant-presented QR code payments to include some of the richer elements a live merchant payments scheme would need.
+- An overlay service to provide B2B payments functionality beyond the payment itself; integration with ERPs, management of supply chains, invoicing etc.
+
+Please contact the Product Director if you'd like to discuss any of these candidate workstreams - in particular, how we make them active!
+
+## Applicability
+
+This version of this document relates to Mojaloop [Version 17.1.0](https://github.com/mojaloop/helm/releases/tag/v17.1.0)
+
+## Document History
+  |Version|Date|Author|Detail|
+|:--------------:|:--------------:|:--------------:|:--------------:|
+|1.0|4th November 2025| Paul Makin|Initial version|

docs/product/features/workstreams/participation.md

@@ -0,0 +1,23 @@
+# Participation Tools Workstream
+The overall objective of the Participation Tools workstream is to develop a “DFSP Tools” portfolio, with the intention of supporting DFSPs and SIs in the integration of the DFSP’s systems with a Mojaloop Hub. Rather than only offering semi-finalised solutions, the portfolio will comprise the tools to carry out an integration, plus a set of exemplar implementations, each tailored to a specific type of DFSP.
+
+It should be emphasised to all DFSPs that reaping the benefits of an inclusive instant payments solution such as Mojaloop relies on the implementation of a “whole ecosystem” approach - and this means extending the reach of the Mojaloop service into the DFSPs’ domains, giving them and their customers the advantages of assurance of transaction finality, lower cost and the reliable delivery of every valid transaction.
+
+## Contributors
+|Workstream Lead|Contributors|
+|:--------------:|:--------------:|
+| James Bush | Sam Kummary, Yevhen Kryiukha, Paul Baker, Vijay Kumar, Phil Green, Steve Haley, Paul Makin |
+
+## Latest Update (Summary)
+The Participation Tools workstream has advanced the long-running effort to refactor and modularise the Mojaloop Connection Manager (MCM). The server component is now fully decoupled from the Mojaloop IaC stack and deployable via Helm into any Kubernetes environment. The onboarding journey has also been re-architected to remove dependency on HashiCorp Vault and Mojaloop’s IAM defaults, allowing standalone, flexible MCM deployments. Only the client-side MCM refactor remains, along with documentation. 
+
+A Docker Compose version of Payment Manager has been developed for smaller DFSPs, and community-facing documentation — including tool selection guidance — has been authored and reviewed. A generalised version of the DRPP system integrator (SI) onboarding guide is planned for future PIs.
+
+## Applicability
+
+This version of this document relates to Mojaloop [Version 17.1.0](https://github.com/mojaloop/helm/releases/tag/v17.1.0)
+
+## Document History
+  |Version|Date|Author|Detail|
+|:--------------:|:--------------:|:--------------:|:--------------:|
+|1.0|4th November 2025| Paul Makin|Initial version|

package.json

@@ -24,10 +24,10 @@
   "devDependencies": {
     "@vuepress/plugin-back-to-top": "^1.9.10",
     "@vuepress/plugin-medium-zoom": "^1.9.10",
-    "got": "^14.5.0",
+    "got": "^14.6.2",
     "husky": "^9.1.7",
     "markdownlint-cli": "^0.45.0",
-    "npm-check-updates": "^19.0.0",
+    "npm-check-updates": "^19.1.2",
     "plantuml-encoder": "^1.4.0",
     "svgo": "^4.0.0",
     "vuepress": "^1.9.10",