Skip to content

Lark tracer: native Human questions answered from the paired DM #1031

Closed

Description

@DoodleBears

Parent

#1019

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

Activity

  1. added this to the v1.2 milestone on Oct 6, 2026
  2. added
    ready-for-agentFully specified, ready for an AFK agent
    area:fullstackEnd-to-end Host and Client implementation
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Oct 6, 2026
  3. 5 remaining items

  4. DoodleBears commented on Oct 7, 2026

    @DoodleBears
    ContributorAuthor

    Agent progress — platform limit fixed after safe recovery

    • Task: codex/local/01a1131c-b268-7212-9ac8-d1c7bf9b6e28; state: active, awaiting a new guarded Human QA window.
    • The first freshly authorized Lark tracer: native Human questions answered from the paired DM #1031 window verified the Human's new actual SDK pairing and granted Answer only. The original native two-question request committed, but Lark rejected card creation with 11310: max_length 2000 exceeds the platform maximum 1000. No answer was accepted and the unknown delivery was not replayed.
    • QA route cleared, pairing revoked, identity unbound, Provider disabled and exact local receiver stopped before production restoration. The verified outage upper bound was 471 seconds, within the ten-minute limit. Restart shows the original request expired with zero answers. The Human confirmed both production Lark and Discord normal.
    • Provider #14 now contains fix 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.
    • BotHarness #1104 at 53a085e3 records 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.
  5. DoodleBears commented on Oct 7, 2026

    @DoodleBears
    ContributorAuthor

    Agent work update — candidate CI repaired

    • Task: codex/local/01a1131c-b268-7212-9ac8-d1c7bf9b6e28; state: active, awaiting a fresh Human-authorized platform window.
    • Root draft #1104 now includes 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.
    • Complete Linux CI passed: 3066 tests passed / 9 skipped, lint, format, typecheck and build. Native Windows additionally passed all 35 relevant plugin/recovery/native-question/Lark tests and the static checks and build.
    • The rebuilt root candidate and Provider draft #14 at a9f6cbc are 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.
    • The first platform attempt remains a failure record, not form qualification. A second window is still awaiting explicit Human authorization. Keep both PRs draft; no qualified pin update, publication, production deployment or scope expansion.
  6. added and removed
    ready-for-agentFully specified, ready for an AFK agent
    on Oct 8, 2026
  7. moved this from Todo to In Progress in IM Identities & Messagingon Oct 8, 2026
  8. modified the milestones: v1.2, v1.3 on Oct 11, 2026
  9. modified the milestones: v1.3, v2.0 on Oct 24, 2026
  10. DoodleBears commented on Nov 3, 2026

    @DoodleBears
    ContributorAuthor

    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.

  11. moved this from In Progress to Done in Roadmapon Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsarea:fullstackEnd-to-end Host and Client implementationfeature:messagingMessaging module and external providersready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions