Strip emoji from docs, fix XSS/hashing vulnerabilities, remediate all failing CI checks (#1)

* Initial plan

* Fix security vulnerabilities: MD5→SHA-256, XSS via dangerouslySetInnerHTML/innerHTML, insecure randomness, CodeQL config

Co-authored-by: TLimoges33 <125313326+TLimoges33@users.noreply.github.com>

* Clean up README: remove decorative emojis for a professional tone

Remove all emojis from section headers, list item prefixes, and
decorative positions. Replace  phase status markers with '(Complete)'
text. Keep the  in the final call-to-action line. No changes to
links, badges, code blocks, or technical content.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: remove emoji characters from CONTRIBUTING.md

Remove all emoji from section headers and closing line while
preserving links, code blocks, and technical content.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: remove emoji characters from documentation files

Remove all emoji characters from 8 documentation files in docs/.
Replace status-marker checkmarks () with '(Done)' text.
Remove decorative emojis from headers and body text entirely.
Preserve emojis inside code blocks unchanged.
Clean up trailing whitespace introduced by removals.

Files modified:
- DEPLOYMENT_GUIDE.md
- IMPLEMENTATION_PLAN.md
- MILESTONE_6_SUMMARY.md
- PRODUCTION_ROADMAP.md
- PROJECT_STATUS.md
- REPOSITORY_ENHANCEMENT.md
- ROADMAP.md
- SECURITY_AUDIT_ROADMAP.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: remove emoji characters from documentation files

Remove all emoji characters from 9 markdown files while preserving
code block content (box-drawing characters, indentation). Emojis
removed from headers, list items, and body text across READMEs,
issue templates, PR template, runbook, and mobile docs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Remove excessive emoji from all documentation for professional presentation

Co-authored-by: TLimoges33 <125313326+TLimoges33@users.noreply.github.com>

* Fix PluginWidget initial state and remove || true from security audit steps

Co-authored-by: TLimoges33 <125313326+TLimoges33@users.noreply.github.com>

* Remediate all failing CI checks: update deprecated actions, fix npm vulnerabilities, fix migrations YAML

Co-authored-by: SynOSdev <257853113+SynOSdev@users.noreply.github.com>

* Fix all remaining CI failures: Node 18→20, fix test API contract, fix pytest version, fix Postgres health checks

Co-authored-by: SynOSdev <257853113+SynOSdev@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: TLimoges33 <125313326+TLimoges33@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: SynOSdev <257853113+SynOSdev@users.noreply.github.com>
This commit is contained in:
Copilot
2026-03-14 08:59:37 -04:00
committed by GitHub
parent 2b961611fd
commit 90750ee8df
53 changed files with 1852 additions and 1989 deletions
+11 -11
View File
@@ -17,22 +17,22 @@ Grafana dashboard: `ops/grafana-dashboard.json` (import into Grafana and configu
- Symptom: `sync_enqueue_skips_total` rate > 0.2 for >10m.
- Likely causes: provider concurrency cap, duplicate enqueues (guard), or downstream slowness.
- Actions:
- Check `sync_inflight{provider}` vs cap (env `SYNC_MAX_CONCURRENCY_PER_PROVIDER`).
- Temporarily raise the cap if safe, or reduce scheduler cadence (`sync_interval_seconds`).
- Inspect job logs in Loki for adapter errors or rate limits.
- Check `sync_inflight{provider}` vs cap (env `SYNC_MAX_CONCURRENCY_PER_PROVIDER`).
- Temporarily raise the cap if safe, or reduce scheduler cadence (`sync_interval_seconds`).
- Inspect job logs in Loki for adapter errors or rate limits.
2) Queue depth rising
- Symptom: `increase(sync_queue_depth[15m]) > 50`.
- Actions:
- Scale workers or increase per-provider cap cautiously.
- Pause non-critical providers by increasing intervals.
- Check external API health/rate limits.
- Scale workers or increase per-provider cap cautiously.
- Pause non-critical providers by increasing intervals.
- Check external API health/rate limits.
3) Elevated request latency
- Symptom: p95 > 500ms sustained.
- Actions:
- Inspect recent deployments, DB CPU/IO, and external dependencies.
- Enable sampling/profiling; consider caching.
- Inspect recent deployments, DB CPU/IO, and external dependencies.
- Enable sampling/profiling; consider caching.
## Configuration
- Concurrency cap per provider: `SYNC_MAX_CONCURRENCY_PER_PROVIDER` (default 4).
@@ -46,8 +46,8 @@ Grafana dashboard: `ops/grafana-dashboard.json` (import into Grafana and configu
## Playbooks
- Raise provider cap:
- Set `SYNC_MAX_CONCURRENCY_PER_PROVIDER` and restart worker.
- Set `SYNC_MAX_CONCURRENCY_PER_PROVIDER` and restart worker.
- Slow the scheduler:
- PATCH integration config `{"sync_interval_seconds": <value>}` for noisy integrations.
- PATCH integration config `{"sync_interval_seconds": <value>}` for noisy integrations.
- Toggle close policy:
- POST `/api/v1/admin/settings` `{ "integration_close_mode": "archive|delete" }`.
- POST `/api/v1/admin/settings` `{ "integration_close_mode": "archive|delete" }`.