Files
agent-radar 2ed3415fb7
Publish Claude Code Binaries / Stage and publish binaries (push) Canceled after 0s
Publish Tutti App Runtime / Build darwin-arm64 (push) Canceled after 0s
Publish Tutti App Runtime / Build darwin-amd64 (push) Canceled after 0s
Publish Tutti App Runtime / Build linux-amd64 (push) Canceled after 0s
Publish Tutti App Runtime / Build windows-amd64 (push) Canceled after 0s
Sync Tutti Agent Skills / sync (push) Canceled after 0s
Windows Agent Adapters / Test Windows agent adapters (push) Canceled after 0s
Windows Daemon Adapters / Test Windows daemon adapters (push) Canceled after 0s
Publish Tutti App Runtime / Publish runtime catalog (push) Canceled after 0s
源码快照 @ 2026-09-01 (source-only, 剔除非源码素材)
2026-09-01 20:17:27 +08:00

64 lines
2.2 KiB
TypeScript

/**
* Wire contract for the answer submitted back to an interactive `ask-user`
* prompt. This payload crosses the renderer → daemon boundary (it rides
* `submitInteractive({ action: "submit", payload })`), so its shape is a
* cross-language contract, not an internal detail.
*
* Consumers that MUST stay in sync with this shape:
* - daemon (Go) standard ACP adapter — preserves this canonical payload for
* local projection and translates selected labels back to provider ACP
* permission option IDs when the provider bridges questions that way.
* - daemon (Go) codex app-server adapter — `appServerUserInputAnswers` reshapes
* `answersByQuestionId` into codex's `requestUserInput` response.
*
* Field semantics:
* - `answersByQuestionId` is the canonical, machine-readable answer: question id
* → the chosen option label(s) / free text. This is what providers consume.
* - `answers` is a flat, human-readable display list (one entry per answered
* question, multi-select joined). Never the source of truth for routing.
*
* Always build this with {@link buildAskUserAnswerPayload} so producers can't
* drift on field names or which field is authoritative.
*/
export interface InteractiveAnswerPayload {
answers: string[];
answersByQuestionId: Record<string, string | string[]>;
}
export function readOwnAnswer<T>(
values: Record<string, T>,
questionID: string,
fallback: T
): T {
return Object.prototype.hasOwnProperty.call(values, questionID)
? values[questionID]!
: fallback;
}
export function writeOwnAnswer<T>(
values: Record<string, T>,
questionID: string,
value: T
): void {
Object.defineProperty(values, questionID, {
configurable: true,
enumerable: true,
value,
writable: true
});
}
/**
* Builds the canonical interactive answer payload from the per-question answers.
* `answers` is derived from `answersByQuestionId` (multi-select values joined)
* so the two fields can never disagree.
*/
export function buildAskUserAnswerPayload(
answersByQuestionId: Record<string, string | string[]>
): InteractiveAnswerPayload {
const answers = Object.values(answersByQuestionId).map((value) =>
Array.isArray(value) ? value.join(", ") : value
);
return { answers, answersByQuestionId };
}