mirror of
https://github.com/siteboon/claudecodeui.git
synced 2026-07-09 07:25:43 +08:00
* fix: don't overlap thinking banner over conversation * feat: support message queue and add attention indicator * fix(shell): use c to copy for claude * fix: strip timestamp tags from cursor * fix: select project when loading session from direct URL * feat: support attached images for all providers * feat(opencode): support permission options * fix: resolve source control and chat UX bugs - make staging real in the git panel: new /stage and /unstage endpoints, /status now reports the actual index via porcelain -z (handles renames, conflicts, and paths with spaces), and Stage/Unstage All run real git commands instead of toggling client-side state - add branch search to the header dropdown and Branches tab - persist the chosen permission mode per provider so a brand-new chat keeps it once the session id arrives, instead of reverting to default - replace cmdk's fuzzy model search with strict token matching so "chatgpt" no longer surfaces unrelated models - unit tests for the git status parser * feat(git): commit graph in history view and cross-spawn everywhere - render a VSCode-style commit graph in the source control history: lane-assignment algorithm, SVG strip with colored rails, merge and branch curves, commit dots, and branch/tag badges per commit - /commits returns parents and ref decorations across all branches (--branches --remotes --tags --topo-order) using unit-separator fields so pipes in commit subjects can't break parsing - collect stats via a single --shortstat pass instead of one `git show --stat` call per commit; raise the history limit to 50 - replace child_process spawn with cross-spawn in all runtimes, routes, and services: it resolves .cmd shims and PATHEXT on Windows (fixing taskmaster's npx invocations) and delegates to native spawn elsewhere, removing the per-file win32 ternaries - unit tests for the log parser and lane assignment * fix: remove gemini support since google discontinued it * fix: address code review findings - validate chat image attachments server-side: only files inside the ~/.cloudcli/assets upload store may reach provider file reads - harden asset serving with nosniff and attachment disposition for SVGs to prevent stored XSS - show the timestamp on image-only user messages - serialize git stage/unstage calls and defer the status re-sync so rapid toggles can't interleave or flicker - use a literal hex fallback for commit ref badges (alpha suffix on a var() string produced invalid CSS) - stop binding a URL session to a guening project instead - add the missing attentionRequiredIndicator key to all sidebar locales - clean up dangling conjunctions left the de/ru/tr/ja/zh-CN/zh-TW READMEs * fix: address code scanning findings - enforce a second image trust boundary in the provider builders: buildClaudeUserContent/buildCodexInputItems only accept files inside the upload store or the run's working directory (CodeQL path injection) - drop an always-true selectedProject check in handleSubmit - remove the unused resume option from spawnCursor * fix: use CodeQL-recognized containment check for image reads Replace the path.relative guard in isPathInsideDirectory with the resolve + startsWith(root + sep) idiom so the path-injection barrier is visible to code scanning; behavior is unchanged. * fix(security): canonicalize Claude image attachment reads Resolve image attachment paths with realpath before reading so symlinks inside allowed roots cannot escape to arbitrary files. Preserve support for symlinked project/upload roots and add focused coverage for both cases. * fix: show agent subtask * fix(sessions): title app-created sessions from the first user message App-created sessions (started by sending a message from cloudcli) were titled with placeholder names — "Untitled Codex Session" from the disk indexer and, briefly, "New session" from the empty canonical upsert — before a later sync finally settled on the right text, causing the sidebar title to flicker. - Codex/OpenCode synchronizers now title app-created sessions (distinct app id mapped to a provider id) from the first user message, while sessions found purely by indexing keep their existing setup. Claude keeps its AI-generated titles; Cursor already used the first message. - Decode OpenCode's JSON-string-literal prompts so titles no longer surface wrapped in quotes; hoist unwrapJsonStringLiteral into shared/utils since it's now used by both the reader and synchronizer. - Guard the sidebar upsert merge so an empty summary can never blank out a title that is already set. - Add codex/opencode synchronizer tests for the app-created vs indexed naming paths. * fix(chat): make message queuing reliable across sessions and turn boundaries Queued messages had four related defects: - A queued message flashed and then vanished at flush time: concurrent transcript refreshes (the `complete` handler racing the watcher-triggered update) could resolve out of order, letting a stale response overwrite newer server messages after the optimistic row was pruned. Session slots now carry a monotonic fetch ticket and discard stale fetch/refresh/ fetchMore responses. - Switching sessions flushed the previous session's queued draft into the newly viewed one (sending it with the wrong provider's settings, e.g. a Claude model into a Codex session). The composer flush is now scoped to its session, and a draft restored into an idle session sends after a short grace period so a live-run ack can cancel it. - The thinking banner never appeared for a queued turn: the chat handler's session-keyed completeRun safety net could fire after a queued message had already started the session's next run, emitting a spurious `complete` that killed it. The safety net is now scoped to its own run via completeRunIfCurrent (with a regression test). - Queued messages only sent while their session was being viewed. Drafts now persist their send options (model, effort, permissions) at queue time, and a new app-level useQueuedMessageAutoSend hook dispatches a non-viewed session's queued message as soon as its run completes, using the storage key as the claim ticket to prevent double sends.
583 lines
17 KiB
TypeScript
583 lines
17 KiB
TypeScript
import type { IncomingMessage } from 'node:http';
|
|
|
|
//----------------- HTTP RESPONSE SHAPES ------------
|
|
/**
|
|
* Canonical success envelope used by backend APIs that return a structured payload.
|
|
*
|
|
* Use this for route handlers that need a stable `success/data` shape so frontend
|
|
* consumers can parse responses consistently across endpoints.
|
|
*/
|
|
export type ApiSuccessShape<TData = unknown> = {
|
|
success: true;
|
|
data: TData;
|
|
};
|
|
|
|
/**
|
|
* Generic plain-object record used when parsing loosely typed JSON payloads.
|
|
*
|
|
* Use this only after runtime shape checks, not as a replacement for validated
|
|
* domain models.
|
|
*/
|
|
export type AnyRecord = Record<string, any>;
|
|
|
|
// ---------------------------
|
|
//----------------- WEBSOCKET TRANSPORT TYPES ------------
|
|
/**
|
|
* Minimal websocket client contract used by backend broadcaster services.
|
|
*
|
|
* Any transport object added to `connectedClients` must implement these two
|
|
* members so shared services can safely send JSON strings and check whether the
|
|
* socket is still open before broadcasting.
|
|
*/
|
|
export type RealtimeClientConnection = {
|
|
readyState: number;
|
|
send(data: string): void;
|
|
};
|
|
|
|
/**
|
|
* Authenticated user payload attached to websocket upgrade requests.
|
|
*
|
|
* Platform and OSS auth flows currently use either `id` or `userId`; both are
|
|
* represented here so websocket handlers can resolve a stable writer user id.
|
|
*/
|
|
export type AuthenticatedWebSocketUser = {
|
|
id?: string | number;
|
|
userId?: string | number;
|
|
username?: string;
|
|
[key: string]: unknown;
|
|
};
|
|
|
|
/**
|
|
* HTTP upgrade request shape after websocket authentication succeeds.
|
|
*
|
|
* `verifyClient` populates `request.user` with the authenticated payload, and
|
|
* downstream websocket handlers rely on this extended request type.
|
|
*/
|
|
export type AuthenticatedWebSocketRequest = IncomingMessage & {
|
|
user?: AuthenticatedWebSocketUser;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- PROVIDER MESSAGE MODEL ------------
|
|
/**
|
|
* Providers supported by the unified server runtime.
|
|
*
|
|
* Use this as the source of truth whenever a function or payload needs to identify
|
|
* a specific LLM integration.
|
|
*/
|
|
export type LLMProvider = 'claude' | 'codex' | 'cursor' | 'opencode';
|
|
|
|
/**
|
|
* One selectable model row in a provider model catalog.
|
|
*/
|
|
export type ProviderModelOption = {
|
|
value: string;
|
|
label: string;
|
|
description?: string;
|
|
effort?: {
|
|
default?: string;
|
|
values: {
|
|
value: string;
|
|
description?: string;
|
|
}[];
|
|
};
|
|
};
|
|
|
|
/**
|
|
* Provider model catalog returned by `GET /api/providers/:provider/models`.
|
|
*/
|
|
export type ProviderModelsDefinition = {
|
|
OPTIONS: ProviderModelOption[];
|
|
DEFAULT: string;
|
|
};
|
|
|
|
/**
|
|
* Cache metadata returned alongside one provider model catalog.
|
|
*
|
|
* `updatedAt` is when the current cached snapshot was last refreshed from the
|
|
* provider itself. `expiresAt` is the backend cache expiry timestamp, and
|
|
* `source` tells callers whether the current response came from in-memory cache,
|
|
* persisted disk cache, or a fresh provider fetch.
|
|
*/
|
|
export type ProviderModelsCacheInfo = {
|
|
updatedAt: string;
|
|
expiresAt: string;
|
|
source: 'memory' | 'disk' | 'fresh';
|
|
};
|
|
|
|
/**
|
|
* Full provider model lookup result returned by the backend service layer.
|
|
*
|
|
* Use this shape when a caller needs both the selectable model catalog and the
|
|
* cache metadata that explains how current the catalog is.
|
|
*/
|
|
export type ProviderModelsResult = {
|
|
models: ProviderModelsDefinition;
|
|
cache: ProviderModelsCacheInfo;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- PROVIDER ACTIVE MODEL TYPES ------------
|
|
/**
|
|
* Provider-neutral result for the model that is actively driving a session or
|
|
* provider runtime at the time of lookup.
|
|
*
|
|
* `model` must always be populated. Provider adapters should use the
|
|
* provider-specific lookup method requested by the caller, and only fall back
|
|
* to the provider catalog `DEFAULT` value when the active model cannot be read.
|
|
*/
|
|
export type ProviderCurrentActiveModel = {
|
|
model: string;
|
|
};
|
|
|
|
/**
|
|
* Input payload used when one session needs to use a different model on its
|
|
* next resumed turn.
|
|
*
|
|
* This is a backend-owned session override, not a claim that the provider has
|
|
* already switched the currently running session in-place. Provider adapters
|
|
* persist this request so the next CLI/SDK resume can inject the chosen model
|
|
* using the provider-specific mechanism supported by that runtime.
|
|
*/
|
|
export type ProviderChangeActiveModelInput = {
|
|
sessionId: string;
|
|
model: string;
|
|
};
|
|
|
|
/**
|
|
* Provider-neutral session model-change state.
|
|
*
|
|
* `supported` indicates whether the provider adapter supports the app's
|
|
* session-scoped resume override flow. `changed` is the persisted boolean the
|
|
* resume layer checks before forcing a model on the next resumed turn. When
|
|
* `changed` is `false`, `model` is `null` and the runtime should use the
|
|
* normal request/default model selection path.
|
|
*/
|
|
export type ProviderSessionActiveModelChange = {
|
|
provider: LLMProvider;
|
|
sessionId: string;
|
|
supported: boolean;
|
|
changed: boolean;
|
|
model: string | null;
|
|
};
|
|
|
|
/**
|
|
* Message/event variants emitted by provider adapters and normalized transports.
|
|
*
|
|
* Keep this union in sync with event kinds produced by provider session adapters.
|
|
*/
|
|
export type MessageKind =
|
|
| 'text'
|
|
| 'tool_use'
|
|
| 'tool_result'
|
|
| 'thinking'
|
|
| 'stream_delta'
|
|
| 'stream_end'
|
|
| 'error'
|
|
| 'complete'
|
|
| 'status'
|
|
| 'permission_request'
|
|
| 'permission_cancelled'
|
|
| 'session_created'
|
|
| 'interactive_prompt'
|
|
| 'task_notification';
|
|
|
|
/**
|
|
* Event kinds added by the chat gateway layer on top of provider message kinds.
|
|
*
|
|
* These are app-level realtime events (subscription acks, sidebar deltas,
|
|
* project loading progress, protocol failures) that are not produced by any
|
|
* provider adapter. Together with `MessageKind` they form the complete set of
|
|
* `kind` values a websocket client can receive, so the frontend only ever
|
|
* needs one kind-based switch.
|
|
*/
|
|
export type GatewayEventKind =
|
|
| 'chat_subscribed'
|
|
| 'session_upserted'
|
|
| 'loading_progress'
|
|
| 'protocol_error';
|
|
|
|
/**
|
|
* Complete set of `kind` values emitted to websocket clients.
|
|
*
|
|
* Every server-to-client websocket frame carries a `kind` from this union.
|
|
* Provider runtimes emit `MessageKind` values; gateway services emit
|
|
* `GatewayEventKind` values.
|
|
*/
|
|
export type ServerEventKind = MessageKind | GatewayEventKind;
|
|
|
|
/**
|
|
* Provider-neutral message envelope used in REST responses and realtime channels.
|
|
*
|
|
* Every provider-specific message must be converted into this shape before being
|
|
* emitted outside provider-specific modules.
|
|
*/
|
|
export type NormalizedMessage = {
|
|
id: string;
|
|
sessionId: string;
|
|
timestamp: string;
|
|
provider: LLMProvider;
|
|
kind: MessageKind;
|
|
/**
|
|
* Monotonic per-run sequence number assigned by the chat run registry when a
|
|
* live event is forwarded to the websocket. History messages loaded over
|
|
* REST do not carry it. Clients use it with `chat.subscribe` to replay only
|
|
* the live events they missed across websocket reconnects.
|
|
*/
|
|
seq?: number;
|
|
role?: 'user' | 'assistant';
|
|
content?: string;
|
|
/**
|
|
* Optional display-oriented metadata used by providers that need to expose
|
|
* richer transcript artifacts without introducing a brand-new message kind.
|
|
*
|
|
* Current Claude usage:
|
|
* - local slash commands expose parsed command fields
|
|
* - compact summaries are flagged so the UI can treat them differently later
|
|
*/
|
|
displayText?: string;
|
|
commandName?: string;
|
|
commandMessage?: string;
|
|
commandArgs?: string;
|
|
isLocalCommand?: boolean;
|
|
isLocalCommandStdout?: boolean;
|
|
isCompactSummary?: boolean;
|
|
images?: unknown;
|
|
toolName?: string;
|
|
toolInput?: unknown;
|
|
toolId?: string;
|
|
toolResult?: {
|
|
content?: string;
|
|
isError?: boolean;
|
|
toolUseResult?: unknown;
|
|
};
|
|
isError?: boolean;
|
|
text?: string;
|
|
tokens?: number;
|
|
canInterrupt?: boolean;
|
|
requestId?: string;
|
|
input?: unknown;
|
|
context?: unknown;
|
|
reason?: string;
|
|
newSessionId?: string;
|
|
status?: string;
|
|
summary?: string;
|
|
tokenBudget?: unknown;
|
|
subagentTools?: unknown;
|
|
toolUseResult?: unknown;
|
|
sequence?: number;
|
|
rowid?: number;
|
|
[key: string]: unknown;
|
|
};
|
|
|
|
/**
|
|
* Shared options used to fetch historical provider messages.
|
|
*
|
|
* Consumers should pass provider-specific lookup hints (`projectPath`) only
|
|
* when the selected provider requires them.
|
|
*
|
|
* `providerSessionId` is the provider-native session id from the sessions
|
|
* index (transcript file name / provider database key). Provider adapters
|
|
* must use it — never the app-facing session id they were called with — when
|
|
* matching transcript rows on disk, because app-created sessions use an
|
|
* app-allocated id that the provider has never seen.
|
|
*/
|
|
export type FetchHistoryOptions = {
|
|
projectPath?: string;
|
|
limit?: number | null;
|
|
offset?: number;
|
|
providerSessionId?: string;
|
|
};
|
|
|
|
/**
|
|
* Standardized response payload returned from provider history readers.
|
|
*
|
|
* Use this as the contract for APIs that return paginated conversation history.
|
|
*/
|
|
export type FetchHistoryResult = {
|
|
messages: NormalizedMessage[];
|
|
total: number;
|
|
hasMore: boolean;
|
|
offset: number;
|
|
limit: number | null;
|
|
tokenUsage?: unknown;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- PROVIDER SKILL TYPES ------------
|
|
/**
|
|
* Scope where a provider skill definition was discovered.
|
|
*
|
|
* Provider skill adapters should use this to describe the origin of each
|
|
* skill markdown file without leaking provider-specific folder names into route
|
|
* contracts. `repo` is used for Codex repository lookup locations, while
|
|
* `project` is used for providers that treat workspace-local skills as project
|
|
* scoped.
|
|
*/
|
|
export type ProviderSkillScope = 'user' | 'project' | 'plugin' | 'repo' | 'admin' | 'system';
|
|
|
|
/**
|
|
* Shared input accepted by provider skill listing operations.
|
|
*
|
|
* Routes pass `workspacePath` when a caller wants project/repository skills for
|
|
* a specific folder. Providers should fall back to the backend process cwd when
|
|
* this option is omitted.
|
|
*/
|
|
export type ProviderSkillListOptions = {
|
|
workspacePath?: string;
|
|
};
|
|
|
|
/**
|
|
* One supporting file bundled with an uploaded provider skill.
|
|
*
|
|
* `relativePath` is resolved below the installed skill directory and must never
|
|
* be absolute or contain traversal segments. Text files may use `utf8`; binary
|
|
* scripts and assets should use `base64` so JSON transport does not corrupt
|
|
* their bytes.
|
|
*/
|
|
export type ProviderSkillCreateFile = {
|
|
relativePath: string;
|
|
content: string;
|
|
encoding: 'utf8' | 'base64';
|
|
};
|
|
|
|
/**
|
|
* One skill markdown payload submitted for provider-managed installation.
|
|
*
|
|
* `content` is the raw markdown body that will be written to `SKILL.md`.
|
|
* `directoryName` lets callers control the target folder name explicitly when
|
|
* they want stable filesystem paths that differ from the markdown front matter
|
|
* `name` field. `fileName` is optional upload metadata used only as a final
|
|
* fallback when no directory name or front matter name is present. `files`
|
|
* carries scripts, references, and other files from a complete skill folder.
|
|
*/
|
|
export type ProviderSkillCreateEntry = {
|
|
content: string;
|
|
directoryName?: string;
|
|
fileName?: string;
|
|
files?: ProviderSkillCreateFile[];
|
|
};
|
|
|
|
/**
|
|
* Shared input accepted by provider skill creation operations.
|
|
*
|
|
* The service layer batches multiple skill definitions in one request. Each
|
|
* entry can contain only markdown or a complete skill folder.
|
|
*/
|
|
export type ProviderSkillCreateInput = {
|
|
entries: ProviderSkillCreateEntry[];
|
|
};
|
|
|
|
export type ProviderSkillRemoveInput = {
|
|
directoryName: string;
|
|
};
|
|
|
|
/**
|
|
* Normalized skill record returned by provider skill adapters.
|
|
*
|
|
* The `command` value is the exact invocation text the selected provider expects
|
|
* for this skill. Claude plugin skills use a namespaced command such as
|
|
* `/plugin-name:skill-name`, while Codex skills use the `$skill-name` form.
|
|
* `sourcePath` points to the skill markdown file that produced the record so
|
|
* callers can distinguish duplicate skill names across scopes.
|
|
*/
|
|
export type ProviderSkill = {
|
|
provider: LLMProvider;
|
|
name: string;
|
|
description: string;
|
|
command: string;
|
|
scope: ProviderSkillScope;
|
|
sourcePath: string;
|
|
pluginName?: string;
|
|
pluginId?: string;
|
|
};
|
|
|
|
/**
|
|
* Internal source descriptor consumed by shared provider skill discovery logic.
|
|
*
|
|
* Concrete provider adapters build these records from their native lookup rules.
|
|
* The shared skills provider then scans `rootDir` for child skill markdown files
|
|
* and uses `commandForSkill` or `commandPrefix` to produce the provider-specific
|
|
* invocation command. Set `recursive` only when a provider stores skills under
|
|
* arbitrary nested folders below the source root.
|
|
*/
|
|
export type ProviderSkillSource = {
|
|
scope: ProviderSkillScope;
|
|
rootDir: string;
|
|
recursive?: boolean;
|
|
commandPrefix?: '/' | '$';
|
|
commandForSkill?: (skillName: string) => string;
|
|
pluginName?: string;
|
|
pluginId?: string;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- SHARED ERROR TYPES ------------
|
|
/**
|
|
* Optional metadata used when constructing application-level errors.
|
|
*
|
|
* `statusCode` should reflect the HTTP response status, while `code` identifies
|
|
* the stable machine-readable error category.
|
|
*/
|
|
export type AppErrorOptions = {
|
|
code?: string;
|
|
statusCode?: number;
|
|
details?: unknown;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- MCP TYPES ------------
|
|
/**
|
|
* Scope where an MCP server definition is stored and resolved.
|
|
*
|
|
* `user` is global for a user account, `local` is provider-local, and `project`
|
|
* is tied to a specific project path.
|
|
*/
|
|
export type McpScope = 'user' | 'local' | 'project';
|
|
|
|
/**
|
|
* Transport protocol used by an MCP server definition.
|
|
*/
|
|
export type McpTransport = 'stdio' | 'http' | 'sse';
|
|
|
|
/**
|
|
* Normalized MCP server model exposed to frontend and route handlers.
|
|
*
|
|
* Provider adapters should map provider-native config to this structure before
|
|
* returning results.
|
|
*/
|
|
export type ProviderMcpServer = {
|
|
provider: LLMProvider;
|
|
name: string;
|
|
scope: McpScope;
|
|
transport: McpTransport;
|
|
command?: string;
|
|
args?: string[];
|
|
env?: Record<string, string>;
|
|
cwd?: string;
|
|
url?: string;
|
|
headers?: Record<string, string>;
|
|
envVars?: string[];
|
|
bearerTokenEnvVar?: string;
|
|
envHttpHeaders?: Record<string, string>;
|
|
};
|
|
|
|
/**
|
|
* Payload for create/update MCP server operations.
|
|
*
|
|
* Routes and services should accept this type, validate it, and then persist it
|
|
* through provider-specific MCP repositories.
|
|
*/
|
|
export type UpsertProviderMcpServerInput = {
|
|
name: string;
|
|
scope?: McpScope;
|
|
transport: McpTransport;
|
|
workspacePath?: string;
|
|
command?: string;
|
|
args?: string[];
|
|
env?: Record<string, string>;
|
|
cwd?: string;
|
|
url?: string;
|
|
headers?: Record<string, string>;
|
|
envVars?: string[];
|
|
bearerTokenEnvVar?: string;
|
|
envHttpHeaders?: Record<string, string>;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- PROVIDER AUTH TYPES ------------
|
|
/**
|
|
* Authentication status result returned by provider health checks.
|
|
*
|
|
* This shape is consumed by settings/status endpoints to report installation and
|
|
* credential state for each provider.
|
|
*/
|
|
export type ProviderAuthStatus = {
|
|
installed: boolean;
|
|
provider: LLMProvider;
|
|
authenticated: boolean;
|
|
email: string | null;
|
|
method: string | null;
|
|
error?: string;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- SHARED DATABASE CREDENTIAL TYPES ------------
|
|
/**
|
|
* Safe credential view returned by credential listing APIs.
|
|
*
|
|
* This intentionally excludes the raw credential secret while still exposing
|
|
* metadata needed for UI rendering and management operations.
|
|
*/
|
|
export type CredentialPublicRow = {
|
|
id: number;
|
|
credential_name: string;
|
|
credential_type: string;
|
|
description: string | null;
|
|
created_at: string;
|
|
is_active: number;
|
|
};
|
|
|
|
/**
|
|
* Result returned after creating a credential record.
|
|
*
|
|
* Use this return shape when callers need the created id and display metadata,
|
|
* but must never receive the stored secret value.
|
|
*/
|
|
export type CreateCredentialResult = {
|
|
id: number | bigint;
|
|
credentialName: string;
|
|
credentialType: string;
|
|
};
|
|
|
|
// ---------------------------
|
|
//----------------- PROJECT PERSISTENCE TYPES ------------
|
|
/**
|
|
* Canonical project row shape returned by the projects repository.
|
|
*
|
|
* Use this type whenever backend services need to pass around one database
|
|
* project record without leaking raw SQL row typing across modules.
|
|
*/
|
|
export type ProjectRepositoryRow = {
|
|
project_id: string;
|
|
project_path: string;
|
|
custom_project_name: string | null;
|
|
isStarred: number;
|
|
isArchived: number;
|
|
};
|
|
|
|
/**
|
|
* Result category returned by `projectsDb.createProjectPath`.
|
|
*
|
|
* `created` means a fresh row was inserted, `reactivated_archived` means an
|
|
* existing archived path was accepted and updated, and `active_conflict` means
|
|
* an already-active path blocked project creation.
|
|
*/
|
|
export type CreateProjectPathOutcome =
|
|
| 'created'
|
|
| 'reactivated_archived'
|
|
| 'active_conflict';
|
|
|
|
/**
|
|
* Structured result returned by project-path upsert operations.
|
|
*
|
|
* Services should use this result to decide whether a request succeeded,
|
|
* should return a conflict, or needs follow-up retrieval of row metadata.
|
|
*/
|
|
export type CreateProjectPathResult = {
|
|
outcome: CreateProjectPathOutcome;
|
|
project: ProjectRepositoryRow | null;
|
|
};
|
|
|
|
/**
|
|
* Validation result for user-supplied workspace/project paths.
|
|
*
|
|
* `resolvedPath` is present only when validation succeeds. `error` is present
|
|
* only when validation fails and is suitable for user-facing diagnostics.
|
|
*/
|
|
export type WorkspacePathValidationResult = {
|
|
valid: boolean;
|
|
resolvedPath?: string;
|
|
error?: string;
|
|
};
|