Add OutageDeck CLI package

[koko3tallah]

Summary

• What changed: adds a reproducible pkgx recipe for outagedeck/cli, built from the tagged source with CGO disabled and the package version injected into the CLI binary.
• Why: makes the zero-key OutageDeck cloud and SaaS status CLI available through pkgx's one-command install and execution flow. I maintain and represent OutageDeck.

AI Intent

• Prompt or task statement: distribute the OutageDeck CLI through appropriate package-manager channels without changing the product repository.
• Scope of AI-assisted changes: one new projects/outagedeck.com/package.yml recipe and its build, audit, test, and CI-matrix validation.

Risk Assessment

• Risk level: low
• Primary risks: upstream tag/source-layout changes, Go toolchain compatibility, or a version linker variable change could break a future package build.
• Compatibility impact: the recipe uses the pantry's default Linux and macOS matrix on x86-64 and ARM64, builds a static Go binary with CGO_ENABLED=0, and introduces no runtime dependencies.

Rollback Plan

• Revert path: revert this commit or remove projects/outagedeck.com/package.yml.
• Forward-fix path (if revert is not possible): pin or adjust the Go dependency range, source layout, linker variable, or tests in the recipe.

Validation

• Local checks run:
  • bk build --clean for OutageDeck CLI v0.1.0 — passed from the tagged source
  • bk audit — passed
  • bk test — passed; verifies the exact version and stable help banner
  • repository CI planner — produced Linux and macOS x86-64/ARM64 jobs
  • git diff --check — passed
• CI checks expected: the pantry's standard build, audit, and test matrix for all four default platforms.

Internal/Public Boundary Check

• No internal-only data, private URLs, secrets, or private runbooks were added.

[jhheider]

i'm not against adding OutageDeck's cli, @koko3tallah , but a few things give me pause:

• this is a sole contributor, zero star, zero fork project, with a repo created today, with 7 commits, all unsigned.
• the providerURL() function includes tracking variables.

func providerURL(slug string) string {
	return "https://outagedeck.com/providers/" + url.PathEscape(slug) +
		"?utm_source=cli&utm_medium=terminal&utm_campaign=cli_distribution"
}

those things together give me concerns about supply-chain risk. i'm happy to keep this PR up, and keep an eye on your project. if demand surfaces, or interest, i'll happily add it.

[koko3tallah]

Thanks for the concrete feedback. I addressed the tracking concern at the source in outagedeck/cli v0.1.1: provider URLs emitted in terminal and JSON output are now canonical and contain no query parameters, with a regression test enforcing that behavior.

Release/change: https://github.com/outagedeck/cli/releases/tag/v0.1.1

I understand this does not resolve the separate maturity and independent-adoption concern. I am leaving this draft as requested; no action is needed from you.

[jhheider]

thanks for the quick response. hopefully, outagedeck is insanely successful, and i feel foolish for my caution. ;)