@go-labs-sg/gosh 0.13.0 → 0.14.0

package/README.md

@@ -183,8 +183,9 @@ value in that template team's `order` field:
 Events default to `OPEN` progression, which keeps the existing open-play flow.
 Sequential progression starts each team or individual on an ordered station
 route. Group routing is available only for `TEAM` play mode. Create teams and
-assign them to routing groups before launching the event; setup freezes when
-play starts. A group shares its ordered station route, while each team keeps
+assign them to routing groups before launching the event; sequential setup
+freezes when play starts. Grouped OPEN events lock only a started team's group
+assignment, a started group's route and the gameplay settings. A group shares its ordered station route, while each team keeps
 independent progress through that route.
 
 Configure gameplay, then manage the event's routing groups and their complete
@@ -225,6 +226,43 @@ the desired order. Use `groupId: null` with `assign-team` to unassign a team.
 Group names are trimmed and limited to 80 characters. The delete command
 requires the additional `--allow-delete` effect flag.
 
+### Staggered group release
+
+`routing-group release` changes flag-off without changing routes. It requires
+launch permission and a draft, ready or live TEAM event with group routing. A
+different group already playing does not block it. Once a team in the target
+group has started, only HOLD (emergency hold) and RELEASE_SCHEDULED_HOLD (resume)
+are accepted.
+
+```bash
+gosh routing-group release \
+  --input '{"eventId":"event-id","groupId":"group-d","action":"SCHEDULE","releaseAt":"2030-01-01T09:20:00+08:00"}' \
+  --target group-d \
+  --allow-state-change
+gosh routing-group release \
+  --input '{"eventId":"event-id","groupId":"group-d","action":"HOLD"}' \
+  --target group-d \
+  --allow-state-change
+```
+
+Replace example IDs/time with your intended target and a future instant.
+SCHEDULE requires an ISO timestamp with `Z` or a numeric timezone offset;
+offsetless, invalid and past times are rejected. CLEAR sets the schedule to null
+but preserves a hold. HOLD overrides the clock. RELEASE_SCHEDULED_HOLD removes
+the hold and retains the schedule; an elapsed/no schedule releases immediately.
+RELEASE_NOW clears both schedule and hold. Omit `releaseAt` for non-schedule
+actions. Repeated no-op controls do not create duplicate audits. List routing
+groups to read back release values and editability, and use
+`gosh routing-group release-history --input '{"eventId":"event-id","groupId":"group-d"}'`
+for the five most recent actor/before/after changes; the existing event activity
+timeline provides the full audit history.
+
+The server evaluates deadlines without cron. Release never starts a timer or
+bypasses LIVE status, availability, check-in or captain permissions. Any team in
+a group beginning play locks that group's schedule; emergency HOLD/resume stays
+available and does not pause running station clocks. There is no
+untimed practice-mission exemption. See [the design notes](../../../docs/design/gosh-staggered-routing-group-release.md).
+
 For sequential player actions, complete any required location check-in with
 `gosh player station-check-in` first. The server checks the signed-in player’s
 current check-in record; a successful check-in also starts the station timer.

package/command-manifest.json

@@ -1173,6 +1173,25 @@
 		"requiresAuth": true,
 		"summary": "List an event's routing groups, ordered stations, and assigned teams."
 	},
