Repair Check Status and qualify normal chat responses in the native UI #34

New Issue

2026-10-02T12:13:16Z

KofTwentyTwo commented

2026-10-02 12:13:16 +00:00

(Migrated from github.com)

The owner reports that Check Status in Chat with Carl does not work. The reproduced screen retains a PENDING conversation choice while the answer area says UNKNOWN. Independent inspection of the exact owner request confirms backend UNKNOWN, no answer/artifact and current authorization. This is a reported UI/status defect; distinguish a stale label or broken refresh from a correctly fetched terminal UNKNOWN.

Trace the native Chat process and dock through their shared saved-request adapter. Check Status must GET the original request/selection, refresh visible status and message, and preserve current caller/audience authorization. It must never resubmit the question, start another inference, silently change selection, or claim a failed answer completed. Display meaningful safe failure/loading states; do not expose provider text or credentials.

Acceptance: controlled native/HTTP regression plus actual owner browser check on the matching installed package, with no extra chat POST; PENDING to terminal refresh, retained UNKNOWN, unavailable transport, private/shared selection and revoked-access denial. Connect this repair to the complete native owner-to-LLM-to-display acceptance, not only direct backend API checks. Implementation/investigation is isolated; the current running 563 package is unchanged.

Related: #28 and the household clerk/accountant capability issue. Private request IDs, cookies and diagnostics remain outside this public tracker.

The owner reports that Check Status in Chat with Carl does not work. The reproduced screen retains a PENDING conversation choice while the answer area says UNKNOWN. Independent inspection of the exact owner request confirms backend UNKNOWN, no answer/artifact and current authorization. This is a reported UI/status defect; distinguish a stale label or broken refresh from a correctly fetched terminal UNKNOWN. Trace the native Chat process and dock through their shared saved-request adapter. Check Status must GET the original request/selection, refresh visible status and message, and preserve current caller/audience authorization. It must never resubmit the question, start another inference, silently change selection, or claim a failed answer completed. Display meaningful safe failure/loading states; do not expose provider text or credentials. Acceptance: controlled native/HTTP regression plus actual owner browser check on the matching installed package, with no extra chat POST; PENDING to terminal refresh, retained UNKNOWN, unavailable transport, private/shared selection and revoked-access denial. Connect this repair to the complete native owner-to-LLM-to-display acceptance, not only direct backend API checks. Implementation/investigation is isolated; the current running 563 package is unchanged. Related: #28 and the household clerk/accountant capability issue. Private request IDs, cookies and diagnostics remain outside this public tracker.

KofTwentyTwo commented

2026-10-02 12:25:46 +00:00

(Migrated from github.com)

Owner-requested pause — October 2, 2026

Shared dock investigation reproduces two UI defects: unchanged UNKNOWN check has no visible acknowledgement and an older automatic PENDING response can replace newer COMPLETE. Actual disposable PostgreSQL/native baseline browser shows GET for the exact saved request returns HTTP200 UNKNOWN, then fails missing visible acknowledgement. The saved request is not resubmitted. This proves that tested status transport responds; it does not provide a completed model answer or qualify the owner's chat.

Isolated candidate:15 component tests and1985 full frontend tests/types/lint/audit/export pass. Candidate packaged browser GREEN, complete foundation gates, publication and actual owner-to-model-to-display acceptance are incomplete. Before adoption, add and qualify the identified regression that a superseded same-owner/current-generation401/403 must clear private state. Candidate is unpublished and not running. Worker is stopped; exact source guards, logs and findings are saved for takeover. Issue remains open.

Owner-requested pause — October 2, 2026 Shared dock investigation reproduces two UI defects: unchanged UNKNOWN check has no visible acknowledgement and an older automatic PENDING response can replace newer COMPLETE. Actual disposable PostgreSQL/native baseline browser shows GET for the exact saved request returns HTTP200 UNKNOWN, then fails missing visible acknowledgement. The saved request is not resubmitted. This proves that tested status transport responds; it does not provide a completed model answer or qualify the owner's chat. Isolated candidate:15 component tests and1985 full frontend tests/types/lint/audit/export pass. Candidate packaged browser GREEN, complete foundation gates, publication and actual owner-to-model-to-display acceptance are incomplete. Before adoption, add and qualify the identified regression that a superseded same-owner/current-generation401/403 must clear private state. Candidate is unpublished and not running. Worker is stopped; exact source guards, logs and findings are saved for takeover. Issue remains open.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/carl#34