bun-sticky-zig v1.4.2: Scoring, Verified

Growing Into the Full Range

bun-sticky-zig shipped scoped to 9 applicable slots for a cli-type project — project and human context, the core of a lean dogfood build. faf-cli's own range covers 21 base slots today. Same file, checked at each scope:

Same project.faf, two ranges. v1.4.2 grows bun-sticky-zig into the wider one.

What Changed

• Extended to the full 21-slot range. Every project type is now checked against the same 21 base slots faf-cli uses — growing past the original 9-slot CLI/dogfood scope. 12 enterprise slots activate when a monorepo/enterprise signal is present in the file.
• Tier system consolidated. Three separate tier implementations across the codebase are now one. Retired the old medal-emoji set in favor of the current geometric ladder — 8 tiers, the ✪ proof seal at 100%.
• faf sync checks before writing. faf-cli's own sync inherits the latest authoring — it preserves what's already in your CLAUDE.md and adds FAF context alongside it, never clobbering your words. bun-sticky-zig now honors that same principle: it won't touch a CLAUDE.md unless the file already carries bun-sticky's own signature.
• Every score now discloses what it is. Terminal, JSON, and every card format say it plainly: an approximation of faf-cli's live kernel, not the authoritative number.

Verified, Not Claimed

The extension shipped through the full pipeline — build, test, tag, release, then a real install:

3 platforms built and released — linux-x64, macos-x64, macos-arm64. Then an actual brew upgrade on a live machine, not a dry run: 1.1.1 → 1.4.2, correct architecture, binary confirmed running.

The Numbers

• v1.4.2 - Released August 14, 2026
• 157/157 - Tests passing
• 3 - Platforms (linux-x64, macos-x64, macos-arm64)
• 21 + 12 - Base slots + conditional enterprise slots
• 0 - Runtime dependencies