Files
treg/examples
UncleCode 1668edb7ea fix(hub): ten fixes from the first hub simulation
Two agents used the hub as a maker and a buyer on a local server; each finding below was checked
against the code or the database before this fix.

- verified-email and lead-pipeline accept only a work email: never a free mail provider, and at the
  input company's domain when one is given. A finder returned a Gmail address for a company's CMO,
  the checker called it valid, and the tool charged its fee.
- A script's price headline shows its cap after the observed range ("$0.0103/run so far · seller
  up to $0.02 a run"): recent runs may all have charged little.
- `treg catalog get` on a hub tool no longer labels the whole run cost "per successful run to the
  maker"; it prints the seller price and, separately, what a run cost a caller.
- After a publish, the CLI's example call uses the tool's own inputs, not a fixed figma.com body.
- `treg hub ls` shows the maker's price and the search state (no / requested / yes / rejected,
  update waits) on the version callers get, marked ◀.
- `treg hub price` on a script says it moved only the cap; the fee is the ctx.charge lines.
- The recipe rules (summary 1-200 characters; the input keys; required, example, int max) are in
  skill.md, llms.txt and the `treg hub init` output.
- A version in `checking` or `review` is never shown on the public views (catalog get, share
  page); before, `catalog get <id>@N` showed an unreviewed summary and price to anyone.
- New `treg whoami`; `treg balance` names the team. `treg whoami` used to run the system whoami
  through `treg with` and print the machine's user name.
- `_kv` keeps a space after a 7-character label ("listingrequested" in `treg hub list`).

Updates docs/context/architecture/hub.md.
2026-09-25 11:04:31 +08:00
..