@orchestraworks/cli 0.5.5 → 0.5.7

package/templates/bug-fix/main.ts

@@ -68,8 +68,13 @@ const github = new Connection(factory, "github", {
   install: { permissions: ["contents:write"] },
 });
 
+// The edge adds the gateway key on the gateway's host. The runtime image's placeholder key rides x-api-key, and
+// the gateway refuses two keys that disagree, so the recipe removes it.
+const gatewayHost = required("ORCHESTRA_FDK_MODEL_GATEWAY_HOST");
 const gatewayKey = new Secret(factory, "model-gateway-key", {
   value: SecretValue.fromGatewayKey(new GatewayKey(factory, "model-gateway", { displayName: "__FACTORY_NAME__ bug fixing" })),
+  hosts: [gatewayHost],
+  injection: { headers: [{ name: "Authorization", value: "Bearer ${secret}" }], removeHeaders: ["x-api-key"] },
 });
 // init-if: anthropic
 
@@ -119,7 +124,7 @@ const runtime = new Environment(factory, "runtime", {
   // Open to start with. Deny the hosts of the team's hosted data here, and tighten once runs succeed.
   egress: EgressPolicy.allowAll()
     .applyPreset(github.egressPolicy())
-    .routeModelsViaGateway({ key: gatewayKey, host: required("ORCHESTRA_FDK_MODEL_GATEWAY_HOST") }),
+    .routeModelsViaGateway({ key: gatewayKey, host: gatewayHost }),
   // Docker for the services the codebase runs in containers. Remove both lines when nothing runs in Docker.
   setup: readFile("image/setup.sh"),
   disks: [{ mountPath: "/var/lib/docker", size: "50G" }],

package/templates/engineering-team/README.md

@@ -5,7 +5,7 @@ use, and the pipelines their work moves through. `orchestra fdk apply` makes the
 
 ## What it declares
 
-One program, in the organization with no project. Everything it declares sits in the organization, so items
+One program, with every row in the Shared team. Everything it declares sits in Shared, so items
 in any of its pipelines can be assigned to any of its agents.
 
 | Path | What it holds |
@@ -54,7 +54,8 @@ bundle fixes the commit the work starts from, so the author and the reviewer of
    default branch.
 2. It uploads the bundle as a File, and writes `Code bundle: <file id>` in the item.
 3. The Engineer Agent downloads it with `orchestra files get-content`, clones from it, and answers with a patch
-   uploaded as another File.
+   uploaded as another File. When a person adds a code host connection that lets it push, it pushes a branch
+   made from the bundle's commit and opens a pull request instead.
 
 Their instructions in `agents/` carry these steps.
 
@@ -65,12 +66,14 @@ the bug, and names the cause. For a feature, it first turns the item into accept
 design in two or three sentences that follow the codebase's own patterns. When it cannot reproduce the bug,
 or the acceptance is unclear, it hands the item back with its questions. Then, for both, it writes the tests
 first, and runs the whole test suite, the typecheck and the lint of every package it touched, as CI does.
-For complex or UI work, it also runs the app, signs in as a test user, and attaches screenshots or logs as
-Files. Next it assigns the item to another Engineer Agent, on the other harness, for an adversarial review
-that sees only the item, the patch and the evidence. The reviewer applies the patch to a fresh clone of
-the bundle each round. Every turn starts by reading who holds the item, and an agent that does not hold it
+For complex or UI work, it also runs the app, signs in as a test user, and takes screenshots and
+recordings. It keeps one progress page on the item, as the `progress-report` skill says. Next it publishes
+the evidence on a version of that page, and assigns the item to another Engineer Agent, on the other
+harness, for an adversarial review that sees only the item, the patch or pull request, and that page version.
+The reviewer applies the patch to a fresh clone of the bundle each round, or reviews the pull request. Every turn starts by reading who holds the item, and an agent that does not hold it
 ends the turn, so the notice the platform sends when an item is assigned away starts no work. The engineer
-fixes each confirmed P1 and P2 finding, in at most two rounds, and reports the evidence on the item.
+fixes each confirmed P1 and P2 finding, in at most two rounds, and publishes its report as an artifact
+page, in the shape the `artifacts` skill gives a bug or feature report.
 `agents/engineer-agent.md` carries these steps. To check UI work in a browser, turn on the Chromium block in `lib/setup.sh`.
 
 ## Inputs

package/templates/engineering-team/agents/engineer-agent.md

@@ -13,6 +13,10 @@ At the start of every turn, run `orchestra work-items get <item id> --output jso
 item is not assigned to `<self>`, end the turn with one short line that names who holds it, and do nothing
 else.
 
+Follow the `progress-report` and `artifacts` skills for your progress page, your machine's preview link and
+end time, your recordings and your report. Only the author of a change publishes the progress page; a
+reviewer does not.
+
 This machine can reach any host. The code for an item comes as a git bundle, a file the Manager Agent
 uploaded, so you and your reviewer start from the same commit. Its id is on the item's `Code bundle:` line.
 
@@ -30,6 +34,8 @@ How you do a work item:
    - For a feature, turn the item into acceptance tests first: one test for each thing the item says the
      feature must do. Then state the design in two or three sentences, following the patterns the codebase
      already uses for the same kind of work.
+   - When the bug or the feature shows in the UI, take the before screenshots and the before recording now,
+     before you change any code, as the `artifacts` skill's "Recordings" section says.
    - When the item's text is narrower than what the code accepts today, keep the existing behavior and say so
      in your report, or ask before narrowing it. Check the current behavior first, through the old code path
      and its tests.
@@ -42,35 +48,48 @@ How you do a work item:
    lint, the way the repository's CI runs them. Then check that the tests from step 3 now pass. Keep the
    output.
 6. Check it by hand when the work is complex or involves the UI. Run the app, sign in as a test user, and do
-   the real operation the item describes. Take screenshots or keep the logs, and upload each one as a File:
-   `orchestra files create --file <path> --filename <name> --output json`.
-7. Write your whole change as one patch, new files and any commits included, against the commit the bundle
-   holds: `git -C /work/code add -A`, then
+   the real operation the item describes. Start the app's server again after the change, and publish the
+   preview, as the `artifacts` skill's "Your machine" section says. Then take the after screenshots and the
+   after recording, as its "Recordings" section says. Never write the test user's password on a page or in a
+   comment.
+7. Save your work. By default you cannot push: this factory sets up no code host connection and no token
+   for you. Write your whole change as one patch, new files and any commits included, against the commit
+   the bundle holds: `git -C /work/code add -A`, then
    `git -C /work/code diff --cached --binary origin/work > /work/change.patch`. Upload it with
    `orchestra files create --file /work/change.patch --filename change.patch --output json`.
+   When a person has added a code host connection that lets you push, push and open a pull request in
+   place of the patch. Make a branch from the bundle's commit, named for the item's slug. Commit your
+   change to it, push it to the team's repository, and open a pull request to its default branch. When
+   the push is refused, upload the patch as above.
 8. Ask for an adversarial review, as "How you ask for a review" says, before you hand the item back.
-9. When the review is done, report the evidence on the item: the cause or the design, the tests from step 3
-   failing before and passing after, the full test runs, the check by hand with its File ids, the patch's
-   File id, and each review finding with what you did about it. Then move the item to its review stage:
-   In review in Bugs and Features, Waiting on requester in Support.
+9. When the review is done, report the evidence on the item: publish the report through the `artifacts`
+   skill, as its "The report" section says. Post the report's link on the item, as that skill says. Then
+   move the item to its review stage: In review in Bugs and Features, Waiting on requester in Support.
 
 How you ask for a review:
 
-A fresh conversation reviews your change before you hand the item back. It sees only the item, your patch
-and your evidence.
+A fresh conversation reviews your change before you hand the item back. It sees only the item, your pull
+request or patch, and your progress page.
 
-1. Upload the patch and each evidence File.
+1. Save your work as step 7 says. Then publish a version of your progress page that holds the evidence:
+   the tests from step 3 failing before and passing after, the full test runs, and the check by hand with
+   its screenshots and recordings.
 2. Add a comment to the item with `orchestra work-items create-activity <item id> --text <comment>`. Start it
-   with `Review request, round <N>, from <self> to <reviewer>`, then give the patch File id, the evidence File ids and the
-   commands you ran.
+   with `Review request, round <N>, from <self> to <reviewer>`. Then give the progress page's link and its
+   version number, the pull request link or the patch File id, and the commands you ran.
 3. Assign the item to `<reviewer>`. Assigning it starts that agent's conversation. Your conversation ends
    here: stop, and do not move the item.
 
 When the item is assigned to you and its last comment is a review request that ends `to <self>`, you are
 the reviewer:
 
-- Read only the item's description, the review request, the patch and the evidence Files. Do not read the
-  conversation that wrote the change.
+- Read only the item's description, the review request, the pull request or the patch, and the progress
+  page version the request names. Read that version with
+  `orchestra artifacts get-version-content <page slug> <version> --output-file /work/progress.html`. Do not
+  read the conversation that wrote the change, and publish no version of its progress page. Run no
+  assessment, and publish nothing: your review comment is the only thing you post.
+- With a pull request, review its diff, and run the tests yourself on a fresh clone of its branch in
+  `/work/review`. With a patch, do as the next bullet says.
 - Review in `/work/review`, never in `/work/code`, and start from a fresh clone each round, because an
   earlier round's patch may still be there. Run `rm -rf /work/review`. Download the bundle with
   `orchestra files get-content <file id> --output-file /work/review.bundle`, then run
@@ -93,6 +112,9 @@ the reviewer:
 
 When the item is assigned to you and its last comment is a review of your change:
 
+- With a pull request, your change is on your pushed branch. Keep working on that branch, and clone it
+  again into `/work/code` when that folder is gone. Skip the next bullet, which is for a patch, and push each
+  fix to the same branch.
 - Your conversation resumes here, so `/work/code` may still hold the change you submitted. Download your last
   patch File with `orchestra files get-content <patch file id> --output-file /work/last.patch`. Then compare:
   `git -C /work/code add -A`, then `git -C /work/code diff --cached --binary origin/work > /work/now.patch`,
@@ -103,7 +125,7 @@ When the item is assigned to you and its last comment is a review of your change
     Then apply your last patch with `git -C /work/code apply /work/last.patch`.
 - Check each finding against the code it cites. Fix each P1 and P2 finding you confirm. For a P1 or P2 you
   do not confirm, say why. Leave the P3 findings.
-- After a fix, run the full tests again and upload a new patch. A fix after round 1 gets a round 2 review.
+- After a fix, run the full tests again, then push the fix or upload a new patch. A fix after round 1 gets a round 2 review.
   Never ask for a round 3: after round 2, report as step 9 says, and list each finding still open.
 - When the review confirms no P1 or P2 finding, report as step 9 says.
 

package/templates/engineering-team/lib/environment.ts

@@ -2,13 +2,22 @@
 //
 // An environment declared in code keeps only what it declares: `orchestra fdk apply` removes every rule and setting
 // added by hand or by the platform at create. So the model gateway rule is declared here, on every environment,
-// and nothing else is assumed.
+// and nothing else is assumed. A key names the hosts the edge adds it on; a rule only opens or closes hosts.
 //
 // Following the orchestra-fdk skill's environment reference, an agent edits the section marked WHAT THE CODE
 // NEEDS once it has found how the team's code is installed, tested and started.
 
 import { readFileSync } from "node:fs";
-import { EgressPolicy, Environment, GatewayKey, Secret, SecretValue, type Factory, type ISecret } from "@orchestraworks/cli";
+import {
+  DEFAULT_MODEL_GATEWAY_HOST,
+  EgressPolicy,
+  Environment,
+  GatewayKey,
+  Secret,
+  SecretValue,
+  type Factory,
+  type ISecret,
+} from "@orchestraworks/cli";
 
 /** A size is the machine: 2, 16 or 32 CPU, with 2 GB of memory per CPU. */
 export type Size = "sm" | "md" | "lg";
@@ -50,6 +59,9 @@ export function declareKeys(factory: Factory): Keys {
     name: "Model gateway key",
     description: "Added to model calls at the network edge. The agents never see it.",
     value: SecretValue.fromGatewayKey(gatewayKey),
+    hosts: [DEFAULT_MODEL_GATEWAY_HOST],
+    // The runtime image's placeholder key rides x-api-key, and the gateway refuses two keys that disagree.
+    injection: { headers: [{ name: "Authorization", value: "Bearer ${secret}" }], removeHeaders: ["x-api-key"] },
   });
   return { modelGateway };
 }
@@ -78,7 +90,7 @@ export function declareEnvironment(
       { mountPath: "/work", size: WORK_DISK_SIZE },
     ],
     ingress: PORTS.map((port) => ({ ...port, access: "authenticated" as const })),
-    // Open to every host, with the model gateway key added on the gateway's host.
+    // Open to every host. The model gateway key names the gateway's host, so the edge adds it there.
     egress: EgressPolicy.allowAll().routeModelsViaGateway({ key: keys.modelGateway }),
   });
 }

package/templates/engineering-team/main.ts

@@ -1,4 +1,4 @@
-// The whole factory, in the organization with no project: the four agents, their machines, the model gateway
+// The whole factory, all of it in the Shared team. It holds the four agents, their machines, the model gateway
 // key, and the Bugs, Features and Support pipelines. `orchestra fdk diff` shows what this file declares, and
 // `orchestra fdk apply` creates it. It declares no code host or tracker, so it applies with no token.
 

package/templates/todo-factory/main.ts

@@ -66,8 +66,13 @@ const github = new Connection(factory, "github", {
   install: { permissions: ["contents:write"] },
 });
 
+// The edge adds the gateway key on the gateway's host. The runtime image's placeholder key rides x-api-key, and
+// the gateway refuses two keys that disagree, so the recipe removes it.
+const gatewayHost = required("ORCHESTRA_FDK_MODEL_GATEWAY_HOST");
 const gatewayKey = new Secret(factory, "model-gateway-key", {
   value: SecretValue.fromGatewayKey(new GatewayKey(factory, "model-gateway", { displayName: "todo-app bug fixing" })),
+  hosts: [gatewayHost],
+  injection: { headers: [{ name: "Authorization", value: "Bearer ${secret}" }], removeHeaders: ["x-api-key"] },
 });
 
 // The image tag hashes the runtime image and every file under image/: a rebuilt image under an unchanged tag
@@ -94,7 +99,7 @@ const runtime = new Environment(factory, "runtime", {
   // Open to start with. Deny the hosts of the team's hosted data here, and tighten once runs succeed.
   egress: EgressPolicy.allowAll()
     .applyPreset(github.egressPolicy())
-    .routeModelsViaGateway({ key: gatewayKey, host: required("ORCHESTRA_FDK_MODEL_GATEWAY_HOST") }),
+    .routeModelsViaGateway({ key: gatewayKey, host: gatewayHost }),
   // Docker for the services the codebase runs in containers. Remove both lines when nothing runs in Docker.
   setup: readFile("image/setup.sh"),
   disks: [{ mountPath: "/var/lib/docker", size: "50G" }],

package/dist/constructs/project.d.ts

@@ -1,33 +0,0 @@
-import { Construct } from "../core/construct.js";
-import type { PlanResource } from "../core/plan.js";
-import type { IProject } from "./interfaces.js";
-export interface ProjectProps {
-    slug?: string;
-    name?: string;
-    labels?: Record<string, string>;
-}
-export declare class Project extends Construct implements IProject {
-    /** Accepts a platform id or a slug interchangeably — one rule, stated on `IResource`. */
-    readonly projectId: string;
-    private readonly explicitSlug;
-    private readonly displayName;
-    private readonly labels;
-    constructor(scope: Construct, id: string, props?: ProjectProps);
-    /** @internal */
-    _resourceId(): string;
-    get slug(): string;
-    _toPlanResource(): PlanResource;
-    /**
-     * The slug grammar is validated so a malformed reference fails at the call site rather than as an
-     * apply-time 404; because every platform id carries the `_` that grammar rejects, the rejection names
-     * {@link Project.fromId} as the id path.
-     */
-    static fromSlug(slug: string): IProject;
-    /**
-     * Validated against {@link ENTITY_ID_PATTERN} for the same call-site reason `fromSlug` validates the slug
-     * grammar. Without this importer a project could only ever be referenced by slug, since `fromSlug`'s
-     * grammar rejects every `_`-carrying id — the uniform "id or slug" contract would be false for projects
-     * alone.
-     */
-    static fromId(id: string): IProject;
-}

package/dist/constructs/project.js

@@ -1,82 +0,0 @@
-// A factory declares at most one project, and the scope-less `Project.fromSlug`/`fromId` importers exist
-// because they are evaluated as the `new Factory({...})` argument — before the Factory, their only legal
-// scope, exists. `projectId` is emitted only when the factory declares a project: a deliberate exception to
-// the always-emit convention, so a project-less factory's plan bytes are unchanged. That cannot express a
-// move to the org commons, and does not need to — placement is identity, set once at create, so a divergence
-// is refused rather than reconciled.
-import { Construct } from "../core/construct.js";
-import { Factory } from "../core/factory.js";
-import { validateDeclaredLabels } from "../core/labels.js";
-import { validateSlugOrKey } from "../core/naming.js";
-import { refToken } from "../core/tokens.js";
-import { resolveManagedSlug, rootOf, validateExplicitSlug } from "./references.js";
-/**
- * Shape only — the platform is opaque about id contents, so this never parses one. It is the exact
- * complement of the slug grammar {@link validateSlugOrKey} enforces (a slug never carries `_`), which is
- * what makes {@link Project.fromSlug} and {@link Project.fromId} a clean split of one key space rather than
- * two spellings of one check.
- */
-const ENTITY_ID_PATTERN = /^[a-z][a-z0-9]*_[^_]+$/;
-export class Project extends Construct {
-    /** Accepts a platform id or a slug interchangeably — one rule, stated on `IResource`. */
-    projectId;
-    explicitSlug;
-    displayName;
-    labels;
-    constructor(scope, id, props = {}) {
-        super(scope, id);
-        validateDeclaredLabels(props.labels, `project '${this.node.path.join("/")}' labels`);
-        validateExplicitSlug(this, props.slug, "project");
-        this.explicitSlug = props.slug;
-        this.displayName = props.name ?? id;
-        // Snapshot, so a key added to the caller's literal after the gate above cannot reach synth.
-        this.labels = props.labels !== undefined ? { ...props.labels } : undefined;
-        this.projectId = refToken("project", this.node.path);
-        const root = rootOf(this);
-        if (!(root instanceof Factory)) {
-            throw new Error(`a Project must be declared under a Factory (its root construct); got '${root.node.id}'.`);
-        }
-        root._registerProject(this);
-    }
-    /** @internal */
-    _resourceId() {
-        return this.projectId;
-    }
-    get slug() {
-        return resolveManagedSlug(this, this.explicitSlug, "project");
-    }
-    _toPlanResource() {
-        const slug = this.slug;
-        // `description` is console-owned and never emitted. `labels` is emitted only when declared, so a project
-        // that declares none keeps its plan bytes; apply still removes the keys an earlier apply declared.
-        const payload = {
-            name: this.displayName,
-            slug,
-            ...(this.labels !== undefined ? { labels: { ...this.labels } } : {}),
-        };
-        return { kind: "project", path: this.node.path.join("/"), slug, managed: true, payload };
-    }
-    /**
-     * The slug grammar is validated so a malformed reference fails at the call site rather than as an
-     * apply-time 404; because every platform id carries the `_` that grammar rejects, the rejection names
-     * {@link Project.fromId} as the id path.
-     */
-    static fromSlug(slug) {
-        validateSlugOrKey(slug, "Project.fromSlug slug", "To reference a project by its platform id instead, use Project.fromId.");
-        return { projectId: slug, _resourceId: () => slug };
-    }
-    /**
-     * Validated against {@link ENTITY_ID_PATTERN} for the same call-site reason `fromSlug` validates the slug
-     * grammar. Without this importer a project could only ever be referenced by slug, since `fromSlug`'s
-     * grammar rejects every `_`-carrying id — the uniform "id or slug" contract would be false for projects
-     * alone.
-     */
-    static fromId(id) {
-        if (!ENTITY_ID_PATTERN.test(id)) {
-            throw new Error(`Invalid project id ${JSON.stringify(id)} for Project.fromId: a platform id is a lowercase prefix ` +
-                `word, exactly one '_', then a '_'-free suffix (e.g. 'proj_01jq7v…'). To reference a project by ` +
-                `its slug instead, use Project.fromSlug.`);
-        }
-        return { projectId: id, _resourceId: () => id };
-    }
-}

package/node_modules/@orchestraworks/client/dist/apis/GroupsApi.d.ts

@@ -1,95 +0,0 @@
-/**
- * Orchestra platform API
- * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
- *
- * The version of the OpenAPI document: 0.1.0
- *
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import * as runtime from '../runtime';
-import { type CreateGroupRequest } from '../models/CreateGroupRequest';
-import { type Group } from '../models/Group';
-import { type PageGroupSummary } from '../models/PageGroupSummary';
-import { type UpdateGroupRequest } from '../models/UpdateGroupRequest';
-export interface CreateGroupOperationRequest {
-    createGroupRequest: CreateGroupRequest;
-    xOrganizationId?: string;
-}
-export interface DeleteGroupRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface GetGroupRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface ListGroupsRequest {
-    q?: string;
-    member?: string;
-    page?: number;
-    limit?: number;
-    xOrganizationId?: string;
-}
-export interface UpdateGroupOperationRequest {
-    id: string;
-    updateGroupRequest: UpdateGroupRequest;
-    xOrganizationId?: string;
-}
-/**
- *
- */
-export declare class GroupsApi extends runtime.BaseAPI {
-    /**
-     * Creates request options for createGroup without sending the request
-     */
-    createGroupRequestOpts(requestParameters: CreateGroupOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    createGroupRaw(requestParameters: CreateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    createGroup(requestParameters: CreateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-    /**
-     * Creates request options for deleteGroup without sending the request
-     */
-    deleteGroupRequestOpts(requestParameters: DeleteGroupRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    deleteGroupRaw(requestParameters: DeleteGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
-    /**
-     */
-    deleteGroup(requestParameters: DeleteGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
-    /**
-     * Creates request options for getGroup without sending the request
-     */
-    getGroupRequestOpts(requestParameters: GetGroupRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    getGroupRaw(requestParameters: GetGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    getGroup(requestParameters: GetGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-    /**
-     * Creates request options for listGroups without sending the request
-     */
-    listGroupsRequestOpts(requestParameters: ListGroupsRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    listGroupsRaw(requestParameters: ListGroupsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PageGroupSummary>>;
-    /**
-     */
-    listGroups(requestParameters?: ListGroupsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PageGroupSummary>;
-    /**
-     * Creates request options for updateGroup without sending the request
-     */
-    updateGroupRequestOpts(requestParameters: UpdateGroupOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    updateGroupRaw(requestParameters: UpdateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    updateGroup(requestParameters: UpdateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-}

package/node_modules/@orchestraworks/client/dist/apis/ProjectsApi.d.ts

@@ -1,93 +0,0 @@
-/**
- * Orchestra platform API
- * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
- *
- * The version of the OpenAPI document: 0.1.0
- *
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import * as runtime from '../runtime';
-import { type CreateProjectRequest } from '../models/CreateProjectRequest';
-import { type PageProject } from '../models/PageProject';
-import { type Project } from '../models/Project';
-import { type UpdateProjectRequest } from '../models/UpdateProjectRequest';
-export interface CreateProjectOperationRequest {
-    createProjectRequest: CreateProjectRequest;
-    xOrganizationId?: string;
-}
-export interface DeleteProjectRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface GetProjectRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface ListProjectsRequest {
-    page?: number;
-    limit?: number;
-    xOrganizationId?: string;
-}
-export interface UpdateProjectOperationRequest {
-    id: string;
-    updateProjectRequest: UpdateProjectRequest;
-    xOrganizationId?: string;
-}
-/**
- *
- */
-export declare class ProjectsApi extends runtime.BaseAPI {
-    /**
-     * Creates request options for createProject without sending the request
-     */
-    createProjectRequestOpts(requestParameters: CreateProjectOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    createProjectRaw(requestParameters: CreateProjectOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Project>>;
-    /**
-     */
-    createProject(requestParameters: CreateProjectOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Project>;
-    /**
-     * Creates request options for deleteProject without sending the request
-     */
-    deleteProjectRequestOpts(requestParameters: DeleteProjectRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    deleteProjectRaw(requestParameters: DeleteProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
-    /**
-     */
-    deleteProject(requestParameters: DeleteProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
-    /**
-     * Creates request options for getProject without sending the request
-     */
-    getProjectRequestOpts(requestParameters: GetProjectRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    getProjectRaw(requestParameters: GetProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Project>>;
-    /**
-     */
-    getProject(requestParameters: GetProjectRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Project>;
-    /**
-     * Creates request options for listProjects without sending the request
-     */
-    listProjectsRequestOpts(requestParameters: ListProjectsRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    listProjectsRaw(requestParameters: ListProjectsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PageProject>>;
-    /**
-     */
-    listProjects(requestParameters?: ListProjectsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PageProject>;
-    /**
-     * Creates request options for updateProject without sending the request
-     */
-    updateProjectRequestOpts(requestParameters: UpdateProjectOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    updateProjectRaw(requestParameters: UpdateProjectOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Project>>;
-    /**
-     */
-    updateProject(requestParameters: UpdateProjectOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Project>;
-}

package/node_modules/@orchestraworks/client/dist/esm/apis/GroupsApi.d.ts

@@ -1,95 +0,0 @@
-/**
- * Orchestra platform API
- * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
- *
- * The version of the OpenAPI document: 0.1.0
- *
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import * as runtime from '../runtime';
-import { type CreateGroupRequest } from '../models/CreateGroupRequest';
-import { type Group } from '../models/Group';
-import { type PageGroupSummary } from '../models/PageGroupSummary';
-import { type UpdateGroupRequest } from '../models/UpdateGroupRequest';
-export interface CreateGroupOperationRequest {
-    createGroupRequest: CreateGroupRequest;
-    xOrganizationId?: string;
-}
-export interface DeleteGroupRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface GetGroupRequest {
-    id: string;
-    xOrganizationId?: string;
-}
-export interface ListGroupsRequest {
-    q?: string;
-    member?: string;
-    page?: number;
-    limit?: number;
-    xOrganizationId?: string;
-}
-export interface UpdateGroupOperationRequest {
-    id: string;
-    updateGroupRequest: UpdateGroupRequest;
-    xOrganizationId?: string;
-}
-/**
- *
- */
-export declare class GroupsApi extends runtime.BaseAPI {
-    /**
-     * Creates request options for createGroup without sending the request
-     */
-    createGroupRequestOpts(requestParameters: CreateGroupOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    createGroupRaw(requestParameters: CreateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    createGroup(requestParameters: CreateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-    /**
-     * Creates request options for deleteGroup without sending the request
-     */
-    deleteGroupRequestOpts(requestParameters: DeleteGroupRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    deleteGroupRaw(requestParameters: DeleteGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
-    /**
-     */
-    deleteGroup(requestParameters: DeleteGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
-    /**
-     * Creates request options for getGroup without sending the request
-     */
-    getGroupRequestOpts(requestParameters: GetGroupRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    getGroupRaw(requestParameters: GetGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    getGroup(requestParameters: GetGroupRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-    /**
-     * Creates request options for listGroups without sending the request
-     */
-    listGroupsRequestOpts(requestParameters: ListGroupsRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    listGroupsRaw(requestParameters: ListGroupsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PageGroupSummary>>;
-    /**
-     */
-    listGroups(requestParameters?: ListGroupsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PageGroupSummary>;
-    /**
-     * Creates request options for updateGroup without sending the request
-     */
-    updateGroupRequestOpts(requestParameters: UpdateGroupOperationRequest): Promise<runtime.RequestOpts>;
-    /**
-     */
-    updateGroupRaw(requestParameters: UpdateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Group>>;
-    /**
-     */
-    updateGroup(requestParameters: UpdateGroupOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Group>;
-}