IRIS CLI v1.2.1 — Fix bloqs create silent failure

[mayoalexander]

Summary

• Fix bloqs create/get/ingest using wrong API route (/users/ → /user/), causing 404s that appeared as silent "Failed" with no error detail
• Stop spinner before displaying error messages so they're actually visible
• Parse create response correctly (data.bloq not data directly)

Fixes #59970 — reported by external user (Patsy Keegan)

Test plan

• iris bloqs create --name "Test" — creates successfully, shows ID and name
• iris bloqs list — lists bloqs correctly
• Build passes typecheck

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR aims to fix IRIS CLI Bloqs commands that were failing due to incorrect API routing and poor error visibility, but it also introduces several new CLI features (OBS control, iMessage utilities, and Events production checks) and accompanying regression tests.

Changes:

• Fix Bloqs create/get/ingest endpoints to use /api/v1/user/{id}/... and ensure API errors are shown after stopping spinners.
• Add shared iMessage + contact resolution libraries and expand iMessage CLI capabilities (search improvements, chat name resolution, vCard extraction).
• Add new operational tooling (OBS CLI + Events preflight/audit/production commands) and new regression test suites.

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
packages/opencode/src/cli/cmd/platform-bloqs.ts	Fix Bloqs API routes and stop spinner before rendering API error details.
packages/opencode/package.json	Bump CLI version to 1.2.1.
packages/opencode/src/cli/cmd/platform-run.ts	Enhance array item display (calendar summary + start time) and add calendar integration functions.
packages/opencode/test/cli/bug-fixes.test.ts	Add tests for calendar event label + start time parsing logic.
packages/opencode/test/platform/bug-regressions.test.ts	Add broad regression suite asserting fixes across multiple platform commands.
packages/opencode/src/cli/lib/imessage.ts	New shared sqlite-based iMessage access utilities + vCard extraction.
packages/opencode/src/cli/lib/contacts.ts	New shared lead-name resolution + caching for phone/email identifiers.
packages/opencode/src/cli/cmd/platform-imessage.ts	Refactor to shared libs; add --since, lead resolution, chat labeling, and contacts subcommand.
packages/opencode/src/cli/cmd/platform-leads.ts	Add alt-email support in lead create; reuse iMessage availability checker in health checks.
packages/opencode/src/cli/cmd/platform-doctor.ts	Reuse shared iMessage availability checker for Full Disk Access check.
packages/opencode/src/cli/cmd/platform-customer.ts	Switch iMessage DB querying to shared lib.
packages/opencode/src/cli/cmd/platform-atlas-comms.ts	Switch iMessage ingestion to shared lib helpers.
packages/opencode/src/cli/cmd/platform-obs.ts	New OBS control command suite (bridge-based) including dashboard share/open helpers.
packages/opencode/src/index.ts	Register new obs command in the CLI.
packages/opencode/src/cli/cmd/command-groups.ts	Categorize obs command for grouped help.
packages/opencode/src/cli/cmd/platform-events.ts	Expand Events tooling: push metadata pass-through, tickets push --force, preflight/audit commands, and production subcommand registration.
packages/opencode/src/cli/cmd/platform-events-production.ts	New production subcommands (overview/runsheet/checklist/budget) stored in event metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

searchByHandle() interpolates search directly into the SQL LIKE '%${search}%' without escaping single quotes. If handle is an email/chat identifier containing ', the query will break (and could be leveraged for SQL injection inside sqlite). Escape ' as '' (as you already do elsewhere) before building the SQL, or parameterize the query.

[Copilot]

contactName resolution uses digits || args.query, but digits is derived from the original query. If the query is a lead name that gets resolved to a phone/email (lines 35-58), digits will still be empty and you'll end up resolving by the name string instead of the resolved identifier. Track the resolved identifier (e.g. resolved phone/email) and pass that into resolveContactName(...) so the displayed sender label matches the chat handle actually queried.

Suggested change

	// Resolve contact name from leads (#58888)
	const contactName = await resolveContactName(digits || String(args.query)) ?? "Them"
	// Resolve contact name from the actual identifier used for the query (#58888)
	const contactName = await resolveContactName(resolvedIdentifier) ?? "Them"

[Copilot]

