fortrip 0.3.1 → 2.0.0

package/LICENSE

@@ -1,21 +1,202 @@
-MIT License
-
-Copyright (c) 2026 FortripEngineering
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                                 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/NOTICE

@@ -0,0 +1,4 @@
+Fortrip
+Copyright 2026 FortripAI, Inc.
+
+This product includes software developed at FortripAI, Inc. (https://fortrip.ai).

package/README.md

@@ -1,150 +1,239 @@
-# fortrip-cli
+# fortrip
 
-Search, price and book Fortrip hotels from the terminal or an AI agent.
-The npm package and the command are both `fortrip`.
+Search hotels, check live room rates and book with a payment link, from the
+terminal or an AI agent. Hotels only for now. The npm package and the command
+are both `fortrip`.
 
-For MCP clients, see the separately maintained
-[Fortrip MCP](https://github.com/FortripEngineering/fortrip-mcp)
-repository for local and hosted connection instructions.
+```bash
+npx -y fortrip login
+npx -y fortrip hotels search --query Bangkok --check-in 2026-11-10 --check-out 2026-11-12
+```
+
+## Install and run
+
+Node.js 22 or newer. Run it with `npx`, which needs no install:
+
+```bash
+npx -y fortrip <command>
+```
+
+or install it once and run `fortrip <command>`:
 
 ```bash
-npx fortrip login          # sign in through the browser
-npx fortrip search --query Bangkok --check-in 2026-11-10 --check-out 2026-11-12
+npm install --global fortrip
 ```
 
-Requires Node.js 22 or newer. No runtime dependencies.
+`fortrip --help` lists the commands, `fortrip hotels --help` the hotel
+commands, `fortrip <command> --help` one command's flags, and
+`fortrip --version` prints the version.
+
+Upgrading from 0.3: 1.0 signs in with OAuth, so a 0.3 sign-in is not reused;
+run `fortrip login` once. A `FORTRIP_TOKEN` from 0.3 is no longer accepted.
+`fortrip mcp` replaces the separate `fortrip-mcp` package.
+
+## Upgrading from 1.x
+
+2.0 puts the hotel commands under `fortrip hotels`, with the same flags and
+arguments:
+
+| 1.x | 2.0 |
+|---|---|
+| `search` | `hotels search` |
+| `hotel <hotelId>` | `hotels get <hotelId>` |
+| `rates` | `hotels rates` |
+| `book` | `hotels book` |
+
+Two MCP tools are renamed: `get_rates` is now `get_hotel_rates` and
+`create_booking` is now `book_hotel`. Sign-in is unchanged. `fortrip mcp` now
+also starts before you sign in: it lists its tools, and the first tool call
+answers with the sign-in link. 2.0 is licensed under Apache 2.0 instead of MIT.
+
+## Sign in
+
+```bash
+fortrip login
+```
+
+`login` prints a code and a link on stderr, opens the link in your browser
+(not with `--no-browser`), and waits until you sign in to Fortrip and approve.
+It then prints your account.
+
+An AI agent can't sit in `login`, so any other command that needs a sign-in
+doesn't wait: it exits with code 3 and prints `loginUrl`, `userCode` and
+`expiresInSeconds` as JSON on stderr. The agent shows the link to the user;
+once the user has approved it in the browser, the agent reruns the same
+command, which finishes signing in and carries on. Commands that run in
+parallel share one link. When Fortrip stops accepting the saved sign-in (it
+was revoked, or it expired and couldn't be renewed), the command does the same
+and keeps the old sign-in until the new link is approved.
+
+You stay signed in. Access tokens last 24 hours and the CLI renews them
+itself, before they run out; refresh tokens don't expire, so the sign-in lasts
+until you run `fortrip logout`, which revokes this machine's sign-in and
+deletes it (other machines stay signed in). `fortrip whoami` prints the
+signed-in account.
+
+The sign-in is saved in `~/.config/fortrip/credentials.json` (`$XDG_CONFIG_HOME`
+is honoured), mode `0600`, per API URL, so a token is only sent to the server
+that issued it.
+
+If a new or renewed sign-in can't be saved (the file stays busy or turns out to
+be damaged), the `hotels` commands and `whoami` still work for that run, with
+the new token. The sign-in is kept in a `credentials.recovered-*.json`
+file next to the credentials file, and the command's JSON output carries a
+`warning` and, when the sign-in could be kept, that file in `recoveryFile`.
+Later commands use it, and the next successful save merges it back. `login`
+doesn't carry on in that case: it exits 1, with `recoveryFile` in the error, and
+the sign-in is kept in that file all the same.
+
+If the directory itself can't be written (a read-only home, as in some agent
+sandboxes), `login` exits 1 before it asks you to approve anything, and any
+other command that needs to save a sign-in exits 1 too. The error says to set
+`XDG_CONFIG_HOME` to a directory that can be written, or to set `FORTRIP_TOKEN`.
 
 ## Commands
 
 | Command | What it does |
 |---|---|
-| `login [--no-browser]` | Device-code login: prints a code, opens `/cli/authorize`, waits for you to approve |
-| `logout` | Revokes the saved token on the server and deletes it locally |
-| `whoami` | The signed-in account |
-| `search` | Hotels with indicative prices |
-| `hotel <hotelId> [--with-rooms]` | Static hotel detail |
-| `rates` | Live rooms and rates |
-| `book` | Order + payment link (a Fortrip page that continues to Stripe) |
-
-Run `fortrip --help` for every flag, or `fortrip <command> --help` for one
-command's. `search`, `rates` and `book` also accept `--body '<json>'` or
-`--body @file.json` with the raw request body; flags override its fields.
+| `hotels search` | Find hotels with indicative prices |
+| `hotels get <hotelId>` | Static hotel detail: description, policies, facilities and photos |
+| `hotels rates` | Live rooms and rates for up to 15 hotels |
+| `hotels book` | Create an order and get a payment link |
+| `login` | Sign in through the browser (device code) |
+| `logout` | Revoke and forget the saved token |
+| `whoami` | Show the signed-in account |
+| `guide [topic]` | Print the guide for AI agents (Markdown) |
+| `mcp` | Run an MCP server over stdio for local clients, bridged to Fortrip's hosted server |
 
-`--adults` and `--child-age` are per room, and every room has the same
-occupancy: 2 rooms for 4 adults is `--rooms 2 --adults 2`. `rates` defaults
-to 1 room for 2 adults; `book` requires `--rooms` and `--adults`.
+```bash
+fortrip hotels rates --hotel <hotelId> --check-in 2026-11-10 --check-out 2026-11-12 --rooms 1 --adults 2
+```
 
-Output is JSON on stdout. Errors are JSON on stderr, with fixed exit codes:
+`hotels search`, `hotels rates` and `hotels book` also accept `--body '<json>'`
+or `--body @file.json` with the raw request body; flags override its fields.
 
-| Code | Meaning |
-|---|---|
-| 0 | Success |
-| 1 | Other error (`retryable: true` on stderr: worth one retry) |
-| 2 | Invalid arguments (local or HTTP 400) |
-| 3 | Not logged in, or the sign-in wasn't accepted (HTTP 401) |
-| 4 | Rate limited (HTTP 429; `retryAfterSeconds` on stderr) |
+`--adults` and `--child-age` are per room, and every room has the same
+occupancy: 2 rooms for 4 adults is `--rooms 2 --adults 2`. `hotels rates` and
+`hotels book` both require `--rooms` and `--adults`.
 
-## Credentials
-
-- `login` saves the token to `~/.config/fortrip/credentials.json`
-  (`$XDG_CONFIG_HOME` is honoured), mode `0600`. Saved tokens are stored per
-  API URL, so a saved token is only sent to the server that issued it.
-- Without a token, any other command starts a device login and exits 3 with
-  `loginUrl` on stderr instead of waiting. Once that link is approved in the
-  browser, rerunning the command saves the token and carries on. This is how
-  AI agents sign in, since they can't sit in `login`. Commands run in
-  parallel share one login link. If the server doesn't accept the saved
-  token, the command keeps it and starts a new login the same way; once that
-  link is approved, the new token replaces the saved one.
-- `FORTRIP_TOKEN` overrides the saved login (CI, remote sandboxes). It is not
-  tied to a server: it is sent to whatever `FORTRIP_API_URL` points at. If the
-  server doesn't accept it, commands exit 3 with `tokenSource: "FORTRIP_TOKEN"`
-  and no `loginUrl`.
-- `FORTRIP_API_URL` overrides the base URL (default `https://fortrip.ai`).
-  Plain `http` is only accepted for `localhost`.
-- `FORTRIP_CURRENCY` sets the default `--currency` for `search` and `rates`
-  (`CNY` or `USD`; the API defaults to `CNY`). Display only: `book`
-  charges the currency it returns.
-
-`logout` revokes the saved token. With the Fortrip server update released
-alongside CLI 0.3.1, sign-ins that go unused for 90 days stop working, and
-signed-in users can list and revoke their CLI sign-ins in their Fortrip
-account (account menu → **Fortrip CLI**).
-
-If a new sign-in can't be saved (the file is busy or damaged), it is kept
-in a `credentials.recovered-*.json` file next to `credentials.json` (mode
-`0600`), and the command's JSON output names it in `warning` and
-`recoveryFile`. The next successful save merges it back and removes the
-file; `logout` revokes and removes these too.
-
-Sharing `credentials.json` with 0.3.0 works on a best-effort basis: 0.3.0
-finds the newest pending login where it expects it, but it writes the file
-without a lock, so don't sign in with 0.3.0 and 0.3.1 at the same moment.
-
-## Agent skill
+`hotels book` creates an unpaid order and prints a payment link for it.
+Nothing is charged until the person pays on the page the link opens.
+
+## For AI agents
 
 ```bash
-npx skills add FortripEngineering/fortrip-plugins --skill fortrip-cli
+npx -y fortrip guide            # when to use the CLI, call order, sign-in, what to show before a payment link
+npx -y fortrip guide planning   # flexible dates, budgets, split stays, several destinations
 ```
 
-The skill lives in
-[fortrip-plugins](https://github.com/FortripEngineering/fortrip-plugins); the
-Claude directory plugin there uses the hosted MCP instead of the CLI. The
-skill only tells the agent to run `npx -y fortrip@latest skill`, which prints
-[`AGENT_GUIDE.md`](AGENT_GUIDE.md): when to use the CLI, the call order, login,
-and what to show the user before handing over a payment link. The guide ships
-with the package, so a CLI release updates every installed skill. Edit
-`AGENT_GUIDE.md`, not the skill.
-
-`fortrip skill planning` prints [`guides/planning.md`](guides/planning.md):
-what to ask, how to rank and how to present options for flexible dates,
-budgets, split stays and several destinations. Both guides are printed with
-`fortrip@latest` replaced by the running version, so an agent keeps using the
-same CLI for the whole conversation.
+Both print Markdown, with `fortrip@latest` replaced by the running version, so
+an agent keeps using the same CLI for the whole conversation. The guide is
+written once in
+[`@fortrip/agent-contract`](https://github.com/FortripEngineering/fortrip/tree/main/packages/contract/guide)
+and compiled into the CLI.
 
-## Support
+For agents that can run shell commands, the same guide is also a skill:
 
-For changes, cancellations, refunds or other help with a booking, email
-[info@fortrip.ai](mailto:info@fortrip.ai) with the booking's order link
-(`orderUrl`).
+```bash
+npx skills add FortripEngineering/fortrip --skill fortrip-cli
+```
 
-## Development
+## MCP server
+
+`fortrip mcp` runs an MCP server on stdio for clients that start local
+servers. It forwards to Fortrip's hosted MCP server, `https://fortrip.ai/api/mcp`,
+with your saved sign-in.
+
+You can add the server to a client before you sign in: signed out, it still
+starts and lists its tools. The first tool call is then answered with a
+JSON-RPC error (`-32001`) whose message says to run `npx -y fortrip login` in a
+terminal, or to open the sign-in link it names and approve it. Once you have,
+the next tool call works, with no restart. If a sign-in stops working later,
+only the request that hit it fails with the same kind of error, and the server
+keeps running.
+
+Claude Desktop (Settings, Developer, Edit Config; on macOS
+`~/Library/Application Support/Claude/claude_desktop_config.json`, on Windows
+`%APPDATA%\Claude\claude_desktop_config.json`) and Cursor (`~/.cursor/mcp.json`,
+or `.cursor/mcp.json` in a project):
+
+```json
+{
+  "mcpServers": {
+    "fortrip": {
+      "command": "npx",
+      "args": ["-y", "fortrip", "mcp"]
+    }
+  }
+}
+```
+
+Claude Code:
 
 ```bash
-pnpm install
-pnpm dev search --query Bangkok ...      # run from source
-pnpm test
-pnpm typecheck
-pnpm build                               # dist/cli.js
+claude mcp add fortrip -- npx -y fortrip mcp
 ```
 
-Point at a local Fortrip app with `FORTRIP_API_URL=http://localhost:3000`.
+Codex, with `codex mcp add fortrip -- npx -y fortrip mcp` or in
+`~/.codex/config.toml`:
 
-## Releasing
+```toml
+[mcp_servers.fortrip]
+command = "npx"
+args = ["-y", "fortrip", "mcp"]
+```
+
+Clients that support remote MCP servers with OAuth don't need the CLI: add
+`https://fortrip.ai/api/mcp` as a remote server and sign in to Fortrip in the
+browser when the client asks. In Claude Code, that is
+`claude mcp add --transport http fortrip https://fortrip.ai/api/mcp`.
+
+## Environment variables
+
+| Variable | Meaning |
+|---|---|
+| `FORTRIP_TOKEN` | An access token, used instead of the saved sign-in. It lasts at most 24 hours, so it suits one sandbox session or one CI run, not standing CI. It isn't tied to a server: it is sent to whatever `FORTRIP_API_URL` points at. If Fortrip doesn't accept it, or it contains a line break or another character that can't be sent in a header, commands exit 3 with `tokenSource: "FORTRIP_TOKEN"` and no `loginUrl`; the error never repeats the token. |
+| `FORTRIP_API_URL` | The base URL (default `https://fortrip.ai`). Plain `http` is only accepted for `localhost`. |
+| `FORTRIP_CURRENCY` | The default `--currency` for `hotels search` and `hotels rates` (`CNY` or `USD`; the API uses `CNY` when nothing sets one). It only changes how prices are shown: `hotels book` charges the currency it returns. |
 
-Pushing a `v*` tag publishes to npm through
-[`.github/workflows/publish.yml`](.github/workflows/publish.yml), which signs
-in with npm trusted publishing (no npm token in GitHub). Pull requests and
-pushes to `main` run typecheck, tests and the build through
-[`.github/workflows/ci.yml`](.github/workflows/ci.yml).
+## Output and exit codes
 
-1. Bump the version in a PR and merge it into `main`:
-   `npm version minor --no-git-tag-version` (or `patch`).
-2. Tag the merged commit on `main` and push the tag:
+Data commands (the `hotels` commands, `login`, `logout` and `whoami`) print
+JSON on stdout. `guide` prints Markdown, and `fortrip mcp`
+speaks MCP over stdio. Errors are JSON on stderr, with an `error` message, the
+`exitCode` and any details.
 
-   ```bash
-   git checkout main && git pull
-   git tag v0.2.0 && git push origin v0.2.0
-   ```
+| Code | Meaning |
+|---|---|
+| 0 | Success |
+| 1 | Other error (`retryable: true` on stderr: worth one retry) |
+| 2 | Invalid arguments (local or HTTP 400) |
+| 3 | Not signed in, or the sign-in wasn't accepted (HTTP 401); `loginUrl` on stderr |
+| 4 | Rate limited (HTTP 429; `retryAfterSeconds` on stderr) |
+
+## Support
+
+For changes, cancellations, refunds or other help with a booking, email
+[info@fortrip.ai](mailto:info@fortrip.ai) with the booking's order link
+(`orderUrl`).
+
+## Releasing
 
-The workflow refuses a tag that doesn't match `package.json` or isn't on
-`main`. A `build` job runs typecheck, tests and the build and packs the
-tarball; a `publish` job in the `npm-publish` environment publishes that
-tarball, with no install or build of its own. Every installed skill picks up
-the new guide on its next `npx fortrip@latest skill`.
+Both packages in this repository, `fortrip` and `@fortrip/agent-contract`,
+are released together from a `vX.Y.Z` tag. See
+[Releasing](https://github.com/FortripEngineering/fortrip#releasing) in the
+repository's README.
 
 ## License
 
 The code and documentation in this repository are licensed under the
-[MIT License](LICENSE). This license does not grant access to the hosted
-Fortrip service, hotel inventory, or third-party data.
+[Apache License 2.0](https://github.com/FortripEngineering/fortrip/blob/main/LICENSE).
+Copyright 2026 FortripAI, Inc. Versions before 2.0.0 were published under the
+MIT License. This license does not grant access to the hosted Fortrip service,
+hotel inventory, or third-party data.
+
+"Fortrip" and the Fortrip logo are trademarks of FortripAI, Inc. The license
+does not grant permission to use the trade names, trademarks, service marks or
+product names of FortripAI, Inc., except as required for reasonable and
+customary use in describing the origin of the software and reproducing the
+content of the NOTICE file (section 6).

package/THIRD-PARTY-NOTICES

@@ -0,0 +1,30 @@
+Third-party notices for the fortrip package
+
+The files in dist/ include code from the packages below, bundled into them.
+Each is listed with its version and license, followed by the license text
+from the package's LICENSE file.
+
+================================================================================
+zod 4.4.3 (MIT)
+--------------------------------------------------------------------------------
+MIT License
+
+Copyright (c) 2025 Colin McDonnell
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.