Lark tracer: explicitly saved approval rules and creator-authorization revocation #1033

Activity

1. DoodleBears

   added this to the v1.2 milestone on Oct 6, 2026
2. DoodleBears

   added a parent issue on Oct 6, 2026

   • Hub: IM questions, approvals, feedback and non-blocking waits — Lark → Discord → Slack #1019
3. DoodleBears

   marked this as blocked on Oct 6, 2026

   • Lark tracer: paired DM Allow once and Reject with canonical execution receipts #1029
4. github-project-automation

   added this to Roadmapand IM Identities & Messagingon Oct 6, 2026
5. github-project-automation

   moved this to Todo in Roadmapon Oct 6, 2026
6. DoodleBears

   added

   ready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent

   area:fullstackEnd-to-end Host and Client implementationEnd-to-end Host and Client implementation

   feature:messagingMessaging module and external providersMessaging module and external providers

   scope:tracerHuman-testable implementation sliceHuman-testable implementation slice

   on Oct 6, 2026
7. DoodleBears

   marked this as blocking 2 issues on Oct 6, 2026

   • Discord tracer: explicit rule-saving controls with independent identity revocation #1044
   • Slack tracer: explicitly confirmed exact and scoped approval rules #1048
8. DoodleBears

   modified the milestones: v1.2, v1.3 on Oct 11, 2026
9. DoodleBears commented on Oct 11, 2026

   

   DoodleBears

   on Oct 11, 2026

   ContributorAuthor

   More actions

   Human-confirmed follow-up: approve this class of operation

   The Human accepted the current PR interaction and requested a follow-up from Lark Allow once / 批准本次操作 to Web-equivalent reusable approval rules. Reuse this existing tracer; do not create a duplicate or widen the pairing-card PR #1418.

   Refine this issue's acceptance with the current authorization model from #1406 / #1414:

   • Keep Allow once as the default. Offer Allow matching operations / 批准匹配的操作 as a distinct action, with a visible scope preview and explicit confirmation. Reuse the Web/native owning approval service and canonical Tool Approval Rule store.
   • Explain “this class” concretely: the first rule matches the same complete tool name and input, PersonaBot execution role and Workspace Grant scope. It is not a fuzzy natural-language similarity match, all future Shell commands, or all operations by this IM person. A broader supported all-opaque scope remains separately disclosed and separately confirmed, never a silently widened exact rule.
   • Rule creation requires current execution approval authority and a separate explicit save-rules capability. Extend the appropriate Role / authorization Group / person-exception controls and the shared effective resolver for this supported action; group membership and approve alone must not confer rule-saving authority. Preserve explicit Deny precedence and keep use/delegation separate where delegation is exposed.
   • Check current trusted actor, Bot, App Binding, native request/receipt, scope and authorization when confirming, including delayed controls. Record the exact creating external authorization and provenance. Creator revocation, a replaced Binding, or removal/Deny of required creator authority disables its rule for future matching approvals; re-pairing cannot resurrect it. Independent authority sources remain effective only if the current resolver permits them.
   • Web and IM show the same rule, scope and active/revoked status. Demonstrate creation, a real automatically approved exact match, a changed-input/scope mismatch requiring fresh approval, capability loss/Deny, revocation and restart. Replayed callbacks are idempotent; no additional rule or execution is created.
   • Begin with the qualified private Lark execution-approval route. Shared native execution approval destinations remain Lark tracer: management conversation destinations with per-actor question and approval checks #1034's separate qualification; public pairing cards from Lark tracer: delegated pairing review from group and private-DM cards #1414 do not expose private operation arguments or authorize native execution rule creation.

   No implementation claim is made by this clarification. Existing ownership, native dependency on #1029, first-tracer Human feedback, and Project #10 sequencing remain authoritative. #1029 is currently closed; this issue is currently Todo with no claim comments or open PR found during this check.
10. 17 remaining items

    Load more
11. DoodleBears

    added 6 commits that reference this issue on Oct 12, 2026

    Record real scoped-rule QA and current-head review evidence

    ...

    c069029

    Document qualified Lark scoped-rule workflow with real screenshots

    ...

    6390f40

    Align bilingual scoped-rule qualification evidence

    ...

    08e8eb1

    Keep scoped-rule release entries focused on observable behavior

    ...

    dbe952a

    Bind review explainer to final documentation head

    ...

    b103951

    Normalize review artifact line endings

    ...

    7669a39
