@bridge-ds/mcp 0.4.0 → 0.5.0

package/dist/branches.d.ts

@@ -9,8 +9,16 @@ export declare const RIGHTS: {
     readonly draft: "Pull requests: read and write (you must be the author, as in Studio)";
     readonly docs: "Contents and Pull requests: read and write";
 };
+export declare function reader(ctx: BridgeContext): Promise<GitHubClient>;
+/**
+ * A client for writes on a branch someone already opened (any name, never a protected branch): the token is required,
+ * with the rights `need` names, so the error says exactly what to add.
+ */
+export declare function writer(ctx: BridgeContext, what: string, need: string): Promise<GitHubClient>;
 /** 12, "#12" or a pull request link: the branch number. Throws how to fix it otherwise. */
 export declare function branchNumber(input: number | string): number;
+/** The viewer of the token, or null without one (or when GitHub does not say). */
+export declare function viewerOf(ctx: BridgeContext, gh: GitHubClient): Promise<string | null>;
 /** Everything Studio reads about one branch to paint its header and decide its actions. */
 export declare function branchFacts(ctx: BridgeContext, gh: GitHubClient, n: number, viewer: string | null): Promise<{
     config: BridgeConfig;
@@ -154,11 +162,8 @@ export declare function listProducts(ctx: BridgeContext): Promise<{
  * Throws with the list when the name is unknown.
  */
 export declare function resolveProduct(ctx: BridgeContext, name?: string | undefined): Promise<ProductConfig>;
-/** Labels and a body line for a branch that starts work for a product (the default product adds nothing). */
-export declare function productMarks(products: ProductConfig[], p: ProductConfig): {
-    labels: string[];
-    line: string;
-};
+/** Labels and a body line for a branch that starts work for a product: the core rule Studio writes too. */
+export { productMarks } from '@bridge-ds/core';
 /**
  * Try it in a product and share it with a product team: the preview of each product Vercel reported for this branch
  * (opened with the Bridge toolbar on it), and the install command product teams use in a staging branch, with a