Maintenance Documentation

[Mouse933]

This PR adds in a new file that shows how to fix the docusaurus instance/documentation hub when the issue that was preventing the test deployment from working is present.

Alongside this it also has the broader goal of setting up a maintenance hub for the cybersecurity team where all teams can compile maintenance and break fix documentation for our various tools. This will aid redback as a whole by reducing the time needed for future cohorts to find fixes for common issues that have been noted and logged, giving them simple easy to understand instructions they can use to get the tool or repository back to a working condition as quickly as possible.

[github-actions]

🔒 OWASP Scanner Results

No vulnerabilities detected.

### File: docs/cybersecurity/Maintenance Docs/Docusaurus Maintenance/Test Deployment Failing Yarn Lockfile.md

🔒 OWASP Scanner Results for docs/cybersecurity/Maintenance Docs/Docusaurus Maintenance/Test Deployment Failing Yarn Lockfile.md

✅ No vulnerabilities found.

### File: docs/cybersecurity/Maintenance Docs/Docusaurus Maintenance/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/Maintenance Docs/Docusaurus Maintenance/_category_.json

✅ No vulnerabilities found.

### File: docs/cybersecurity/Maintenance Docs/Maintenance Introduction.md

🔒 OWASP Scanner Results for docs/cybersecurity/Maintenance Docs/Maintenance Introduction.md

✅ No vulnerabilities found.

### File: docs/cybersecurity/Maintenance Docs/_category_.json

🔒 OWASP Scanner Results for docs/cybersecurity/Maintenance Docs/_category_.json

✅ No vulnerabilities found.

✅ Good to go.

[VishalAbiman05]

Security review – PR #330

I've reviewed the maintenance documentation changes, including the Yarn lockfile troubleshooting guide and the introduction.

What I checked:

• No hardcoded credentials, API keys, tokens, or internal IP addresses
• No real secrets or sensitive infrastructure details exposed
• Commands are standard for Yarn and Docusaurus maintenance
• External links to GitHub and Yarn documentation use HTTPS

Security observations and suggestions:

1. sudo usage – In a prior screenshot I saw a command like sudo /home/bin/act. If users are instructed to use sudo with act, please add a warning:

   "Running commands with sudo grants elevated privileges. Only do this if you trust the script and understand the risks."

2. yarn install without --frozen-lockfile – Step 4 instructs users to run yarn install (without the flag) to regenerate the lockfile. This is fine, but consider adding a note:

   "After regenerating, always verify that only expected dependencies changed. Review the diff before committing."

3. Running act locally – The optional step using act executes CI workflows that could modify files or access secrets (though it's expected to fail). Recommend adding:

   "Before running act, ensure you are in a clean directory and have no sensitive environment variables set. The tool may attempt to emulate GitHub Actions behaviour."

Overall assessment:
The documentation is well-written and addresses a real maintenance issue. No blocking security problems. Good to merge after considering the minor security warnings above.