+	{
+		"effects": [],
+		"input": "json",
+		"operation": "query",
+		"path": ["routing-group", "release-history"],
+		"procedure": "team.listRoutingGroupReleaseHistory",
+		"requiresAuth": true,
+		"summary": "Show a routing group's five most recent release changes with actor, action and before/after UTC values."
+	},
+	{
+		"effects": ["state-change"],
+		"input": "json",
+		"operation": "mutation",
+		"path": ["routing-group", "release"],
+		"procedure": "team.updateRoutingGroupRelease",
+		"requiresAuth": true,
+		"summary": "Schedule (future releaseAt ISO timestamp with offset), CLEAR schedule, HOLD, RELEASE_SCHEDULED_HOLD (keep schedule), or RELEASE_NOW for a routing group. After a group starts, only HOLD and RELEASE_SCHEDULED_HOLD are accepted. Requires launchEvent permission.",
+		"targetKeys": ["groupId", "eventId"]
+	},
 	{
 		"effects": ["state-change"],
 		"input": "json",

package/command-reference.md

@@ -450,6 +450,22 @@ List an event's routing groups, ordered stations, and assigned teams.
 - Input: `--input '<json>'` required
 - Effects: read-only
 
+## `gosh routing-group release-history`
+
+Show a routing group's five most recent release changes with actor, action and before/after UTC values.
+
+- Authentication: browser-authenticated CLI session required
+- Input: `--input '<json>'` required
+- Effects: read-only
+
+## `gosh routing-group release`
+
+Schedule (future releaseAt ISO timestamp with offset), CLEAR schedule, HOLD, RELEASE_SCHEDULED_HOLD (keep schedule), or RELEASE_NOW for a routing group. After a group starts, only HOLD and RELEASE_SCHEDULED_HOLD are accepted. Requires launchEvent permission.
+
+- Authentication: browser-authenticated CLI session required
+- Input: `--input '<json>'` required
+- Effects: state-change
+
 ## `gosh routing-group create`
 
 Create a routing group within an event before play starts.

package/dist/index.js

@@ -7453,6 +7453,14 @@ var typedOperations = {
     kind: "query",
     invoke: (client, input) => client.team.listRoutingGroups.query(input)
   },
+  "team.listRoutingGroupReleaseHistory": {
+    kind: "query",
+    invoke: (client, input) => client.team.listRoutingGroupReleaseHistory.query(input)
+  },
+  "team.updateRoutingGroupRelease": {
+    kind: "mutation",
+    invoke: (client, input) => client.team.updateRoutingGroupRelease.mutate(input)
+  },
   "team.createRoutingGroup": {
     kind: "mutation",
     invoke: (client, input) => client.team.createRoutingGroup.mutate(input)
@@ -7865,6 +7873,7 @@ var defaultMutationTargetKeys = [
   "name"
 ];
 var mutationTargetKeys = {
+  "team.updateRoutingGroupRelease": ["groupId", "eventId"],
   "team.setGameplaySettings": ["eventId"],
   "team.createRoutingGroup": ["eventId"],
   "team.renameRoutingGroup": ["groupId"],
@@ -7985,6 +7994,8 @@ var commands = [
   mutation(["team", "set-station-routes"], "team.setStationRoutes", "Replace a team's linked station route and set its order.", ["state-change"]),
   mutation(["event", "set-gameplay"], "team.setGameplaySettings", "Set open or sequential progression, group routing, and per-mission skipping before play starts.", ["state-change"]),
   query(["routing-group", "list"], "team.listRoutingGroups", "List an event's routing groups, ordered stations, and assigned teams."),
+  query(["routing-group", "release-history"], "team.listRoutingGroupReleaseHistory", "Show a routing group's five most recent release changes with actor, action and before/after UTC values."),
+  mutation(["routing-group", "release"], "team.updateRoutingGroupRelease", "Schedule (future releaseAt ISO timestamp with offset), CLEAR schedule, HOLD, RELEASE_SCHEDULED_HOLD (keep schedule), or RELEASE_NOW for a routing group. After a group starts, only HOLD and RELEASE_SCHEDULED_HOLD are accepted. Requires launchEvent permission.", ["state-change"]),
   mutation(["routing-group", "create"], "team.createRoutingGroup", "Create a routing group within an event before play starts.", ["state-change"]),
   mutation(["routing-group", "rename"], "team.renameRoutingGroup", "Rename an event's routing group before play starts.", ["state-change"]),
   mutation(["routing-group", "delete"], "team.deleteRoutingGroup", "Delete an unassigned routing group before play starts.", ["state-change", "delete"]),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/gosh",
-  "version": "0.13.0",
+  "version": "0.14.0",
   "description": "GOSH CLI for organizers and AI agents — manage organizations, events, teams, stations, missions, templates, and live operations through the GOSH API.",
   "type": "module",
   "main": "./dist/index.js",