[1.0] Add an application-factory entry point and deterministic onboarding flow

A working server command needs a simple way to run a user's own Flock application and demonstrate the full typed-artifact path without requiring model credentials.

Scope

• Allow the CLI to load an explicitly configured, trusted Python application factory using the existing server composition.
• Provide one maintained deterministic example: publish typed input, run two independent producers, join their results and inspect a controlled failure.
• Show the same application through API and dashboard, with an optional existing LLM engine path.

Acceptance criteria

• From a fresh installation, the documented commands load the factory and produce the expected typed output without an API key.
• The input, joined result and controlled failure can be inspected through the application API and dashboard.
• Invalid factory references produce clear startup errors; complex input uses the JSON fallback.

Boundaries

Do not load executable application code from an untrusted HTTP request or import bundle. No new authoring DSL.

References

• Implementation dependencies: #435, #438.
• src/flock/cli.py
• src/flock/orchestrator/server_manager.py
• examples/01-getting-started/01_declarative_pizza.py

Start with src/flock/cli.py and src/flock/orchestrator/server_manager.py, then inspect examples/01-getting-started/01_declarative_pizza.py and the implementation dependencies in #435 and #438. A fresh installation should load a trusted factory, run the deterministic typed-artifact flow without an API key, expose its input, joined result, and controlled failure through the API and dashboard, and report clear errors for invalid references.