Skip to content

QQ tracer: independent source-file processing and original-group result files #1158

New issue
New issue
Closed
Closed
QQ tracer: independent source-file processing and original-group result files#1158
Labels
area:fullstackEnd-to-end Host and Client implementationfeature:messagingMessaging module and external providersready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice
Milestone
v1.3

Description

@DoodleBears
DoodleBears
opened on Oct 7, 2026

v1.3 release reconciliation — 2026-10-11

Target release: v1.3. The implementation/evidence recorded below was merged into the existing #1156 QQ feature branch, not main. Added native blocker #1156 for default-branch stack promotion and current-product qualification; preserve the fulfilled #1153 foundation and all existing owner/evidence records. Do not reimplement the accepted media slice or close it merely because the child PR was merged to a dependency branch. This is a release/integration dependency, not a new claim or authorization to merge.

Parent

QQ group chat specification #1149

What to build

Mention the Bot with a synthetic QQ group file, inspect the source file in the local Channel, let the Bot acquire and process an independent authorized working copy, and receive the resulting file from its own app in the same QQ group.

Reuse checked source-file contracts, canonical Attachment presentation, Workspace Grants and Tool Approval Rules. This slice proves actual file work and native result delivery, following existing Slack file-processing evidence without depending on image or voice implementation.

Acceptance criteria

  • A real file event retains trusted account/group/native-message association, source metadata and mention scope through the public checked intake. Credentials/private source URLs remain Provider-owned.
  • The linked Channel shows an authorized source file card with known type/size/name where available and usable download/open behavior through existing platform support. Human file inspection does not count as Bot Observation.
  • The Bot explicitly acquires the file through the checked source operation and processes an independent authorized working copy. Receiving a file alone neither executes it nor grants workspace writes; the received original remains unchanged.
  • Use a synthetic file with known input and expected transformation. The actual authorized tool/model path produces a distinct result whose bytes/content can be independently checked.
  • One checked native file reply from the owning QQ app reaches the original group. Independently inspect native association, original/result bytes and the resulting file, preserving receipt truth and unknown-send behavior.
  • Existing scope and lifecycle fences apply at acquisition, serving, tool access and sending. Expired, oversized, unsupported, cancelled or revoked sources are explicit failures without raw-URL or cross-app fallback.
  • Preserve canonical Attachment ownership and source metadata across replay/refresh/restart. Original and derived metadata are distinguishable and no QQ-specific file/credential authority is created.
  • Public-seam regression covers origin association, policy/authority, independent-copy processing, size/resource failures, cancellation/revocation and checked original-group result receipt. Existing Slack/Lark/Discord behavior remains qualified.
  • Perform a real QQ/Client/model-tool test with verifiable input/output content, original preservation and native result-file inspection. Record the exact qualified revisions and sanitized lifecycle evidence.
  • Provide required Client evidence, bilingual guide and ledger updates and checks. Submit reusable QQ file acquisition/output contracts to the maintained Provider fork and upstream.
  • If official QQ file reception/acquisition or result delivery is unavailable on the actual app, show the cause and keep this slice unfinished. Preview or attachment forwarding alone does not pass.

Blocked by

Reuse Slack file-processing #831 and the shared media specification #1020. Image and voice slices are not blockers.

