v0.1.13 - Hydrated normal configuration controls

Changes

• Removed the raw All app fields dump. Normal Configuration controls show the workspace's current values.
• Source toggles recognize configured source types with custom IDs. Named APIs retain their settings in typed source controls.
• Current matching presets are selected; changed looks say Custom. Saved-state selection matches current model settings.
• App-file theme and branding seed values when no saved theme override exists.
• Existing code helpers and saved-key presence show in the usual controls. Empty optional values and missing keys explicitly say not filled. No secret values are returned.
• Extra nested fields use typed controls in their normal sections. Saving source/additional fields requires restart; edits never execute code or contact a service.

Verification

• Exact GitHub source and rebuilt wheel each passed 473 tests: 471 passed, 2 optional skips.
• 17 focused browser hydration scenarios: manual workspace, all theme controls, light/dark colors, presets, custom look, saved states, model/retrieval/budget, named APIs, extra fields, missing/saved keys, helper and prompt fields, restart persistence, custom-field saving, ZIP imported state and mobile.
• Regression browser tests: all nine offline prompt generators, both code routes, YAML/ZIP import, cited Demo answer, stop/remove, traversal rejection and continuous scrolling at 1366/980/760/390 pixels.

Model-dependent tests use Demo/fakes, not a live model. Missing values are not invented; unused services are not enabled automatically. Extra stored fields do not create new runtime capabilities. Imported bundles exclude keys. Python connectors use a bounded process, NOT a security sandbox. A finite test matrix does not cover every possible custom program or API.