12. DoodleBears commented on Oct 12, 2026

    

    DoodleBears

    on Oct 12, 2026

    Last edited by DoodleBears

    ContributorAuthor

    More actions

    Agent progress — qualified scoped-rule native QA

    Task: codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76; claim remains active on codex/1033-lark-saved-rules.

    • Current Host #1455 head dbe952ad7f7261eac377d36c3694574b1e8cddaa; Provider #24 head bc795b9cb576c411f0c94997e025b72a94c4f1fb. Native QA used Host fca0d383; later commits only update documentation/screenshots/ledger wording.
    • The Human accepted the all-opaque first slice before expansion. Actual QA1: preview/Back left zero rules; fresh separately disclosed Confirm ALL saved one rule and executed A; new changed input B auto-matched with independent native audit and no extra card; changed Grant scope C required approval and Reject prevented execution; original scope restored, rule revoked/restart, identical B input D still required approval and Reject prevented execution.
    • Final actual refreshed Lark cards: C/D rejected with no controls; old rule receipt shows fixed disabled text with no input/buttons. An update interrupted by the deliberate restart recorded unknown-outcome; explicit idempotent revoke refreshed the same known receipt without creating a rule or execution. This is not an automatic-recovery claim.
    • The first actual candidate request exposed an IM-only missing canonical DM refusal. It did not execute. The public owner/checked-Provider regression reproduced the failure, then passed after on-demand canonical DM creation through the existing Channel Store; no old message was replayed.
    • Current native sequence, runnable path and visual limits. PR bodies embed current base/after/preview/result/different-input/disabled captures; GitHub rendered all 17 Host and 11 Provider images. Bilingual public tutorials include real scoped-rule captures. Head-bound HTML is shared in PR comments and its public download is byte-verified.
    • 64 focused fix/approval/rule/store tests, Host typecheck/lint/full format/build and 476-page docs-content build passed; unchanged Provider has 86 passing related tests/build. Standards and Spec at the final heads have zero remaining findings. Current full verify passed. Preparation also passed at this exact head and does not publish.
    • Native Lark dark-theme capture remains unavailable because Lark ignored browser color-scheme changes; accepted Role-editor light/dark comparisons remain separate. Final HTML desktop/narrow visual inspection was interrupted by browser disconnection; navigation/title and public download were verified, but that responsive visual check is not claimed.
    • QA1 task receiver and temporary review-only server are stopped. No automatic merge, Provider promotion, publication or deployment. Lark tracer: explicitly saved approval rules and creator-authorization revocation #1033 and Project M3: Bot 模式 IA 与聊天外壳（列表/Section/DM/本地消息） #10 remain In Progress pending review/merge/delivery coordination; do not close the Hub or take another owner's task.

    Read-only next-task audit: #1046 has no assignee/claim/comments and native prerequisite #1029 is closed; #1041 is similarly unclaimed with #1029 closed. Recheck claims/PRs before claiming either. #1404 still explicitly retains one-time code scope; it is a design Hub, not a duplicate implementation ticket. No new coding claim or receiver window was taken.
13. DoodleBears

    added 2 commits that reference this issue on Oct 12, 2026

    Lark: add separately confirmed scoped approval-rule cards (#24)

    ...

    32d38b6

    Lark: save scoped tool rules with current reviewer authority (#1455)

    ...

    8392828
14. DoodleBears commented on Oct 12, 2026

    

    DoodleBears

    on Oct 12, 2026

    ContributorAuthor

    More actions

    Agent work outcome — completed source tracer

    • Agent: Codex
    • Task: codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76
    • State: completed for Lark tracer: explicitly saved approval rules and creator-authorization revocation #1033's qualified private Lark exact/all-opaque source tracer; Human explicitly authorized merge after acceptance and remaining native QA.
    • Host #1455 merged into main as 8392828804c71fa54ad802128526f481769adc01; Provider #24 merged into its existing codex/1111-inline-app-setup integration branch as 32d38b69a2bb8157f3f4baab3bc16ad13e238eea. Current reviewed Host head dbe952ad full verify/preparation passed; Provider 86 relevant tests/build passed. The merge preserves task provenance.
    • Exact and all-opaque first slices Human-accepted; remaining real scope/revoke/restart/final-card checks and public native sequence/screenshots are complete. The initial missing-DM refusal was reproduced and fixed through canonical Channel Store; old requests were not executed. The interrupted receipt update required an explicit idempotent refresh, as documented. Native dark-theme/HTML responsive inspection limits remain explicit in PR evidence.
    • QA1 task receiver stopped and this round's window released. No package publication, published Provider pin promotion, deployment, production takeover or unrelated owner changes. Provider packaging/install promotion stays with IM identities and messaging: provider coordination #48/Spec: single-install qualified IM Provider and resumable Lark onboarding #822/Create the app inside Bind app: Lark credentials and WeChat QR (Provider setup capability) #1111; source-tracer completion does not claim public-release delivery. Group destinations and questions stay with Lark tracer: management conversation destinations with per-actor question and approval checks #1034/Lark tracer: native Human questions answered from the paired DM #1031.
15. DoodleBears

    removed

    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs

    in-progressHeld by an agent session; see Claim comment for whoHeld by an agent session; see Claim comment for who

    on Oct 12, 2026
16. DoodleBears

    closed this as completedon Oct 12, 2026
17. github-project-automation

    moved this from In Progress to Done in IM Identities & Messagingon Oct 12, 2026
18. github-project-automation

    moved this from Todo to Done in Roadmapon Oct 12, 2026