feat: publish Obol CLI version for the frontend footer

[HananINouman]

Write obolVersion into obol-stack-config on stack up / tunnel sync and inject OBOL_STACK_VERSION into the frontend pod so the UI can show the running CLI release.

Summary

What changed:

Why it matters:

Risk level:

Commit under test:

Base branch:

Scope

• Code
• Charts / manifests
• Flows / QA scripts
• Docs / skills
• Images / dependencies
• Other:

Validation

CI checks:

Check	Status	Link

Unit tests:

<!-- command, result, commit/SHA -->

Integration tests:

<!-- command, result, commit/SHA -->

Flow tests:

Flow	Network	QA machine label	Worktree	Result	Artifacts

Release smoke:

<!-- command, flags, result -->

Live Chain Evidence

Do not include private keys, seed phrases, passwords, hostnames, personal paths, or raw bearer tokens.

Network:

RPC/provider:

Facilitator:

Contracts and tokens:

Name	Address	Version / notes

Wallet roles:

Role	Address	Source
Alice / seller / register
Bob / buyer / payer
Facilitator / receiver

Balances:

Token	Address	Before	After	Expected delta	Actual delta

Transaction receipts:

Purpose	Tx hash	From	To	Amount / event	Status
ERC-8004 registration
Metadata / service offer
Approval / permit
Purchase request
Settlement transfer

Runtime Evidence

QA environment:

Item	Value
OS / arch
Backend
Tool versions
QA agent/model

Images:

Component	Image	Tag / digest	Source

Kubernetes / stack:

Item	Value
Stack IDs
Namespaces
Pod readiness
Cleanup result

Model and routing:

Item	Value
Agent/model used
LiteLLM route
Paid endpoint status
Auth token source

Artifacts and logs:

Artifact	Location / link	Notes

Demo readiness:

Item	Status	Notes
Seller visible / registered
Buyer discovery works
Paid route works
Settlement visible on-chain

Review Notes

Known gaps:

Follow-ups:

Reviewer focus: