services.shared

The implementations behind the services.* tools. They wrap the service asset type (asset.resolve(name, "service")) so the tools stay thin and an agent never has to resolve or invoke a service directly.

• discover — list enumerates available services with fully-described operations; balance reads credits; caps reads the caps in force, the refusals a later generation would meet the same way.
• start — generate resolves the service and invokes it, returning a handle.
• track — status / jobs read the in-flight run records a generation mirrors into /zero/source/tmp/services/<id>.json; outputs reads the durable provenance stamped on each produced asset (the run records aren't synced and vanish on restart — the asset stamp is what survives).