Activity

  1. DoodleBears
    added this to the v1.2 milestone on Oct 7, 2026
  2. DoodleBears
    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 7, 2026
  3. DoodleBears
    added a parent issue on Oct 7, 2026
  4. DoodleBears
    marked this as blocked on Oct 7, 2026
  5. DoodleBears
    added this to IM Identities & Messagingon Oct 7, 2026

  6. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a117bf-865d-72d1-a9c6-88658c59f844 (not a DSH Session)
    • Issue scope: QQ group source-file capability qualification, canonical authorized working-copy processing and checked original-group result files; platform restrictions remain explicit failures, not URL/image fallbacks.
    • Branch: codex/1158-qq-files
    • Started: 2026-10-08 10:25 UTC
    • State: active

    Build on the current checked media seams from #1157 while preserving one product issue → one PR. Current SDK file APIs do not establish this application's group-file permission; native input and output must be qualified independently before readiness.

  7. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026

  8. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Task: codex/local/01a117bf-865d-72d1-a9c6-88658c59f844

    Implementation checkpoint, still active: product draft #1193, maintained Provider dac1bfd1 and modern upstream draft dsh-im #332. Spec and Standards reviews are complete; known-size/type metadata fixes and shared Provider acquisition fixes are included. Product Linux CI passes (381 files, 5 skipped), as do 184 upstream QQ and 42 public Delivery/adapter tests. Maintained Provider full Windows suite has 40 failures not baseline-qualified; no complete Provider success is claimed.

    The local Host is running the digest-verified candidate and the real Bot has replied that it is ready to save/read/process/import and return a distinct result file. Synthetic CSV fixture is prepared; no fresh native QQ file Source Event exists yet. Real input association, bounded private download host, app upload/send permission, original-group result download and Client light/dark/keyboard/video remain Human/runtime qualification steps. Adjacent/quoted messages are not admitted as file association. No issue is closed and no PR is merged.

  9. DoodleBears
    added 4 commits that reference this issue on Oct 8, 2026

    feat(qq): pin explicit file-quote source qualification

    38f17ca

    fix(qq): expose bounded file refusal diagnostics

    5dc51af

    fix(qq): expose bounded file refusal diagnostics

    a274455

    fix(qq): pin bounded native file refusal diagnostics

    9b169f8

  10. 11 remaining items

  11. DoodleBears
    added 2 commits that reference this issue on Oct 8, 2026

    fix(qq): pin native file quote metadata compatibility

    99fa619

    fix(qq): pin structural native file quote checks

    9a9c9d3

  12. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    QQ file round-trip qualified; visual acceptance remains partial

    • Agent task: codex/local/01a117bf-865d-72d1-a9c6-88658c59f844; QQ tracer: independent source-file processing and original-group result files #1158 remains active and PR #1193 remains Draft.
    • Real QQ acceptance on 2026-10-08: explicit file-card quote + current @mention → one canonical Source, one Inbox Admission, one Channel placement → native read of an independently saved CSV → distinct total.csv → one own-app original-group file reply with native receipt. The original hash stayed unchanged. Human confirmed receipt, download and correct total_quantity / 5 contents.
    • Client keyboard Enter download also passed; browser bytes match the original 29-byte CSV, authenticated HTTP is 200 with forced download/no-store/nosniff. This adds no Bot admission or send authority.
    • Maintained Provider code remains pinned at 6d24d1f and runtime-digest verified on DSH RC1; documentation heads are maintained 9c03fe7, modern 7fff01b, product 68cda4f0. No modern live-runtime or direct-carrier proof is claimed.
    • Actual light/dark screenshots and captured-state video are published. Viewports differ slightly; continuous keyboard/download and native QQ result-file recording remain incomplete because Chrome repeatedly stopped responding. The state video is not continuous-recording acceptance.
    • 176 maintained QQ and 6 product-pin tests pass; modern PR #332 passes 187 QQ + 42 delivery tests. Spec and Standards review passed. Maintained full Windows suite: 3,683 pass / 38 fail / 7 skip, failures not baseline-qualified. Product code-head Linux CI passed 381 test files, lint/format/typecheck/build/docs and release preparation; current-head verification and release preparation both pass. Local format and bilingual ledgers pass.

    Remaining: matched-viewport/continuous recording evidence and the existing PR stack/upstream qualification. No further QQ resend or authorization is needed for the completed CSV proof.

  13. DoodleBears
    added a commit that references this issue on Oct 8, 2026

    docs(qq): record qualified quoted CSV round trip

    68cda4f

  14. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work outcome

    • Agent: Codex
    • Task: codex/local/01a117bf-865d-72d1-a9c6-88658c59f844
    • State: completed for this implementation slice; the Human approved merge with the disclosed capture limits.
    • PR #1193 merged at f96332d5890ad25863f39bd951511e05e6c55484 into codex/1156-qq-own-identities on 2026-10-08. Promotion of the QQ stack to main remains separate.
    • Real quoted-CSV intake, canonical Source/Inbox/Channel, independent-copy native reading, unchanged original, distinct original-group result file/native receipt, Human result download/content check and Client keyboard download passed. Current-head product verification and release preparation passed; both review axes passed.
    • Evidence limits remain explicit: slightly different before/after viewports and a screenshot-state walkthrough rather than continuous recording. Maintained Windows suite failures remain unqualified against baseline. The maintained-runtime acceptance does not qualify every app, direct-file carriers or modern upstream Host.
    • Upstream dsh-im PR #332 remains open; it was not included in the product merge authorization.
    • Next slice: QQ tracer: incoming voice playback and understanding with original-group text answers #1159, incoming voice playback and actual understanding with own-app text reply; no outgoing voice.
  15. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
  16. DoodleBears
    modified the milestones: v1.2, v1.3 on Oct 11, 2026
  17. github-project-automation
    added this to Roadmapon Oct 11, 2026
  18. github-project-automation
    moved this to Todo in Roadmapon Oct 11, 2026
  19. DoodleBears
    marked this as blocked on Oct 11, 2026

  20. DoodleBears commented on Oct 13, 2026

    @DoodleBears
    DoodleBears
    on Oct 13, 2026
    ContributorAuthor

    Agent work outcome — accepted delivery merged

    • Agent: Codex
    • Task: codex/local/01a1342d-5ce4-7872-9f9e-492a9caee393 (not a DSH Session)
    • State: completed for delivery/acceptance and default-branch promotion. Earlier implementation outcomes and their contributors remain part of the record.
    • Product #1505 merged into main at b5285b610393df2531be6c386d15656bb45ca947. Reviewed head 41c3a1c7 passed full Linux verify and package preparation.
    • Maintained Provider #26 merged at b283be11 into its declared dependency branch, not the default branch; no Provider package/release or production cutover is claimed.
    • Human acceptance decision: native own Echo is deferred, not passed. No own-text-echo capability is advertised. Tencent contract inquiry #8 remains open.
    • Evidence and exact revision boundaries: fresh K qualifies recovered runtime 2edb56d5 / Provider 1eee207c / SDK1.0.4 / DSH RC2. The merge does not retroactively qualify the later main composition. Earlier capture/Windows limits remain disclosed.

    The already accepted file implementation (#1193) is now promoted to main. Fresh quoted source CSV is independently read and processed; the distinct total-k.csv has only total_quantity and 42, downloaded/opened and confirmed by the Human. Original bytes remain unchanged and authenticated Client keyboard download passes. Earlier resource-unavailable lookup remains recorded.

  21. DoodleBears
    closed this as completedon Oct 13, 2026
  22. github-project-automation
    moved this from Todo to Done in Roadmapon Oct 13, 2026
  23. github-project-automation
    moved this from Todo to Done in IM Identities & Messagingon Oct 13, 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

    area:fullstackEnd-to-end Host and Client implementationfeature:messagingMessaging module and external providersready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions