Start 0.7 development cycle

[omry]

Bump the repository development version from 0.6.0.dev1 to 0.7.0.dev1 so local binaries and package builds report the next development series.

---

Stack created with Sapling. Best reviewed with ReviewStack.

• Normalize controlled-session protocol and add client readiness #46
• -> Start 0.7 development cycle #45
• Compose current controlled sessions #43
• Prove controlled-session network isolation #42
• Integrate controlled-session networking #41
• Persist controlled-session network ownership #40
• Add controlled-session network adapter #39
• Plan controlled-session networking #38
• Retry controlled-session watchdog cleanup #37
• Persist controlled-session crash receipts #36
• Fail closed when session watchdog exits #35
• Launch controlled-session watchdog #34
• Prepare controlled-session cleanup manifest #33
• Record controlled-session resource ownership #32
• Prove controlled-session lifecycle in Docker #31
• Supervise controlled-session lifecycle #30
• Bridge controlled-session controller and workload I/O #29
• Add Docker controlled-session controller adapter #28
• Add Docker workload PTY adapter #27
• Add private controlled-session channel #26
• Freeze controlled-session execution plans #25
• Add bounded controlled-session PTY draining #24
• Enforce controlled-session output finalization #23
• Verify sandbox state on the execution thread #22
• Preserve base identity in direct installs #21
• Run application sandbox integration in CI #20
• Add controlled-session lifecycle state machine #18
• Add controlled-session framed protocol #17
• Define controlled-session authorization #16
• Make queued admission cancellation deterministic #15
• Enforce coarse application network policy #14
• Protect host system trees from runtime binds #13
• Enforce root host filesystem boundary #12
• Add container-local runtime identities #11
• Verify application sandbox at startup #10
• Harden application container identity and kernel policy #9
• Unify application sandbox planning #8
• Document controlled sessions and repositories #7

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 36f884dd7a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add a release-note fragment for the version bump

Because VERSION is embedded in native binaries and Python wheel metadata, changing the reported development series is user-facing, but this commit adds no Changie fragment under .changes/unreleased/; add a Changed fragment so the 0.7 development release notes record the change as required by the repository guidance.

AGENTS.md reference: AGENTS.md:L9-L10

Useful? React with 👍 / 👎.

[Copilot]

Pull request overview

This PR starts the 0.7 development cycle by bumping the repository’s development version so locally built binaries and package builds report 0.7.0.dev1.

Changes:

• Update the root VERSION file from 0.6.0.dev1 to 0.7.0.dev1.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.