You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5ab63ba
Browse filesBrowse the repository at this point in the historyBrowse files
Core v0.19.4 is the fleet floor. Its served-call contract is the one the
harness already implements: runnable/served.go and the protocol constants
are unchanged since v0.6.0, so only the pin moves. The go directive goes
to 1.27.2 for the stdlib fixes `codefly publish` checks with govulncheck.
The agent manifest stays at 0.0.6: the release is cut by `codefly
publish`, not by this change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
The Codefly language agent for typed, finite Python operations: generate a handler, prepare its dependencies, and produce identified native packages and container build recipes.
4
4
5
-
**Status: the generated harness serves call mode on core v0.6.0, and authoring, preparation and packaging run through the real Builder gRPC lifecycle.** A package is a server: one call is a POST carrying the bounded input document, with the caller's Work Context required on it ([docs/protocol.md](docs/protocol.md)). The launcher framing — two document paths in the environment, a result file, an exit code a launcher read — went with the native placement in core#681. Published binaries appear on the [releases page](https://github.com/codefly-dev/runnable-python/releases). [Milestone 3](docs/milestone_3_builder_grpc.md) records the Builder checkpoint and predates the served harness; [issue #1](https://github.com/codefly-dev/runnable-python/issues/1) still tracks durable Kubernetes execution.
5
+
**Status: the generated harness serves call mode on core v0.19.4, and authoring, preparation and packaging run through the real Builder gRPC lifecycle.** A package is a server: one call is a POST carrying the bounded input document, with the caller's Work Context required on it ([docs/protocol.md](docs/protocol.md)). The launcher framing — two document paths in the environment, a result file, an exit code a launcher read — went with the native placement in core#681. Published binaries appear on the [releases page](https://github.com/codefly-dev/runnable-python/releases). [Milestone 3](docs/milestone_3_builder_grpc.md) records the Builder checkpoint and predates the served harness; [issue #1](https://github.com/codefly-dev/runnable-python/issues/1) still tracks durable Kubernetes execution.
6
6
7
7
The review corrections and current validation are recorded in [milestone 2](docs/milestone_2_review_fixes.md). Earlier image/k3d observations are historical and do not qualify the Codefly/Orchestration path.
0 commit comments