feat: discover existing workflow objects

docs/project_map.md

@@ -189,6 +189,11 @@ server state is needed.
 
 Draft workspaces are intentionally not part of `wf_client`. They are a separate
 server/admin surface and must be explicitly enabled when composing a server.
+
+Use `app.artifacts(...)`, `app.deployments()`, and `app.runs(...)` to discover
+existing remote objects as lightweight immutable summaries. Exact loaders
+(`app.workflow(...)`, `app.deployment(...)`, and `app.run(...)`) reconstruct the
+selected rich object without making collection listing eager or trace-heavy.
 - `examples/agent_challenges/` contains reusable opencode challenge harnesses
   for evaluating whether agents can use the public workflow CLI/server path.
 

docs/wf_api_architecture.md

@@ -175,6 +175,12 @@ to server/admin and console callers, but normal server composition keeps draft
 JSON-RPC registration opt-in so artifact, deployment, and run durability do not
 depend on a draft store.
 
+Existing remote objects can be discovered without eagerly loading their full
+plans, bindings, or traces. `app.artifacts(...)` and `app.runs(...)` return
+paged immutable summary rows; `app.deployments()` returns an immutable tuple.
+Call `app.workflow(id, version=...)`, `app.deployment(id)`, or `app.run(id)` to
+reconstruct the selected rich object.
+
 ## WorkflowApiSurface And Domain Services
 
 `WorkflowApiSurface` is the public application contract shared by local and