marketing-cycle: surface refresh (af-50cdad6b)

[stempeck]

marketing-cycle · cycle-2 (bead af-50cdad6b) — Tier A surface refresh

Marketing cycle 2 for the repo. Audited development since v0.1.0, refreshed owned GitHub
surfaces, and staged Tier B drafts for the operator to publish. Flagship (operator-approved,
#93): the web console + its new Telemetry view (per operator direction on #94).

Tier A — in this PR

Three STALE README claims fixed (each source-verified in the audit):

• af version → af --version (the former is not a command)
• "Nineteen formulas ship" → 24 (adds fable-secure, gpt-fable-review, gpt-rootcause-all, multi-agent, marketing-cycle)
• "Included Skills" 3 → 10 (all embedded via //go:embed install_skills/*)

New feature coverage:

• README Observability section + command-reference entries for af telemetry (per-step timing + token/cost usage)
• README Web Console section now surfaces the Floor view and the new Telemetry view
• Lighter coverage of af improvement and multi-provider (af config models, gpt-* formulas)
• CHANGELOG [Unreleased]: telemetry, multi-provider agents, operator-only factory teardown, reliable improvement self-edits, new formulas

Cycle artifacts (committed mode): audit, story, drafts, two live-console screenshots, and the gate log.

Gates passed

• GATE-1 (audit checklist) PASS · GATE-3 (every public claim verified against source, + web-console addendum) PASS
• SELF-REVIEW PASS · SELF-VERIFY PASS (tier law, voice law, privacy mode all upheld)
• go build ./... clean · make test all pass · main is green

Tier B — staged, NOT published (operator publishes)

• Medium (.marketing/cycle-af-50cdad6b-medium.md) — READY (approved as written, MARKETING CYCLE af-50cdad6b: drafts awaiting your edit #94)
• LinkedIn (.marketing/cycle-af-50cdad6b-linkedin.md) — EDITED (your shorter version is canonical)
• Screenshots staged for the Medium piece; the agent never posts externally.

Release recommendation (your call at merge)

I recommend cutting v0.2.0 after this merges, themed observability + multi-provider — the
#92 feature wave (telemetry, multi-provider agents, operator-only teardown, self-improvement) is
substantial and still unreleased, and main is green. This PR itself is docs-only (no product code).

HOLD

Per the runbook I don't merge — you or the supervisor merge. After merge (and the release
decision), I continue to publish support (I prep the mechanics; you click) and then verify every
published page.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

agentfactory seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[stempeck]

Status for your merge decision:

• CI: running (unit, integration, web-unit, regen, supply-chain-lint, toml-conformance, license/cla). I'll confirm here when it's green — please don't merge until it is. Note license/cla may need your sign-off as owner.
• Main health: green at cycle start (make test all passed on origin/main); this branch also builds clean and passes make test.
• Release recommendation: cut v0.2.0 after merge, themed observability + multi-provider (the Run telemetry, operator-only factory teardown, reliable improvement self-edits, multi-provider agents #92 wave is substantial and still unreleased). This PR is docs-only. If you want the release, say so at merge and I'll cut the tag + themed notes from merged main; if not, I'll skip it.

I don't merge — you or the supervisor do. After merge (+ release decision) I move to publish support (mechanics for you to click) and then verify every published page.

[stempeck]

CI update: all real checks are GREEN ✅ — integration, unit, web-unit, regen, supply-chain-lint, toml-conformance all pass.

One blocker, and it's yours to clear: license/cla is pending because the commits are authored by agentfactory <dev@agentfactory.local> (the factory's local bot identity), which the CLA assistant can't match to a GitHub account. I can't sign a CLA or merge — both are operator actions.

Your options:

1. Admin-merge (simplest, since it's your repo and CI is green): gh pr merge 95 --squash --admin
2. Sign/adjust the CLA at the check's link if you'd rather keep the gate satisfied.

Release decision (needed at merge): cut v0.2.0 (observability + multi-provider) — YES/NO? If YES, I'll tag it from merged main with themed notes after you merge.

Holding here until #95 is merged. Then I prep publish support (Medium + LinkedIn mechanics for you to click) and verify the published pages.

[stempeck]

Merged ✅ and v0.2.0 is live: https://github.com/stempeck/agentfactory/releases/tag/v0.2.0 (themed observability + multi-provider). Moving to publish support — I'll prep the Medium rich-text paste vehicle + the LinkedIn text and an ordered publish checklist for you to click, then verify every published page.