Three features live on production had no coverage at all, so the bot could only
answer questions about them by emailing support.
Pay Control (6.2, 6.5) — zero prior mentions. Vista and Foundation only, and
only AP Admin / Accountant / Support see the column, which is the answer to
almost every "why can't I see this" question about it. Bulk Assign Pay Control
is Foundation-only: Vista companies see the column and cannot bulk-assign from
it, which is the sort of thing support otherwise guesses at. Also adds the
Sitting With column, which was missing from the column list.
Annotating a document (7.8) — zero prior mentions. The four stamps
(TAX EXEMPT, RECEIVED, APPROVED, VOID), the free-text note, and the consequence
people actually ask about: the marks are burned into the image, so they travel
to the ERP and cannot be peeled off — changing one means re-annotating.
File types (5.7) — the distinction that catches people out is that an EMAILED
iPhone HEIC photo is converted automatically,…
Section 18 was a single paragraph saying project managers can approve
from the field, so the bot answered "Beiing Human does not mention a
dedicated mobile app" and mailed the support alias for anything more
specific.
Rewrites it against beiing-human-mobile v2.3.2: install and sign-in
(including the Accountant / AP Admin login block, which is by design and
was being triaged as a password problem), the dashboard, lists, the
document screen, what each status allows, the approve-time validation
gate and why there is no "Approve Anyway", Q&A, uploads, Create PO,
notifications, forced updates, and what the app cannot do. The existing
settings-propagation answer is kept as 18.11, next to the cached-profile
fix it belongs with, since permissions are read at sign-in only.
test_knowledge_base.py drives app.respond() directly — same prompt, same
knowledge base as the Space — with the SES client stubbed so a run mails
nobody. A probe fails when the real trigger logic would have sent an
unanswer…
