chore: report 0.2.0, the version --ttl actually shipped in

[ProJedi1234]

--ttl (#2) added a flag to publish and left SteleVersion.current at 0.1.0. Two binaries with different command surfaces therefore both identify as stele-cli/0.1.0 — and that string is exactly what the server's 426 gate compares, so the drift is invisible to the one mechanism built to catch it.

The concrete failure: an install predating #2 answers stele publish --ttl with an unknown-flag error while reporting the same version as an install that supports it. I hit this on my own machine before noticing the cause.

What changed

One line. SteleVersion.current is the only version literal in the repo, and all five test assertions interpolate it rather than hardcoding a string, so nothing needed updating in lockstep.

What deliberately did not change

minimumCLIVersion on the server stays at 0.1.0. This is an additive change — a 0.1.0 client is still correct, it just has no --ttl. Raising the floor would answer 426 to every installed client to prevent drift that does no harm.

Nothing on the server side needed touching at all: its version literals are parser fixtures (stele-cli/0.1.0 as a parse input, stele-cli/0.0.1 as the outdated case) and its gate tests derive relatively from minimumCLIVersion.

Verification

• 110 CLI tests pass
• scripts/integration-smoke.sh against a real server on a virgin database: 72/72, driven by the installed 0.2.0 binary rather than --bin

That last detail is the point — it proves the bumped version is not gated, rather than asserting 0.2.0 >= 0.1.0 and hoping.

Still open

This repo has no tags and no release automation, which is how --ttl shipped under 0.1.0 in the first place. The bump is a hand-edit nothing reminds you to make. Worth closing separately — either a CI check that fails a PR touching Sources/ without touching Version.swift, or real tagged releases.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E3vBKBewMwmbCo5VxBLrmA

Summary by CodeRabbit

• Chores
  • Updated the application version to 0.2.0.
  • User agent information now reports version 0.2.0.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: e1cd2205-a523-45a4-80cf-ec252b4f2a1a

📥 Commits

Reviewing files that changed from the base of the PR and between 6bd53ee and aa5fa32.

📒 Files selected for processing (1)

• Sources/SteleKit/Version.swift

---

📝 Walkthrough

Walkthrough

The change updates SteleVersion.current from 0.1.0 to 0.2.0. The derived userAgent reports the updated version.

Changes

Version Metadata

Layer / File(s)	Summary
Update public version Sources/SteleKit/Version.swift	SteleVersion.current now returns 0.2.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A rabbit hops through version cheer,
“Zero point two point oh is here!”
The user agent wears its badge,
With carrots packed inside its cache.
Hop, hop—metadata is clear!

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}