Add delete publish

[SpontaneousOverthrow]

No description provided.

[piotr-iohk]

Nitpick: but maybe publish/get/delete would be more natural order of operations

[piotr-iohk]

Some review feedback from Codex:

🍒 Key feedback

Repeated sign‑in / sign‑out pattern isn’t resilience-friendly

In all three helpers (publish_data, delete_data, get_data) the session is torn down only on the “happy path”. If storage.put/get/delete throws, you’ll skip the signout() call. Consider wrapping the signout in a match/finally block or call it in a drop guard so the session always gets closed.

Path validation

storage.put/delete/get expect an absolute Pubky path. Right now the CLI just forwards the string verbatim. It’d be safer to run it through PubkyResource::parse / ResourcePath::parse (or at least validate the /pub/... prefix) so users get a nice error rather than the SDK error.

get assumes UTF-8 text

.text() forces UTF-8; any binary file (even Lightning backups) will panic. You’ll probably want to stream bytes and either dump stdout as-is or add --outfile. Until then, document that this command is text-only.

CLI UX details

• The argument descriptions say “Path to file /pub/test.txt” but don’t mention the requirement for absolute paths.
• For publish, we probably want a --mime or at least to accept stdin so users don’t need a temp file (optional but worth thinking about).
• get currently prints the fetched data alongside session diagnostics, which means piping to another command will pick up those logs. Maybe gate the diagnostic prints behind a --verbose.
• Overall the feature is a good addition; just tighten up the validation, cleanup behavior, and test coverage. The binary’s new functionality will then be much safer to rely on.

[SpontaneousOverthrow]

I guess that's fine for the MVP

[SpontaneousOverthrow]

we can also move the session creation/destroy to separate functions, but this is for refactor.