/**
 * synap view
 *
 * Manage views on the pod.
 *
 * Usage:
 *   synap view create --type kanban --profile task --name "My Board" --workspace <id>
 *   synap view create --type bento --profile note --json
 *   synap view list [--workspace <id>]
 *
 * API:
 *   POST /api/hub/views  — CreateViewRequest: { userId, workspaceId, name, type, profileId, config, metadata }
 *   GET  /api/hub/views  — ListViewsQuery:    { userId, workspaceId, type, profileId }
 *
 * Note: the backend accepts `profileId` (not `profileSlug`). The CLI accepts
 * `--profile <slug>` for convenience and passes it as `profileId` — the backend
 * resolves it at the entity level or stores it as-is. Pass a UUID if you need
 * exact profile routing.
 */
export interface ViewCreateOpts {
    type: string;
    profile?: string;
    name?: string;
    workspace?: string;
    json?: boolean;
    podUrl?: string;
    apiKey?: string;
}
export interface ViewListOpts {
    workspace?: string;
    type?: string;
    json?: boolean;
    podUrl?: string;
    apiKey?: string;
}
export declare function viewCreate(opts: ViewCreateOpts): Promise<void>;
export declare function viewList(opts: ViewListOpts): Promise<void>;
export interface ViewArrangeOpts {
    file?: string;
    workspace?: string;
    json?: boolean;
    podUrl?: string;
    apiKey?: string;
}
/**
 * POST /api/hub/views/:viewId/arrange
 *
 * Replaces the widget arrangement for a bento-type view.
 * Payload: { userId, workspaceId?, widgets: BentoWidget[] }
 *
 * BentoWidget shape: { id, kind, x?, y?, w?, h?, config?, ...passthrough }
 *
 * Layout JSON can be provided via --file <path> or piped from stdin.
 * Expected format: an array of BentoWidget objects, OR
 *   { widgets: BentoWidget[] } wrapper — both are accepted.
 */
export declare function viewArrange(viewId: string, opts: ViewArrangeOpts): Promise<void>;