Add JSDoc documentation to CLI lifecycle functions

[Copilot]

Added missing JSDoc documentation to functions introduced in the launch readiness fixes PR to satisfy documentation coverage requirements.

Functions documented:

• resolveCliAutoShutdown() - Interprets CODEX_CLI_AUTO_SHUTDOWN environment variable with default behavior and supported values ('0', 'false', 'no')
• renderBackgroundDaemonStatus() - Renders daemon status including PID, start time, interface mode/tier
• useSystem() - System lifecycle management with updated options parameter for auto-shutdown control
• UseSystemOptions type - Configuration options for system lifecycle behavior

All documentation follows established JSDoc conventions with @param, @returns, and @remarks tags.

/**
 * Resolves whether CLI should auto-shutdown after command execution by 
 * interpreting the CODEX_CLI_AUTO_SHUTDOWN environment variable.
 * 
 * @returns true if auto-shutdown is enabled, false otherwise
 * 
 * @remarks
 * - Returns true if CODEX_CLI_AUTO_SHUTDOWN is not set or is empty (default behavior)
 * - Returns false if CODEX_CLI_AUTO_SHUTDOWN is '0', 'false', or 'no' (case-insensitive)
 * - Returns true for any other value
 */
function resolveCliAutoShutdown(): boolean { ... }

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Continue Tasks: ▶️ 5 queued — View all

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: df375fbc52

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Revert peer-only flag on direct runtime dependency

The lockfile now marks ws as "peer": true even though the root package declares it in dependencies; Arborist trusts this metadata from package-lock.json, and npm ci/npm install explicitly support --omit=peer to skip peer-typed nodes, so installs in that mode will incorrectly omit ws (and zod in the same commit) from disk. This turns a documentation-only change into a dependency graph regression for environments that use peer omission.

Useful? React with 👍 / 👎.