@basein/runner 0.1.0 → 0.2.0

package/LICENSE

@@ -1,201 +1,201 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -51,11 +51,18 @@ byte-for-byte.
 
 ```bash
 export BIR_AUTH_URL=https://your-basein-service   # required to record anything
-bir login                                        # once
+bir login                                        # once; approve it in the browser
 bir-hooks                                        # leave running; Ctrl-C to stop
 claude                                           # your session, now recorded
 ```
 
+`bir login` prints a link and a short code and waits for you to approve it in
+the browser — the OAuth device grant, the same shape `gh auth login` uses. It
+never handles a password, so it works for accounts that only sign in with
+Google, and the link can be opened on any device, which is what makes it usable
+on a headless runner. `--no-browser` prints the link without opening one;
+`--password` is the deprecated email-and-password prompt, removed next release.
+
 Check it:
 
 ```bash
@@ -174,7 +181,7 @@ instead.
 
 | Variable | Effect |
 |---|---|
-| `BIR_AUTH_URL` | BaseIn auth-service. **Unset means nothing is recorded** — everything else still works. |
+| `BIR_AUTH_URL` | BaseIn auth-service — the **API** address (normally `https://api.<your-domain>`), not the docs or app website. **Unset means nothing is recorded** — everything else still works. |
 | `BIR_AUTH_DISABLE=1` | Skip authentication (local dev / CI). |
 | `BIR_CONTROL_PORT` | Preferred control-server port (default 53411). |
 | `BIR_CONTROL_URL` / `BIR_CONTROL_TOKEN` | Point a proxy at a control server directly, bypassing discovery. Injected into generated config; the only reliable channel for an SDK session. |

package/dist/auth/client.d.ts

@@ -1,21 +1,35 @@
 /**
- * auth client — ported from RRepeat's `src/auth/client.ts` (Phase 4.1).
+ * auth client — the CLI's session with the BaseIn service.
  *
- * Authenticates the CLI user against the BaseIn auth-service and returns a JWT
- * session. Every recording call carries that access token; the recording's owner
- * is the JWT subject on the server side, which is what makes tenancy work
- * without BaseInstRunner knowing anything about it.
+ * Every recording call carries an access token; the recording's owner is the
+ * JWT subject on the server side, which is what makes tenancy work without
+ * BaseInstRunner knowing anything about it.
+ *
+ * TWO HALVES, AND ONLY ONE OF THEM MAY PROMPT.
+ *
+ * `authenticate()` is the silent half, and every process calls it — `bir-hooks`
+ * at startup, each `bir-proxy`, and the CLI:
  *
- * Flow:
  *   1. Load the cached session from ~/.baseinstrunner/credentials.json.
  *   2. If the access token is still valid, reuse it.
  *   3. Else if a refresh token is present, POST /auth/refresh (silent).
- *   4. Else prompt for email + password and POST /auth/login.
- *   5. Persist the result (mode 0600) and return it.
+ *   4. Else give up and return undefined.
+ *
+ * It used to have a fifth step — prompt for a password — and that had to go
+ * when sign-in moved to the browser. A device flow prints a code and waits up
+ * to ten minutes for someone to approve it in a browser; a control server doing
+ * that at startup, possibly under a supervisor where nobody can see the code,
+ * would hang instead of degrading. So interaction lives in `deviceLogin()`,
+ * which only `bir login` calls.
  *
- * WHY IT NEVER `process.exit`s: `bir-proxy` runs inside the host's process tree.
- * Failing to authenticate must degrade to not-recording (§10), not kill a server
- * the host is waiting on. Callers get `undefined` and decide.
+ * `deviceLogin()` is the interactive half: the OAuth 2.0 device authorization
+ * grant (RFC 8628). It mints a code, prints a link, and polls until the person
+ * approves in the console. It never handles a password, which is what makes it
+ * work for Google-only accounts — they have no password to type.
+ *
+ * WHY NOTHING HERE `process.exit`s: `bir-proxy` runs inside the host's process
+ * tree. Failing to authenticate must degrade to not-recording (§10), not kill a
+ * server the host is waiting on. Callers get `undefined` and decide.
  *
  * Config:
  *   BIR_AUTH_URL      base URL of the BaseIn auth-service (required).
@@ -36,8 +50,13 @@ export interface AuthSession {
 export interface AuthenticateOptions {
     /** Base URL of the auth service. Defaults to BIR_AUTH_URL. */
     authUrl?: string;
-    /** Never prompt: fail (return undefined) if no valid/refreshable session exists. */
-    nonInteractive?: boolean;
+}
+interface AuthResponse {
+    accessToken: string;
+    refreshToken: string;
+    /** Access token lifetime in seconds. */
+    expiresIn: number;
+    user: AuthUser;
 }
 /**
  * Where the cached session lives.
@@ -77,9 +96,129 @@ export declare function resolveAuthUrl(opts?: AuthenticateOptions): string;
  * configure is worse than failing.
  */
 export declare function normalizeAuthUrl(baseUrl: string, fetchImpl?: typeof fetch): Promise<string>;
