Enhance CONTRIBUTING.md and update dependencies

- Added a contents section to the CONTRIBUTING.md file for better navigation.
- Included detailed instructions for running development checks and automated tests before submitting pull requests.
- Updated package.json and package-lock.json to include `vitest` as a new dependency for testing.
- Corrected the link to the CONTRIBUTING.md file in the README.md for improved accessibility.

These changes aim to improve the contribution process and enhance the development workflow.

Author: SeeWhatsOn

CONTRIBUTING.md

@@ -2,6 +2,8 @@
 
 This document describes the contribution process and governance policies of the FINOS Electron FDC3 Desktop Agent & App Directory project. The project is also governed by the [Linux Foundation Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), and the FINOS [IP Policy](https://github.com/finos/community/blob/master/governance/IP-Policy.pdf), [Code of Conduct](https://github.com/finos/community/blob/master/governance/Code-of-Conduct.md), [Collaborative Principles](https://github.com/finos/community/blob/master/governance/Collaborative-Principles.md), and [Meeting Procedures](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md).
 
+**Contents:** [Contribution process](#contribution-process) · [Development, checks, and automated tests](#development-checks-and-automated-tests) · [Security](#reporting-security-issues) · [Governance](#governance)
+
 ## Contribution Process
 
 Before making a contribution, please take the following steps:
@@ -14,6 +16,40 @@ Before making a contribution, please take the following steps:
 
 NOTE: All contributors must have a contributor license agreement (CLA) on file with FINOS before their pull requests will be merged. Please review the FINOS [contribution requirements](https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/75530375/Contribution+Compliance+Requirements) and submit (or have your employer submit) the required CLA before submitting a pull request.
 
+## Development, checks, and automated tests
+
+For build and run instructions (browser and Electron), see the [README](README.md).
+
+### Before you open or update a pull request
+
+Run the same checks used in continuous integration (see [.github/workflows/ci.yml](.github/workflows/ci.yml)):
+
+1. `npm install`
+2. `npm run format:check`
+3. `npm run lint`
+4. `npm run build`
+5. `npm run test`
+
+Use a **Node.js** version consistent with the `node-version` set in `ci.yml`.
+
+Use clear **commit messages** (imperative subject line, optional body explaining _what_ and _why_) so history and `git bisect` stay usable.
+
+### Automated tests
+
+When you add or materially change behavior, include **new or updated automated tests** in the same change when practical, so CI exercises the behavior you introduce.
+
+The main automated suite today is in **`packages/da-impl`**: Gherkin features and step definitions under [`packages/da-impl/test/`](packages/da-impl/test/). **`packages/common`** includes **Vitest** unit tests under [`packages/common/test/`](packages/common/test/). From the repository root, `npm run test` runs each workspace `test` script where one is defined.
+
+Feature requests may include suggested test ideas in the [Feature request issue template](.github/ISSUE_TEMPLATE/Feature_request.md); bug reports may do the same in the [Bug report template](.github/ISSUE_TEMPLATE/Bug_report.md).
+
+### Code style
+
+Follow the repository **Prettier** and **ESLint** configuration (`format:check` and `lint` above).
+
+## Reporting security issues
+
+Please do not report security vulnerabilities in public GitHub issues. Follow [SECURITY.md](SECURITY.md).
+
 ## Governance
 
 ### Roles

README.md

@@ -181,7 +181,7 @@ To join the Electron FDC3 Desktop Agent & App Directory mailing list please emai
 
 1. Fork it (<https://github.com/finos/fdc3-sail/fork>)
 2. Create your feature branch (`git checkout -b feature/fooBar`)
-3. Read our [contribution guidelines](.github/CONTRIBUTING.md) and [Community Code of Conduct](https://www.finos.org/code-of-conduct)
+3. Read our [contribution guidelines](CONTRIBUTING.md) and [Community Code of Conduct](https://www.finos.org/code-of-conduct)
 4. Commit your changes (`git commit -am 'Add some fooBar'`)
 5. Push to the branch (`git push origin feature/fooBar`)
 6. Create a new Pull Request

package-lock.json

@@ -4,7 +4,8 @@
   "description": "",
   "scripts": {
     "clean": "npx rimraf dist",
-    "build": "tsc"
+    "build": "tsc",
+    "test": "vitest run"
   },
   "main": "dist/src/index.js",
   "types": "dist/src/index.d.ts",
@@ -14,7 +15,8 @@
   "devDependencies": {
     "electron": "^36.9.5",
     "fast-check": "^4.5.3",
-    "rimraf": "^6.0.1"
+    "rimraf": "^6.0.1",
+    "vitest": "^3.2.4"
   },
   "dependencies": {
     "@finos/fdc3": "2.2.1-beta.3",