docs(guide): scrub decommissioned QDS_ADMIN role from KB content (#10) #11

2026-07-08T15:41:57-04:00

hiveiq commented

2026-07-08 15:41:57 -04:00

Scrubs the decommissioned QDS_ADMIN role from the Guide knowledge base.

Follow-up to hiveops-incident#253 (already merged), which removed QDS_ADMIN from all 5 backends' SecurityConfig/InstitutionContext and from the hiveops-auth Role enum — so no JWT can carry the role. The Guide KB still quoted QDS_ADMIN in hasAnyRole(...) allow-lists and role/scoping tables, which no longer matched the code.

Changes

Removed QDS_ADMIN from 26 references across 23 content files (analytics, dashboard, devices, incident, msp, platform/auth, recon, technical/transactions, transactions).
Surviving roles (USER, CUSTOMER, ADMIN, MSP_ADMIN, BCOS_ADMIN, plus AGENT/SYSTEM) left exactly as-is.
No frontmatter touched → zero module-coverage impact. Doc-accuracy only, zero runtime change.

Verification

git grep QDS_ADMIN over content/ → 0 hits.
Full diff reviewed line-by-line: every edit removes only the token + one separator; role lists stay well-formed.
scripts/coverage-reconcile.py — the one gap it reports (hiveops-feedback needs technical.feedback) is pre-existing and unrelated to this change (an undocumented service, not a QDS artifact). Worth its own issue.

Closes #10.

Scrubs the decommissioned **`QDS_ADMIN`** role from the Guide knowledge base. Follow-up to **hiveops-incident#253** (already merged), which removed `QDS_ADMIN` from all 5 backends' `SecurityConfig`/`InstitutionContext` and from the hiveops-auth `Role` enum — so no JWT can carry the role. The Guide KB still quoted `QDS_ADMIN` in `hasAnyRole(...)` allow-lists and role/scoping tables, which **no longer matched the code**. ### Changes - Removed `QDS_ADMIN` from **26 references across 23 content files** (analytics, dashboard, devices, incident, msp, platform/auth, recon, technical/transactions, transactions). - Surviving roles (`USER, CUSTOMER, ADMIN, MSP_ADMIN, BCOS_ADMIN`, plus `AGENT`/`SYSTEM`) left exactly as-is. - **No frontmatter touched** → zero module-coverage impact. Doc-accuracy only, zero runtime change. ### Verification - `git grep QDS_ADMIN` over `content/` → **0 hits**. - Full diff reviewed line-by-line: every edit removes only the token + one separator; role lists stay well-formed. - `scripts/coverage-reconcile.py` — the one gap it reports (`hiveops-feedback` needs `technical.feedback`) is **pre-existing and unrelated** to this change (an undocumented service, not a QDS artifact). Worth its own issue. Closes #10.

hiveiq added 1 commit 2026-07-08 15:41:57 -04:00

docs(guide): scrub decommissioned QDS_ADMIN role from KB content 3ace2e06d2

Follow-up to hiveops-incident#253 (QDS_ADMIN removed from all 5 backends'
SecurityConfig/InstitutionContext, and from the hiveops-auth Role enum so no
JWT can carry it). The guide KB still quoted QDS_ADMIN in role/allow-list
descriptions, which no longer matched the code.

Removed QDS_ADMIN from 26 references across 23 content files; surviving roles
(USER, CUSTOMER, ADMIN, MSP_ADMIN, BCOS_ADMIN, AGENT, SYSTEM) left unchanged.
No frontmatter touched -> zero module-coverage impact. Doc-accuracy only.

Closes #10

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

johannes approved these changes 2026-07-08 15:42:43 -04:00

hiveiq merged commit 11d6369ad6 into develop

2026-07-08 16:02:42 -04:00

hiveiq deleted branch chore/purge-qds-admin-kb-10

2026-07-08 16:02:43 -04:00

hiveiq referenced this pull request

2026-07-08 17:00:37 -04:00

[CI] cd-develop run flipped to `failure` ~30 min AFTER the job succeeds (act_runner v0.2.11 / Gitea status-reconciliation) — NOT the smoke window #12

hiveiq referenced this issue from a commit

2026-07-08 17:01:58 -04:00

ci(guide): widen cd-develop smoke health-check window to ~5 min

hiveiq referenced this pull request