Implemented features and verification¶
The current implementation provides the following capabilities. The verification column identifies the acceptance evidence that must remain green; it does not claim a successful release or validation on an operating system without a run.
Version 0.5.0 integrates lclang 1.1.0 configuration composition, configurable verbose scopes and native exception reports. Version 0.4.0 added synchronous HTTP exception callbacks and native local/UTC log timezone selection.
| Capability | Contract and evidence |
|---|---|
| Managed background workers | Code-only callables on dedicated threads/loops, service bridges, restart/shutdown, dedicated logs and controller events; unit and native-process tests. |
| Uncaught HTTP exceptions | Typed synchronous/asynchronous callbacks, native compact/full exception trees and generic 500 fallback; response, precedence, cause/group, streaming and logging-failure tests. |
| Scoped configuration Frames | use_lcl_frame() derives and owns nested task-local Frames; behavioral tests verify inheritance, restoration, concurrency and cancellation. |
| LCL configuration and typed application | Native Module composition, isolated import namespaces, optional introductions, lazy required/runtime values, portable defaults and CLI precedence; configuration and application behavior tests. |
| Request context and logs | Server-generated lclang Snowflake IDs, response headers, isolated context, and separate controller/worker upstream logging with lifecycle observations. Upstream clock/sequence failures return 503 without an ID and record one failure access log. |
| Native verbose diagnostics | CLI --verbose and its protected __verbose__ binding reach downstream expressions, lifespan, requests, Workers and playground traces; disabled/enabled, handoff, local-silencing and native reload tests. Logging practices execute exact example source and show captured logs. |
| Focused service logs | Paired multiline REST start/completion trees with IDs and connection context, concise controller headers, and FastAPI/Starlette frame filtering in native reports; response, metadata privacy, original traceback/group preservation and captured-log tests. |
| Native log timezones | Local timestamps by default or explicit UTC through configuration/CLI, shared by controller/API/background logs; deterministic timestamp and configuration tests. |
| Windows and Linux service runtimes | Uvicorn with Winloop and Gunicorn respectively; real-process tests run separately on each platform. |
| Development Python reload | serve -o hot_reload, explicit recursive server.reload_dirs, one effective worker, graceful native replacement, and cross-platform process tests. |
| Local operational CLI | Downstream pyproject entrances, native CLI configuration overrides and dry-run; fixed JSON status and observed active log paths, identity validation, token-authenticated graceful stop. |
| Health and offline API documentation | Nonblocking sampled system metrics and bundled Swagger UI resources. |
| Deployment configuration rendering | Nginx and systemd text output; deterministic renderer and executable guide tests. |
Windows and Linux CI exercise the process lifecycle independently. The initial release's implementation PR checks retain its acceptance evidence; review the quality workflow for later revisions. The acceptance plan maps each area to its maintained reference contract. The authoritative full gate and aggregate 100% production branch coverage remain requirements for every completed change.
The independently authored minimal and composed downstream projects have passed local Windows checks against an installed wheel. Eight GitHub Actions jobs validate all four projects on Windows/Uvicorn and Linux/Gunicorn in isolated environments. Their full API/CLI and cleanup checks must pass on the final PR head. All projects are excluded from the wheel.
The framework does not implement authentication systems, a management service, HTTP log streaming, configuration watching, or deployment commands.
The from-scratch catalog guide teaches an independent read-only service. Its documentation test extracts the exact application, configuration, and verifier from Markdown, runs native workers, checks HTTP behavior and request logs, stops gracefully, and verifies deployment rendering.
The Build a service series adds independently installed directory-monitor and playground applications with bundled static UIs. Their verifiers cover recursive SSE updates, file APIs, session isolation, AST/dependency inspection and native evaluation replay.
The browser tutorials provide every source file to build from an empty directory. The playground also ships reusable, dependency-free LCL highlighting JavaScript and CSS for static code or native textarea overlays, with escaped source rendering.