Repository navigation
Description
Parent
Delivery status — 2026-10-08 reconciliation
Existing task codex/local/01a1131c-b268-7212-9ac8-d1c7bf9b6e28 remains the owner. Draft PR #1104 and Provider candidate #14 have automated/CI evidence, but real Lark form submission and final-card qualification still need a fresh Human-arranged platform window. The first failed attempt is recovery evidence, not successful platform acceptance. Do not create a duplicate implementation task or take the production receiver under a previous window's authorization.
Configuration placement follows #1083: use the Bot DM Channel sidebar's shared Approvals/Approvers/destination management; the old Profile screenshots in the draft describe that candidate, not the final placement contract. Group destination qualification remains #1034; non-blocking waits remain #1036–#1039.
What to build
An explicitly authorized Lark responder answers native formal questions through card choices, explicit text submission or a reliably correlated reply, while Web shows the same authoritative answer.
Acceptance criteria
- Use the configured route and the native question owner; choices and free-text responses are both usable in the real DM.
- Verify answer capability, sender/account, original question receipt/reference, answer shape and live status; ambiguous multi-question replies require explicit selection.
- Web/IM races accept one answer; a failed or uncertain submission preserves the original ask until its owning service accepts and exposes repair rather than blind replay.
- Answers create no Tool Approval Rule and cannot approve a permission request by prose interpretation.
- Ordinary Lark clarification remains in the source conversation; direct DM text is disambiguated when several questions are open.
- Show answered, expired and cancelled states in the original card and Web; restart never revives an old native owner. Answer delivery alone is not non-blocking proof.
- Test through checked Provider and authenticated management/owning service boundaries; keep existing canonical persistence and no parallel content/decision authority.
- Retain real sanitized screenshots/step evidence and maintain the affected English/Chinese tutorial section; UI changes include matched baseline/changed light/dark evidence and no private secrets.
- Provide the exact-version runnable review path and focused behavioral coverage; pause for Human QA before expansion, without automatic merge/deployment.
Blocked by
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
- StatusShow more project fieldsDone
Activity
5 remaining items
DoodleBears commentedon Oct 7, 2026
Agent progress — platform limit fixed after safe recovery
codex/local/01a1131c-b268-7212-9ac8-d1c7bf9b6e28; state: active, awaiting a new guarded Human QA window.11310:max_length 2000exceeds the platform maximum 1000. No answer was accepted and the unknown delivery was not replayed.a9f6cbc7: form rendering and actual SDK custom-field validation both cap at 1000, with boundary regression assertions. Package verification passes; checked Provider 791 passed / 5 existing platform-related skips. The exact corrected runtime is privately installed and digest-verified while disabled.53a085e3records the real failed window, recovery and corrected limit in both guides and sanitized evidence. Keep both PRs draft: real Lark form submission and final-card qualification remain incomplete. No merge, deployment, published pin or scope expansion occurred.fix: gate IM question attachment on database readiness
DoodleBears commentedon Oct 7, 2026
Agent work update — candidate CI repaired
codex/local/01a1131c-b268-7212-9ac8-d1c7bf9b6e28; state: active, awaiting a fresh Human-authorized platform window.29dbcd0b. It gates database-backed IM question attachment on database readiness, retaining recovery diagnostics and file-backed surfaces, and updates the exhaustive bridge contract test.a9f6cbcare verified in the authenticated isolated Profile. Exact Provider package/runtime digests match; reception is disabled, with no active identity, approved pairing or management route. Production remains restored; the Human confirmed normal replies from Lark and Discord.feat(messaging): answer native questions from a paired Lark DM (#3314)
DoodleBears commentedon Nov 3, 2026
Delivered by #3314 with BotHarness/dsh-im#14. Lark form and /answer verified natively on 2026-11-03 (see docs/dev/verification/lark-1031-native-questions.md). Ships with Provider 4.32.0-botharness.26.