Global app/library versioning standard and tickets

Established the approved shared-library lifecycle, semantic versioning, appearance/profile requirements, isolated implementation artifacts, and evidence-scoped canonical tickets so future app adoption has an owner, test, publication, and rollback path.

Scope

• Work host: rdmbair15m5.
• Canonical issue records: rdmsm4x:/Users/richh/dev/issues.
• Canonical source target inspected but not modified: rdmsm4x:/Users/richh/dev/lib/ecs0lib.
• No app repository, installed app, signing identity, managed provider state, or fleet profile destination was modified.

Exact local files created or updated

• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/GLOBAL-APP-CAPABILITY-STANDARD-v1.md
• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/ecs0lib-versioning-8f3f95a.patch
• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/SUBAGENT-LIBRARY-VERSIONING-REPORT.md
• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/RECENT-WORK-TICKET-LEDGER-2026-08-30.md
• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/REBOOT-SAFE-CHECKPOINT-2026-08-30-1529.md
• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/work/ecs0lib-versioning-subagent commit 8f3f95a24b92fea3573835500fbd7e4d8eb5fc69.

Canonical tickets created

• FEAT-20260830-41, TASK-20260830-02, UI-20260830-01, DOC-20260830-02, SEC-20260830-01.
• FEAT-20260830-42, TASK-20260830-03, SEC-20260830-02, SEC-20260830-03, TASK-20260830-04, UI-20260830-02.
• Each ticket is a child of existing EPIC-20260830-02; no duplicate epic was created.

Commands and verification

• Searched the canonical ticket registry before filing overlapping work.
• Used /Users/richh/bin/ticket open through a login shell on rdmsm4x; the tool generated canonical Markdown and HTML for each ticket.
• Versioning sub-agent ran swift test --sanitize=thread: 123 tests, zero failures, no reported data race; one pre-existing mutable-variable compiler warning remained.
• Root rechecked patch SHA-256 d6ebeb0db595c8271bc569e0f129cb723870099f9696f0116b94397fe807b91a, ran git diff --check, and parsed all new JSON schemas/manifests with jq empty.
• Protected dev.ecs0.net ticket URLs returned Cloudflare Access sign-in pages. This verifies routing only; authenticated page content/hash verification remains pending.
• Read-only fleet audit found ~/lib/terminal_color_profiles/manifest.json absent on all six hosts; no deployment was attempted.

Backups and undo

• Both implementation efforts are isolated commits and patch files. Undo locally by deleting the isolated clones and output artifacts only after canonical acceptance or explicit owner direction; no canonical code rollback is needed because canonical source was not modified.
• Ticket records are additive and should not be deleted. If superseded, comment with the replacement and resolve them with evidence.
• No profile deployment or installed-app mutation occurred, so there is no fleet rollback action.

Outstanding owner actions

• Canonical owner must review the two patches in a dedicated clean worktree, rerun full tests, and decide the release version.
• Reconcile pre-existing dirty documentation files before generating or publishing the library status page.
• Authenticated publication verification must bind served content hash to the accepted source commit.
• App owners must resolve architecture, signing, bundle identity, dependency/version source, and one-writer worktree before canaries.
• Fleet control must stage and verify profile deployment on every host with backups and hashes.
• Managed-context owner must integrate and verify the v1.1 pointer for Claude, Codex, and agy; provider state must remain host/account-local.