Module teams 

Where supercode-teams lives on this box, and the service unit that keeps its node up (docs/architecture/teams.md).

supercode does not implement teams; the sdk/teams package does. This module holds the two facts the Rust CLI needs about it:

• where its Node entry is — teams_entry, resolved exactly the way crate::orchestrator::daemon_entry resolves the orchestrator’s: SUPERCODE_TEAMS_ENTRY first, then the checkout the running binary sits in, then the current directory, then the globally installed @volter-ai-dev/supercode-teams package (npm root -g).
• what a service unit for its node would say — service_unit renders the launchd plist / systemd unit that runs node <entry> node start --listen 127.0.0.1:0, written under <home>/service/; install_service and uninstall_service drive launchctl / systemctl --user over it.

Everything else about teams — its keys, grants, log, machines — is the Node package’s own state, written by its own CLI. There is no second writer of that home in this binary.

Enums

TeamsError

Why a teams verb could not do its work.

Constants

SERVICE_DIR

Directory the rendered service unit is written into, relative to the home.

SERVICE_NAME

launchd label / systemd unit name for this Machine’s teams node.

TEAMS_ENTRY

The teams CLI entry inside the sdk/teams package.

TEAMS_PACKAGE

The npm name the sdk/teams package is published under.

Functions

install_service

Render the unit, hand it to the platform’s service manager, and start it.

service_status

What the platform’s service manager says about the teams node unit.

service_unit

Render the per-platform service unit for this Machine’s teams node.

teams_entry

Locate the Node teams entry (sdk/teams/bin/teams.mjs).

teams_home

The teams home: SUPERCODE_TEAMS_HOME, else <SUPERCODE_HOME>/teams.

uninstall_service

Stop and unregister the unit, and remove the rendered file.

write_unit

Write a rendered unit under <home>/service/.