[Guide] technical.feedback module missing — coverage-reconcile.py exits 1 #26

New Issue

2026-07-16T15:04:29-04:00

hiveiq commented

2026-07-16 15:04:29 -04:00

python3 scripts/coverage-reconcile.py currently reports:

Guide coverage — 126 documented modules across 19 apps

❌ 1 MISSING (in code, not in guide):
   [SERVICE] hiveops-feedback  →  needs  technical.feedback

and exits 1.

hiveops-feedback is a backend service (src/main/java/com/hiveops), so check 1 expects a technical.feedback module. It has none. The service is live in prod (deployed 2026-07-09, ports 8024/5190).

Why this matters beyond a red exit code

The reconciler is meant to be usable as a session-start / CI gate. A permanently-failing check trains everyone to ignore it, which is how #23 (fleet.task-permissions undocumented) went unnoticed for as long as it did — though note that one had a different cause and the reconciler could not have caught it either way (see the SPA-nav blind spot issue).

Scope

Add content/technical/feedback/ following the shape of a sibling technical.* module. Grounded in hiveops-feedback source — endpoints, tables, Kafka topics, roles, gotchas.

Worth confirming first: is the queue still empty pending browser#85? If the service is effectively dormant, the module should say so rather than describe a flow nobody exercises.

`python3 scripts/coverage-reconcile.py` currently reports: ``` Guide coverage — 126 documented modules across 19 apps ❌ 1 MISSING (in code, not in guide): [SERVICE] hiveops-feedback → needs technical.feedback ``` and exits **1**. `hiveops-feedback` is a backend service (`src/main/java/com/hiveops`), so check 1 expects a `technical.feedback` module. It has none. The service is live in prod (deployed 2026-07-09, ports 8024/5190). ### Why this matters beyond a red exit code The reconciler is meant to be usable as a session-start / CI gate. A permanently-failing check trains everyone to ignore it, which is how #23 (`fleet.task-permissions` undocumented) went unnoticed for as long as it did — though note that one had a *different* cause and the reconciler could not have caught it either way (see the SPA-nav blind spot issue). ### Scope Add `content/technical/feedback/` following the shape of a sibling `technical.*` module. Grounded in `hiveops-feedback` source — endpoints, tables, Kafka topics, roles, gotchas. Worth confirming first: is the queue still empty pending browser#85? If the service is effectively dormant, the module should say so rather than describe a flow nobody exercises.

hiveiq added the Bug

Priority

Medium

labels 2026-07-16 15:04:38 -04:00

hiveiq self-assigned this 2026-07-16 15:04:38 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hiveiq-src/hiveops-guide#26