+/**
+ * The hint printed whenever `BIR_AUTH_URL` turns out not to be the API. Kept in
+ * one place so `bir login`, `bir doctor` and the interactive prompt agree.
+ */
+export declare const AUTH_URL_HINT: string;
+/**
+ * Is there a BaseIn service at `baseUrl`? Returns `undefined` when there is,
+ * else one line saying what answered instead.
+ *
+ * WHY THIS EXISTS. Pointing `BIR_AUTH_URL` at the *website* instead of the API
+ * (`https://example.com` is the docs, `https://api.example.com` the service) is
+ * the easiest mistake to make and the hardest to read back: the static site
+ * answers `GET /health` with 200 and a page, so nothing objects until the
+ * password has already been POSTed to it and it says `405 Method Not Allowed`
+ * — a message about HTTP verbs, for a problem about hosts. Observed on a first
+ * sign-in; the user tried the app URL next and got a redirect.
+ *
+ * So, before anyone types a password: expect the health endpoint to answer
+ * with JSON. A website answers with HTML; a wrong port answers with nothing.
+ * The check is deliberately loose about the body — deployments differ — and
+ * strict about the content type, which is what separates a service from a page.
+ */
+export declare function describeAuthService(baseUrl: string, fetchImpl?: typeof fetch): Promise<string | undefined>;
 /**
  * Authenticate and return a valid session, or `undefined` when none can be
  * obtained. Callers degrade to not-recording rather than failing the session.
  */
 export declare function authenticate(opts?: AuthenticateOptions): Promise<AuthSession | undefined>;
+/**
+ * The service has no device endpoints — it predates browser sign-in.
+ *
+ * Thrown so `bir login` can fall back to the password flow rather than leaving
+ * someone stranded on a runner that is newer than the service it talks to.
+ */
+export declare class DeviceFlowUnsupported extends Error {
+    constructor();
+}
+/** The CLI's view of a started device authorization. */
+export interface DeviceCodeGrant {
+    deviceCode: string;
+    userCode: string;
+    verificationUri: string;
+    verificationUriComplete?: string;
+    expiresIn: number;
+    interval: number;
+}
+/**
+ * Start a sign-in. Returns the codes; the caller shows one and polls with the
+ * other.
+ *
+ * `clientName`/`clientVersion` are shown on the approval page so the person can
+ * tell their own `bir login` from somebody else's — the one defence a device
+ * flow has against being talked into approving a stranger's code.
+ */
+export declare function startDeviceCode(authUrl: string, client: {
+    name?: string;
+    version?: string;
+}, fetchImpl?: typeof fetch): Promise<DeviceCodeGrant>;
+/** The user gave up, or the code died before anyone approved it. */
+export declare class DeviceFlowAborted extends Error {
+    readonly reason: "access_denied" | "expired_token" | "timeout" | "cancelled";
+    constructor(message: string, reason: "access_denied" | "expired_token" | "timeout" | "cancelled");
+}
+export interface PollOptions {
+    interval: number;
+    expiresIn: number;
+    fetchImpl?: typeof fetch;
+    /** Injected so tests run in milliseconds rather than minutes. */
+    sleep?: (ms: number) => Promise<void>;
+    signal?: AbortSignal;
+    now?: () => number;
+}
+/**
+ * Poll until the sign-in is approved, refused, or dies.
+ *
+ * RFC 8628 §3.5's loop, including the part people skip: `slow_down` is not an
+ * error, it is the server asking for a longer gap, and the interval must
+ * *stay* longer afterwards. Ignoring it turns a slow client into a blocked one.
+ */
+export declare function pollDeviceToken(authUrl: string, deviceCode: string, opts: PollOptions): Promise<AuthResponse>;
+/**
+ * Open a URL in the user's browser. Best effort, and never fatal.
+ *
+ * No dependency and no shell: this package ships zero runtime dependencies, and
+ * passing a URL through a shell is how a URL becomes a command. The link is
+ * printed either way, so a failure here costs nothing.
+ */
+export declare function openBrowser(url: string): void;
+export interface DeviceLoginOptions {
+    /** `--no-browser`, or a machine where opening one is wrong. */
+    openBrowser?: boolean;
+    fetchImpl?: typeof fetch;
+    sleep?: (ms: number) => Promise<void>;
+    signal?: AbortSignal;
+    /** Where the human-readable lines go. stderr, so stdout stays parseable. */
+    write?: (text: string) => void;
+}
+/**
+ * Sign in through the browser and cache the session.
+ *
+ * Everything a person sees goes to stderr: `bir login`'s stdout is one line
+ * that a script may read, and the code block is not it.
+ */
+export declare function deviceLogin(authUrl: string, opts?: DeviceLoginOptions): Promise<AuthSession | undefined>;
+/**
+ * Sign in with an email and a password.
+ *
+ * DEPRECATED, and kept for exactly two cases: `bir login --password`, and a
+ * runner talking to a service that predates the device endpoints. Both go in
+ * the release after this one, and this function goes with them.
+ *
+ * It cannot work at all for an account created through Google — there is no
+ * password on it to send — which is the main reason sign-in moved.
+ */
+export declare function legacyPasswordLogin(authUrl: string): Promise<AuthSession | undefined>;
+/**
+ * Sign out: revoke the refresh token server-side, then forget it locally.
+ *
+ * Deleting the file alone left the token live for its full 30 days, which made
+ * `bir logout` a tidy-up rather than a revocation. The endpoint is idempotent
+ * and its failure is not worth blocking on — the local half must happen either
+ * way, or "logged out" would be a lie on a machine with no network.
+ */
+export declare function logout(authUrl?: string): Promise<void>;
+export {};
 //# sourceMappingURL=client.d.ts.map