Repository navigation
QQ tracer: independent Bots answer in one group through their own app identities #1156
Description
Accepted delivery scope — 2026-10-13
Human decision authorizes merge and closure of the delivered scope with native own Echo explicitly deferred. All native evidence remains qualified only at its recorded revision; closing this ticket does not claim Echo support, final-head live qualification or completion of QQ proactive/ordinary participation.
Parent
QQ group chat specification #1149
What to build
Bind two independent official QQ apps to two PersonaBots, map their verified group conversations to one local Group Channel, and mention each in the same real QQ group. Each answer must use the responding Bot's own app identity, including when reading a shared source.
This is QQ qualification and mapping through the existing multi-app/shared-source model, not another account ownership redesign. It can be demonstrated with mentions-only intake and does not require ordinary collection first.
Acceptance criteria
- The existing Bind app and app/conversation lists support the two distinct owning Bots and native app identities. Each app has one owner; a Bot may still bind several apps per platform under the shared model.
- Both official apps are actually authorized in the same dedicated QQ QA group. Independently authenticate and explicitly map each app-scoped conversation; matching names, text or OpenIDs never automatically merge them.
- Through the actual Client, sync both verified sources into the selected local Group Channel with useful app/sender attribution and no duplicated content authority or implicit Human DM placement.
- A real mention of each app reaches the correct Bot's Inbox/Orchestrator and returns an independently inspected reply from that app in the original group.
- Reading shared Channel content never lends another Bot's app. A responder with no authorized own-app conversation cannot send; two qualified own apps representing the destination produce the shared explicit ambiguity refusal rather than a guessed identity.
- Deferred by Human acceptance decision: native same-App own Echo correlation/positive loop qualification remains unavailable; receipts and foreign callbacks are not own Echo. Generic correlation/fence regressions pass and no own-text-echo capability is advertised. Decision; official contract inquiry. Native cross-app identity evidence remains distinct.
- Blocking, unbinding or archiving one owner fences that owner's effects without transferring its identity to the other Bot or erasing accepted source history. Restart retains valid independent ownership.
- Focused public-seam tests cover trusted mention attribution, ownership/ambiguity, cross-app identity isolation, shared read/send fences, echo loops and lifecycle changes. Do not require QQ tracer: opted-in ordinary group observation and intentional participation #1155's ordinary-message policy to pass these cases.
- Real QA includes distinguishable native own-app replies and independently inspected receipts plus Client source mapping. Record the sanitized evidence and actual qualified revisions.
- Provide required Client evidence, bilingual guide/ledger changes, focused checks and any reusable maintained-fork/upstream Provider contribution. This slice adds no QQ private messages or auto group-joining feature.
Blocked by
- QQ tracer: manage conversations, Channel sync and truthful reconnect history #1153 — the qualified text path and explicit local source placement/conversation controls.
Activity
DoodleBears commentedon Oct 8, 2026
Agent work claim
codex/local/01a117bf-865d-72d1-a9c6-88658c59f844(not a DSH Session)codex/1156-qq-own-identitiesPrerequisite #1153 is delivered by ready PR #1168 at
40868a6e44293adf3446b683fe32705c84808315, with real QQ/Client acceptance and full Linux CI. This issue remains one separate product PR; implementation reuses the existing multi-app/shared-source owners. #1154 waits for shared #1115 and is not duplicated here.DoodleBears commentedon Oct 8, 2026
Agent work progress
codex/local/01a117bf-865d-72d1-a9c6-88658c59f84465390020, v1.2 and Project M3: Bot 模式 IA 与聊天外壳（列表/Section/DM/本地消息） #10.43×47 → 2021and47×53 → 2491. Each independently inspected record has one Source, one handled owning Inbox admission, one placement and one original-group own-app accepted receipt, one send attempt; restart retains them.own-text-echo; actual receipts are not Echo proof. No receive-all permission or ordinary-message admission has been enabled.37e97bdeoncodex/1156-qq-echo-observation. It will observe only already-delivered native candidates before filtering, with bounded sanitized diagnostics, and will not claim or enable Echo capability without native proof.fix(qq): restore mapped reception after transient startup unavailability
DoodleBears commentedon Oct 8, 2026
Agent progress — final restart qualification
Task:
codex/local/01a117bf-865d-72d1-a9c6-88658c59f844· branchcodex/1156-qq-own-identities· state: active, partial acceptance.Draft PR #1172 now contains final head
3b2be95, stacked on #1168. The Human confirmed the first post-fix, post-restart replies61×67 → 4087and67×71 → 4757. Each was independently audited as exactly one canonical Source Event, one handled owning Bot Inbox admission, one shared Channel placement and one accepted own-app original-group reply, with one send attempt. Both group receivers restored automatically; existing history remains present.Final-head Linux verification and package preparation pass. Final Standards and Spec review has no actionable code findings. Windows full-suite success is not claimed.
Actual Client evidence now includes light/dark final captures, source-detail upper portions and a clearly labeled captured-state MP4 slideshow. Return, Escape and focus restoration pass in both themes. The original comparable light pair renders in GitHub; matched dark/source-detail baseline pairs remain pending.
Native Echo remains an explicit acceptance gap. The installed bounded observer and its logger exporter were verified using known lifecycle records, but this actual window yielded zero native bot-message candidates. This is limited observation, not proof of platform-wide absence. No Echo capability, receive-all or ordinary-message admission was enabled. Upstream diagnostic contribution #328 is attached to this task and remains Draft; the maintained QA artifact pin is
71fa2a2.No PR has been merged and this issue is not complete. The remaining native platform gate must not be replaced with HTTP receipt or synthetic fixture evidence.
Merge main into QQ multi-app and media slices
fix(qq): keep own-app mentions under full group reception
72 remaining items
Merge current main while preserving QQ audio and mention qualification
Integrate current Client stylesheet ownership and composer recovery
Document current QQ audio and username chip evidence with version bou…
Add current owning App lists and bilingual guide captures
DoodleBears commentedon Oct 12, 2026
Continuation — current Client, audio/mention alignment and public delivery
Task
codex/local/01a130f6-e6e0-7093-a412-886b04293da1remains active. The Human's native own-Echo gate is retained; #1156 remains open.Running code: product
6d44dd549ce9cd087c98cf81bc7b923342cb1ee4, including main9a01a3eff00f8d7e472da5034359a34ca8a6691d, Provider1eee207c0c23fc98aa26e329f753c1de8b910aff, SDK1.0.4 / DSH0.2.0-rc.2. The checked Provider has418 runtime files / SHA256155ddb125e790abe45ba6cc0e2d56d27f6e4a669f8ed087b61afd249b320fe6e. A fresh generation83 consistent snapshot passed integrity check before the exact owned Host restart. Both independent bindings, active mappings and previous14/15 accepted Outbox facts survived. Both fresh local DMs received genuine replies.The Human-requested UI refinements now use the existing components: QQ voice uses
MessageAudio; native mention names/IDs feed the existing inertExternalMessageTextchips. Unknown names remain literal; native IDs are hover details, without changing original text, App ownership or reply authority. Each App's full native marker reply was confirmed at product28d34471/ Provider1eee207c. The actual current Client6d separately shows both correct chips with matching32-character native IDs.Current Client checks:
T3 automation detached after explicitly reporting no Host through
preview_open; the current checks used an independent headless Chrome with the same authenticated owned Profile. It started no QQ receiver and changed no App permission. Literal public crops remove private author names/native conversation IDs. The old literal mention Before would expose a private scoped ID, so the visual exception and runnable fallback fixture are recorded explicitly.Current evidence record · product PR1505 · Provider PR26 · browser-verified HTML review aid.
Delivery2edb56d5 only adds public docs/assets after runtime/code6d. The checked0952790f rebuild has identical five runtime artifacts; the subsequent2ed commit changes no package/script/build input. Complete Linux CI2edb56d5 and prerelease preparation pass. Filtered Windows Astro completes494pages; full Windows suite and the Windows slides-inclusive docs chain are not claimed green. Provider source0670ea33 independently passes Linux build, all3,801tests and package verification, with portable artifacts committed1eee207c. Both review axes pass. The13 public PNGs and generated HTML return200/exact bytes; the review aid renders four panels on desktop/narrow without overflow. Actual GitHub PR rendering verifies the audio Before/After and two chip images. Docs-site publication/npm release/production deployment remain separate.
Remaining: fresh6d original-group reply confirmation, current native image/file qualification and genuine same-App native own Echo. Core Echo facts remain0 and QQ does not declare
own-text-echo. Historical lifecycle A–E and their exact revisions remain intact. Receipts, peer observations, UI screenshots, fixtures or PRs do not substitute for native own Echo; no closure or sibling closure is performed.Original QA1/QA2 receivers remain guarded stopped and the pair guard remains held by this continuation. The current pair remains active; no credential-store copy, production switch, whole-machine restart or resource release occurred.
DoodleBears commentedon Oct 13, 2026
Agent work claim — Human-directed native acceptance continuation
codex/local/01a1342d-5ce4-7872-9f9e-492a9caee393(not a DSH Session)codex/1156-native-acceptance-continuationThe Human explicitly requested continuation of the latest record. This supersedes task
codex/local/01a130f6-e6e0-7093-a412-886b04293da1for this bounded continuation; prior claims, accepted revisions and evidence remain history. Product PR #1505 and maintained Provider PR #26 remain draft. Read-only preflight finds no listener for the previously recorded paired Host, so that historical running-state claim is not carried forward. This task adopts the existing exclusive paired receiver guard before recovery; original receivers must remain stopped and original restoration claims are retained. No App permission change, duplicate receiver, credential-store copy, production cutover, release or sibling closure is included.Merge current main into QQ acceptance continuation
Record fresh QQ replies and verified native media results
DoodleBears commentedon Oct 13, 2026
Fresh native K qualification and official contract question
codex/local/01a1342d-5ce4-7872-9f9e-492a9caee393· continuation claim · state: active, awaiting a supported native own-Echo condition/contract.41c3a1c7507a8c13f73d5d9e0c33418566d0916b; code integrationf08c35c9includes main snapshote68b04b2. Conflicts are resolved. Complete Linux verification and prerelease preparation both pass at that exact head: 530 test files / 4,471 tests pass, with 7 files / 13 tests skipped. This is preparation, not release.2edb56d539c960b5d5491b5d305c474011401ba7, Provider1eee207c0c23fc98aa26e329f753c1de8b910aff, SDK1.0.4 / DSH0.2.0-rc.2; 418 Provider runtime files / SHA256155ddb125e790abe45ba6cc0e2d56d27f6e4a669f8ed087b61afd249b320fe6e. Its five checked runtime artifacts match code6d44dd54. The later main integration has not been deployed or qualified as this native run.The previously recorded Host was no longer running. Recovery verified both original receivers stopped, adopted the existing pair guard without changing original restoration claims, and made a new generation83 consistent SQLite snapshot with successful integrity check. Both owning bindings, active shared mappings and all14/15 accepted Outbox facts survived. Both fresh actual Client DMs and both K original-group replies succeeded; the Human confirms each complete marker. Each requested App has one handled owning Inbox, available Source, shared placement and own-App Outbox/native receipt. Foreign-marker Admissions are zero; the two additional K Attention items are independently tied to the local Human DMs.
QA1's fresh image and explicit quoted-CSV path also pass. The actual Qwen3.8 Flash request/header and native
read_imageimage block precede the correctly namedBLUE_68241.pngresult. Native CSVread/write, import and own-App native file send produce the distinct18-bytetotal-k.csvwithtotal_quantity / 42. The Human confirms the returned blue square / BLUE /68241 and downloads/verifies the exact CSV contents. The original9,372-byte QQ PNG and33-byte CSV hashes match the actual Client downloads and independent working copies. The initial wrong attachment lookup'sresource-unavailablerefusal remains recorded; the model reads the correct reference and completes one send.The media checkpoint has exactly two QA1 Admissions/Outbox facts and zero new QA2 Admissions/Outbox. Actual Client image enlargement/Escape/focus return and keyboard original-file download pass. The dedicated QA Grant/write authorization is revoked; QA1's original model preset is restored and a new real DM plus native request header verify DeepSeek V4 Flash. Final readback keeps both Apps connected, each with one active mapping, accepted Outbox totals17/16 and Core Echo0.
The frozen K text boundary has three group frames per App with complete WebSocket→Gateway→callback correspondence, matching20 received/decoded frames per App including heartbeats and zero refusal/suppression/capture failure. Each Bot author is scoped foreign; no self-author or same-App receipt ID/reference match exists. A separate media boundary observes QA1's five Human frames / five callbacks and two send receipts with no Bot frame; QA2 has seven frames / seven callbacks, including two scoped foreign Bot frames. Both media transport counters and phases match, without missing group frames or capture failure. This is bounded evidence, not encrypted-wire capture, a universal platform claim or an own-Echo loop qualification.
With the Human's explicit authorization, the sanitized official Tencent SDK contract question #8 is now published. It asks for supported same-App reflection, self-author fields and receipt/event correlation. No response or new supported condition is inferred yet. The Human's retained native own-Echo gate remains unchanged.
Public evidence record · version-bound review aid · Provider PR #26.
All four new PNGs and the HTML return200/exact committed bytes; all four PNGs render at their correct dimensions in GitHub's PR body. The public HTML shows four panels on1280×800 and390×844, without overflow after layout settles. Earlier screenshots keep their original versions. Local93 integration +13 helper tests, typecheck/lint/format/ledgers/build pass; filtered Windows Astro builds498pages. The first helper-test invocation used the wrong runner; the corrected Vitest invocation passes all13. No full Windows suite or Windows slides-inclusive chain is claimed green. Manual Standards/Spec integration review found no new actionable issue; earlier Provider reviews retain their exact revisions.
#1156 and both PRs remain open/draft. Native own Echo is still not implemented/advertised. The merged composition needs its own final runtime qualification when a distinguishing native Echo condition is available. No sibling closure, SDK upgrade, App permission change, credential-store copy, npm release, production switch or receiver-resource release occurred. Original receivers remain guarded stopped; the recovered exclusive pair stays active under this continuation.
DoodleBears commentedon Oct 13, 2026
Human acceptance decision — own Echo deferred
Agent task:
codex/local/01a1342d-5ce4-7872-9f9e-492a9caee393.On 2026-10-13 the Human explicitly authorized merging the delivered QQ work, closing the related delivered tickets and continuing to the next ticket despite the unavailable native own-Echo condition. This supersedes the previous retained merge gate; it does not change the observations or establish an Echo capability.
Accepted scope: independent owning Apps, explicit shared source mapping and identity fences, genuine original-group replies, image understanding/result delivery, independent CSV processing/result delivery, and the previously qualified incoming voice/transcript/text-answer slice. The Human confirmed both complete K markers, the blue image with BLUE/code 68241, and downloaded
total-k.csvcontaining onlytotal_quantityand42.Native same-App own Echo remains unqualified and deferred. Native receipts and foreign-App callbacks are not own Echo. No
own-text-echocapability is advertised. Tencent SDK inquiry #8 stays open to establish a supported contract before future implementation/qualification.Delivery: product #1505, reviewed head
41c3a1c7507a8c13f73d5d9e0c33418566d0916b, with passing Linux verification/preparation; maintained Provider #26, head1eee207c0c23fc98aa26e329f753c1de8b910aff, into its declared dependency branch. The latter does not promote the entire Provider stack to its default branch or publish a package.Version-bound evidence remains unchanged: fresh native K evidence qualifies recovered product
2edb56d5, not the later undeployed main integration; historical voice understanding retains its own revision. Earlier Windows/capture limits remain documented. No release or production cutover is claimed.#1154/#1155 and QQ hub #1149 remain open because their proactive/ordinary-participation work is unfinished.
DoodleBears commentedon Oct 13, 2026
Agent work outcome — accepted delivery merged
codex/local/01a1342d-5ce4-7872-9f9e-492a9caee393(not a DSH Session)b5285b610393df2531be6c386d15656bb45ca947. Reviewed head41c3a1c7passed full Linux verify and package preparation.b283be11into its declared dependency branch, not the default branch; no Provider package/release or production cutover is claimed.2edb56d5/ Provider1eee207c/ SDK1.0.4 / DSH RC2. The merge does not retroactively qualify the later main composition. Earlier capture/Windows limits remain disclosed.Both complete own-App K replies are Human-confirmed; explicit source mapping, current owner attribution, independent identity fences, preserved restart facts and actual Client DMs are documented. The previous own-Echo merge gate is superseded only by the linked Human decision. Earlier claims are concluded for this accepted ticket scope; future Echo work remains deferred under the official inquiry. QQ hub #1149 and proactive/ordinary #1154/#1155 remain open.