The --share path builds an osascript command string using execSync(...) and interpolates both handle (user input) and msg into a single-quoted shell command. This is vulnerable to shell/AppleScript injection (e.g. a handle containing ' breaks quoting) and can also fail on normal characters. Use execFileSync("osascript", ["-e", script]) (no shell) and escape values for AppleScript (or pass them as arguments) rather than concatenating into the command string.

[Copilot]

The iMessage health check treats any isAvailable() === false as status: "no_permission" with a Full Disk Access hint. isAvailable() also returns false on non-macOS and when the DB file doesn't exist, so this will misreport the failure mode (e.g. Linux users will be told to enable Full Disk Access). Consider branching on process.platform !== "darwin" / missing DB separately (e.g. status: "error" with "macOS only" / "Messages DB not found") and reserve no_permission for actual permission errors.

[Copilot]

File header says “All data in metadata.production”, but the implementation also reads event.metadata.production_timeline / local.data.metadata.production_timeline as a separate top-level metadata field. Either move that timeline under metadata.production (to match the statement) or update the comment so it accurately describes where production data lives.

Suggested change

	// All data in metadata.production (no new tables)
	// Production data lives in metadata.production; timeline data may also be read
	// from metadata.production_timeline (no new tables)

[Copilot]

isAvailable()/query() use execSync() with a shell command string (e.g. sqlite3 "${MESSAGES_DB}" "${escaped}"). Because the SQL text can include user-derived values in callers, shell expansions like $(...)/backticks can be evaluated before sqlite3 runs, creating a command-injection risk and also making quoting brittle. Use execFileSync/spawnSync with an argument array (no shell) and pass the SQL as a separate argv element or via stdin; also consider rejecting/escaping characters like $ and backticks if any user input can reach SQL.

[Copilot]

ImessageReadCommand uses args.since to compute cutoffSeconds, but the command builder never defines a --since option. As written, --since won't be recognized by yargs and the new logic is effectively dead code. Add the .option("since", ...) to the builder (matching search/chats) or remove the args.since branch here.

[Copilot]

exec(open "${openUrl}") executes through a shell and openUrl is derived from network sources (ngrok API) and local IP detection. If the URL ever contains quotes or shell metacharacters, this can lead to command injection or just broken behavior. Prefer execFile/spawn with args (e.g. open, [openUrl]) so the URL is passed as a single argument.

Suggested change

	const { exec } = await import("child_process")
	exec(`open "${openUrl}"`)
	const { spawn } = await import("child_process")
	spawn("open", [openUrl], { detached: true, stdio: "ignore" }).unref()

[Copilot]

In search, when a non-phone query resolves to a lead email (lines 54-58), normalized is updated but whereClause still uses args.query in the non-phone branch. That means the email resolution has no effect on the actual SQLite query (it still searches for the original name string). Use the resolved identifier (normalized) in the LIKE clause for the non-phone case as well (with proper SQL escaping), or introduce a separate searchHandle variable that always reflects what you’re querying for.

Suggested change

	: `c.chat_identifier LIKE '%${args.query.replace(/'/g, "''")}%'`
	: `c.chat_identifier LIKE '%${normalized.replace(/'/g, "''")}%'`

[Copilot]

--since is parsed via new Date(String(args.since)).getTime() without validating the result. If the user passes an invalid date (or a timezone-less string that parses unexpectedly), getTime() becomes NaN and you’ll emit unixepoch('now') - NaN in SQL, which fails with a confusing sqlite error. Validate Number.isFinite(ts) and surface a clear error (and non-zero exit code) when --since can’t be parsed.

Suggested change

	const cutoffSeconds = args.since
	? Math.max(0, Math.floor((Date.now() - new Date(String(args.since)).getTime()) / 1000))
	: (args.days as number) * 86400
	let cutoffSeconds = (args.days as number) * 86400
	if (args.since) {
	const ts = new Date(String(args.since)).getTime()
	if (!Number.isFinite(ts)) {
	prompts.log.error(`Invalid value for --since: "${String(args.since)}". Please use a valid date/time.`)
	process.exitCode = 1
	prompts.outro("Done")
	return
	}
	cutoffSeconds = Math.max(0, Math.floor((Date.now() - ts) / 1000))
	}