…ser-sessions

fix(whatsapp): multi-user session isolation and bridge message handling

…ser-sessions

fix(whatsapp): multi-user session isolation and bridge message handling

…ser-sessions

fix(whatsapp): multi-user session isolation and bridge message handling

… document edit-result caveat

Independent review of v6.8 Part 2 flagged 3 polish items. All addressed.

## Regex tightening (NousResearch#75 follow-up)

The bullet-not-applicable regex `\S.{6,}` was accepting reasons of
7 chars (1 + 6) but the docstring and tests asserted ≥8 chars to
match the `imports_match_deliverable_entrypoints` invariant.

Tightened to `\S.{7,}` so 1 + 7 = 8 chars minimum. Same as the
imports_match length check, no off-by-one.

## Integration test gaps (NousResearch#74 follow-up)

Reviewer flagged two missing integration cases:
- Bare `verdict: reject` with no test_quality fields: floor bypasses
  (because verdict IS reject) but reviewer-fields gate catches the
  missing discipline. New test asserts the gate that catches it is
  MissingReviewerFieldViolation, NOT RuntimeFloorViolation. This
  proves the bypass doesn't accidentally green-light no-evidence
  rejects.
- No verdict at all: parsed_verdict is None, is_honest_reject is
  False, floor fires normally. New test asserts a result like "Just
  my thoughts, no verdict line." doesn't silently bypass the floor.

## edit_completed_task_result documentation

The reviewer noted this function exists at kanban_db.py:4180 to back-
fill results on done tasks (via `hermes kanban edit`). It bypasses
EVERY v6.7/v6.8 gate. If a future maintainer wires it into a worker
tool surface, every gate becomes bypassable: complete with low-
discipline, edit to high-discipline, or flip approve↔reject after
the gate already ran.

Added a multi-line .warning:: docstring listing every gate it
bypasses and the specific attacks a worker-accessible wiring would
enable. No code change — this is a comment-level guard for human
ops.

107/107 in test_kanban_completion_gates.py pass (105 + 2 new).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…_applicable evidence (NousResearch#74, NousResearch#75)

Two precision fixes for the v6.7 completion gates surfaced by the
2026-06-10 validation chain on hermes-dashboard. Both touch
kanban_completion_gates.py and ship together.

Closes hermes-jarvis#74 (honest-reject floor bypass)
Closes hermes-jarvis#75 (bullet not_applicable for evidence)

NousResearch#74: verify_runtime_floor gains is_honest_reject kwarg. When True
AND worker is in REVIEW_ROLES, floor bypassed. Build/orchestration
roles unaffected — a friday 60-second 'implementation' that ends
in reject still warrants the 5-min floor. Verdict parsed once at
top of _v6_7_run_completion_gates via existing _v6_7_parse_verdict.

NousResearch#75: _field_present for test_quality.evidence accepts
'- not_applicable: <reason>' bullet with reason ≥8 chars (regex
tightened from \\S.{6,} to \\S.{7,} per self-review). Same
code_change_context rule — code-touching reviews require real
citations.

Polish from self-reviews:
- Tightened bullet regex to enforce ≥8 chars
- Added 2 integration tests (bare reject hits reviewer-fields,
  null verdict still subject to floor)
- Documented edit_completed_task_result as bypassing every gate
- Removed stale dangling reference in kanban_tools.py
  (_enforce_kanban_complete_hygiene call) that would NameError

107 tests in test_kanban_completion_gates.py. 191/191 across full
v6.7+v6.8 + adjacent regression set, zero failures.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>