v0.103.1

Install or update: npm i -g cotal-ai@0.103.1

Changes in this release

• A manager can now bound how many live seats it holds for one owner, so a manager shared by several
  owners cannot be filled by the first one to ask. cotal supervise --seat-cap <n> and cotal up --seat-cap <n> set it, and the value is recorded in the root, so a repair, a resume or a bare up
  after down keeps it. The default is unlimited, which leaves the manager's own 50-slot ceiling as
  the only bound, so a mesh with one owner keeps every slot it had. The cap counts the seats that
  manager supervises for the owner a launch belongs to, plus its launches that have no process yet;
  it does not count cooling slots or another owner's seats.

  A launch over the cap is refused before a name is reserved or anything is minted, and the seats
  already running are untouched. The refusal is resource-exhausted carrying the owner, its count and
  the cap, so a caller reads the numbers rather than the sentence. cotal spawn exits 2 with
  CONFLICT, the manager's sentence and a remedy naming cotal stop --name <name> and --seat-cap;
  under --json those three numbers are in error.cause.detail. cotal_spawn shows an agent the same
  sentence. Stopping one of that owner's seats admits the next launch.

• The folder question a managed launch asks in a terminal now works on a static mesh. An operator
  instrument carries resolve-cwd on the manager it pins, the read that question's check needs, so a
  typed folder is resolved by that manager instead of refused at the broker, and a folder it cannot
  use is shown with its reason and asked again. A check that could not be made at all keeps the
  responder's internals out of its sentence and names the -C <dir> that sends the folder with the
  launch.

  The question also reads the host the manager reports, the name cotal ps prints as its reported
  host, so a manager running on this host is no longer asked about and its receipt no longer says the
  host was not reported. The mesh and the pin are read before anything is asked, so a stopped mesh or
  an --on that names no running manager is refused first.

What's Changed

• fix(manager): preserve structured refusal codes by @davidfarah2003 in #4816
• test: refresh detached spawn refusal fixture anchor by @davidfarah2003 in #4818
• feat(auth): serve several spaces from one auth callout process by @davidfarah2003 in #4819
• fix(cli): refuse delivery cutover after an unconfirmed manager stop by @davidfarah2003 in #4820
• feat(manager,cli): cap live seats per owner on a manager by @davidfarah2003 in #4822
• fix(cli): ask the spawn folder question only where it can be answered by @davidfarah2003 in #4821
• chore(release): version packages by @davidfarah2003 in #4817
• chore(release): version packages by @davidfarah2003 in #4823

Full Changelog: v0.102.0...v0.103.1