roboshed 0.1.0a3__tar.gz

roboshed-0.1.0a3/.gitignore

@@ -0,0 +1,50 @@
+# Python bytecode
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Virtual environments and local configuration
+.venv/
+venv/
+.env
+.env.*
+!.env.example
+
+# Tests, coverage, and static analysis
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+junit.xml
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.pyright/
+.hypothesis/
+.tox/
+.nox/
+
+# Packaging and generated documentation
+build/
+dist/
+wheels/
+*.egg-info/
+.eggs/
+site/
+
+# Editors and operating systems
+.idea/
+.vscode/
+.VSCodeCounter/
+*.swp
+*.swo
+*~
+.DS_Store
+Thumbs.db
+
+# Robozium local runtime output
+rbz_data/
+worktrees/
+
+# CI diagnostics
+reports/

roboshed-0.1.0a3/CHANGELOG.md

@@ -0,0 +1,96 @@
+# Changelog
+
+## Unreleased
+
+## 0.1.0a3 - 2026-09-10
+
+- Breaking: replace the public Shed `Workspace` and `Project` primitives with a
+  single `Sandbox`. Configure tier and persistence paths once, derive the policy
+  with `sandbox.permissions(project_slug)`, and pass the sandbox plus slug to
+  RoboSprawl deployment factories. Import `Sandbox` and the standalone
+  `PermissionPolicy` from `roboshed.sandbox`. The tiered permission behavior is
+  unchanged.
+
+## 0.1.0a2 - 2026-09-09
+
+- Treat wildcard characters in project and workspace names literally when
+  deriving permissions, preventing writes from extending into other directories.
+- Keep dependency health scheduling alive after observation failures and allow
+  a stopped scheduler task to restart, with sanitized diagnostics. Infer checker
+  registrations from the first dependency for each ID, matching core binding.
+
+- Allow `RoboSprawl.librarian_capabilities` to configure maintenance per project
+  and recursive foreground names. The default remains snapshots, consolidation,
+  retention, and a 120-second cadence, in that order.
+
+- Add the `robosprawl` orientation skill following PeffaHub’s hub, Librarian, and HUD guidance. Resolve actual paths separately through `RoboSprawl.project_context`; obsolete safe-script behavior is omitted.
+
+- Configure `RoboSprawl` with a capability sequence and project instruction template; permission factories bind during each recipe invocation, so consumers need no configuration callbacks.
+
+- Move `ModelSelector` from `roboshed.deployments.models` to
+  `roboz.llm.endpoints`, also exported by `roboz.llm`. Update imports; selection
+  behavior is unchanged. See `docs/context-migration.md`.
+
+- Move registration and binding from `roboshed.dependencies.contract` to
+  `roboz.dependencies`, and health checks from `roboshed.dependencies.health` to
+  `roboshed.dependency_health`. Update imports to these paths; the former
+  dependency package is removed. See `docs/context-migration.md`.
+
+- Add the `RoboSprawl` deployment recipe: consumers select project capabilities and models while shared composition derives project instructions, recursive agent names, and Librarian maintenance. Host-specific instructions and interaction channels remain explicit inputs.
+
+- Derive standard workspace boundaries with `Project.permissions`: workspace reads, project writes, confirmation for shared writes, and denial elsewhere. No application permission factory is needed.
+
+- Add recipe-driven `DeploymentFactory`, reusable `RunFactory` and model selection, isolated dependency inspection, and exact registrations with safe health monitoring. Recipes explicitly own dependency reuse; construction starts no agents or background tasks.
+
+- Breaking: move email input models into `roboshed.tools.email.inputs`; they
+  remain exported from `roboshed.tools.email`. Remove `roboshed.assistant`,
+  `roboshed.demo`, and the `roboz-demo` command. Compose file agents directly
+  from `AgentDefinition` and Shed capabilities; see `docs/agent-factories.md`.
+
+- Breaking: compose the Librarian through its `capabilities` argument, like the
+  orchestrator. Public `ConversationSnapshots`, `MemoryConsolidation`,
+  `ArtifactRetention`, and `MaintenanceCadence` live in `roboshed.capabilities`.
+  Move project inputs and `LibrarianTuning` settings to the relevant capability;
+  the aggregate tuning class is removed. See `docs/agent-factories.md`.
+
+- Breaking: capabilities pass configured endpoints directly to their tools,
+  falling back to the agent's model when unset. Librarian snapshotting and
+  consolidation can use separate models. Use `librarian(agent_endpoint=...)`
+  for a shared default, with `endpoint` overrides on `ConversationSnapshots`
+  and `MemoryConsolidation`. Its special `endpoint_factory` argument
+  is removed; endpoints and runtime cancellation remain independent inputs.
+  See `docs/agent-factories.md`.
+
+- Add `roboshed.deployments.robosprawl.AgenticFactory` to bind project persistence, initial memory, and background-start capabilities to configured definitions. Builds return `RoboSprawlBundle(agent, background_agents)`, a named tuple for direct invocation and host cancellation; construction starts no threads. See `docs/agent-factories.md`.
+
+- Breaking: own orchestrator/Librarian presets, workspace/project structure, reusable capabilities, and memory/summarization tools. Import presets from `roboshed.agents`, feature implementations from `roboshed.capabilities`, and explicit paths/permission inputs from `roboshed.workspace`. Both presets return `AgentDefinition`; the orchestrator remains available across tasks until asked to stop. Preset extensions use only `capabilities`; move separate tool/skill inputs into capability builds. See `docs/agent-factories.md`.
+
+- Breaking: rename the distribution from `roboz-shed` to `roboshed` and the import namespace from `roboz_shed` to `roboshed`. Update dependency declarations and imports. No compatibility package is provided.
+
+### Added
+
+- Compact active conversations with configurable continuation prompts, context thresholds, cancellation, and optional per-attempt timeouts.
+
+### Changed
+
+- **Breaking:** Replace specialized tool contexts with `roboz.Ctx(**values)`
+  and use service/executable resources directly. Existing builders retain their
+  defaults and guard behavior. See `docs/context-migration.md` in the repository
+  for the low-level API migration.
+
+- Document Shed's agent-facing tools under the shared docstring contract.
+
+### Fixed
+
+- Reject relative project persistence paths that escape through traversal or
+  symlinks. External logs, snapshots, and memory require explicit absolute paths;
+  see `docs/agent-factories.md` for migration guidance.
+- Skip conversation files with invalid UTF-8 during snapshot processing without
+  modifying the source or preventing valid conversations from being summarized.
+- Direct targeted reads in file-editing guidance to the configured command tool.
+
+- Preserve conversation history when compaction cannot produce a replacement within its context budget, and report current usage and headroom after successful compaction.
+
+## 0.1.0a1
+
+Initial independently installable package. See README for capabilities and setup.

roboshed-0.1.0a3/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

roboshed-0.1.0a3/PKG-INFO

@@ -0,0 +1,141 @@
+Metadata-Version: 2.5
+Name: roboshed
+Version: 0.1.0a3
+Import-Name: roboshed
+Summary: roboshed: optional building blocks for Roboz
+Project-URL: Repository, https://github.com/Tachion-Oy/roboz
+Author: Tachion Oy
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Requires-Dist: pydantic>=2.12.4
+Requires-Dist: roboz<0.2.0,>=0.1.2.dev2
+Description-Content-Type: text/markdown
+
+# roboshed
+
+Reusable agent factories, capabilities, sandbox policies, tools, and skills built on Roboz. Version `0.1.0a1`
+is alpha; APIs may change before 1.0. Dependencies are Roboz and Pydantic only.
+
+Includes guarded Unix file commands, Python patch editing, CLI/file/email
+instructions, and provider-neutral email contracts and tools. It does not
+install any model SDK, Proton, document SDK, web service, or backend framework.
+
+```python
+from pathlib import Path
+from roboz import stop
+from roboz.deployment import AgentDefinition, Capability
+from roboz.llm import MockLLMEndpoint
+from roboshed.capabilities import FileCommands, FileEditing
+from roboshed.sandbox import PermissionPolicy
+
+permissions = PermissionPolicy.local(Path("./sandbox"))
+agent = AgentDefinition(
+    name="file_worker",
+    system_prompt="Complete the user's task, then call stop.",
+    agent_endpoint=MockLLMEndpoint([
+        {"action": "stop", "rationale": "done", "value": "Ready."}
+    ]),
+    capabilities=(
+        Capability(tools=(stop,)),
+        FileCommands(permissions),
+        FileEditing(permissions),
+    ),
+).build()
+result, messages = agent.invoke()
+```
+
+`roboshed.capabilities` provides `FileCommands`, `FileEditing`, `Compactification`,
+`ConversationSnapshots`, `MemoryConsolidation`, `ArtifactRetention`, and
+`MaintenanceCadence`, alongside the `tools` and `skills` modules. Applications
+choose and configure these capabilities through the presets’ single `capabilities`
+extension argument. A capability owns its tools and any skills used for instructions. `roboshed.deployments.robosprawl`
+provides project composition. `roboshed.agents` supplies the reusable
+orchestrator/Librarian presets. Generic definitions and
+capability contracts live in `roboz.deployment`. Each capability
+builds its tools with explicit endpoint overrides or the agent's default.
+Runtime controls remain separate from endpoints. The Librarian accepts an ordered
+`capabilities` sequence. Snapshot and consolidation capabilities each expose an
+`endpoint`; `agent_endpoint` supplies their shared default. Retention and cadence
+need no model. Each capability owns its settings and project inputs. Select permission policies through
+`roboshed.sandbox.PermissionPolicy`, or configure one `Sandbox` and derive
+the standard tiered policy with `sandbox.permissions(project_slug)`. The sandbox
+also derives all project persistence paths. Compose task-oriented agents directly
+with `AgentDefinition`.
+
+See the [factory and migration guide](../../docs/agent-factories.md).
+
+## Conversation compaction
+
+The following fragment belongs inside an agent or tool builder. `endpoint` is
+the selected compaction model, and `agent_pipe` is the owning agent's event
+pipe. These are independent inputs to the tool.
+
+```python
+from roboshed.tools import get_compactify_messages_when_needed_tool
+
+compact = get_compactify_messages_when_needed_tool(
+    endpoint=endpoint, threshold_percent=60, pipe=agent_pipe, timeout_s=60,
+)
+```
+
+Include this tool in an agent's `default_tools` and pass that agent's owning
+`EventPipe`. The standalone factory defaults to an 80% threshold and no timeout;
+`system_prompt` and `skill_message` override the full continuation instructions.
+The tool preserves the contiguous bootstrap prefix and folds the remaining
+history, including previous summaries, into a new continuation message. Its
+status also carries the summary for event persistence. Each constructed tool
+owns its compaction count; constructing one per agent keeps counters independent.
+
+Successful status reports describe the compacted history's current usage and
+headroom. Summaries are budgeted below the configured threshold and endpoint
+capacity, including the preserved prefix and continuation payload. If there is
+no room for a summary, or the returned replacement still exceeds the budget
+after summarization retries, the tool returns `blocked` without changing history
+or the counter. The continuation payload retains `percent_used_before`.
+
+Cancellation and interruption propagate through the existing Roboz summarizer.
+An optional positive, finite `timeout_s` bounds each provider attempt, not the
+whole compaction. Failed attempts leave history and the counter unchanged;
+late provider results are ignored without forcibly killing worker threads.
+Summarization messages and model-call events use the supplied pipe.
+
+The public tool name and persisted caller are `compactify_messages_when_needed`.
+This tool owns the shared continuation prompts and retains RoboSprawl's caller
+name. The old `robosprawl.compaction` import is
+replaced by `roboshed.tools`. Shed also owns the shared summarizer and Librarian
+memory pipeline; core provides the mechanisms they use.
+
+## Context API migration
+
+Low-level tool factories now use `roboz.Ctx(**values)` directly, with service,
+endpoint, and executable objects supplied without wrappers. The specialized
+context classes have been removed. Existing tool builders retain their keyword
+arguments, defaults, permission checks, cancellation, and timeout behavior.
+See the [migration guide](https://github.com/Tachion-Oy/roboz/blob/main/docs/context-migration.md)
+for low-level context fields and state ownership.
+
+
+Use `RoboSprawl` from `roboshed.deployments.robosprawl` to configure project
+capabilities and a memory endpoint. It derives the persistent orchestrator,
+project instructions, and Librarian maintenance. Its `librarian_capabilities`
+callable can override the default maintenance sequence using each run's project
+and recursive foreground names. For repeatable CLI or server
+construction, pass this recipe to `DeploymentFactory`; custom recipes can return
+`AgenticFactory` directly. Use core's `roboz.llm.ModelSelector` for lazy model
+selection. Recipes allocate fresh stateful inputs while allowing
+explicitly shared lazy clients. The factory returns uninvoked agents; consumers
+own interaction and shutdown. `roboz.dependencies` supplies exact dependency
+registration and binding; `roboshed.dependency_health` supplies probes and health
+monitoring without a web framework or provider SDK.
+Permission policies treat configured folder names literally. Health scheduling
+retries observation failures; timed-out workers retain their concurrency slots
+until completion.
+See [agent factories](../../docs/agent-factories.md) for the contracts and examples.
+
+The `robosprawl` skill from `roboshed.skills` covers sandbox orientation and the HUD
+file-link/markdown contract. Select it through
+`Capability(auto_loaded_skills=(robosprawl,))` for compatible consumers. It uses project
+paths supplied through `RoboSprawl.project_context` instead of choosing a sandbox layout.

roboshed-0.1.0a3/README.md

@@ -0,0 +1,125 @@
+# roboshed
+
+Reusable agent factories, capabilities, sandbox policies, tools, and skills built on Roboz. Version `0.1.0a1`
+is alpha; APIs may change before 1.0. Dependencies are Roboz and Pydantic only.
+
+Includes guarded Unix file commands, Python patch editing, CLI/file/email
+instructions, and provider-neutral email contracts and tools. It does not
+install any model SDK, Proton, document SDK, web service, or backend framework.
+
+```python
+from pathlib import Path
+from roboz import stop
+from roboz.deployment import AgentDefinition, Capability
+from roboz.llm import MockLLMEndpoint
+from roboshed.capabilities import FileCommands, FileEditing
+from roboshed.sandbox import PermissionPolicy
+
+permissions = PermissionPolicy.local(Path("./sandbox"))
+agent = AgentDefinition(
+    name="file_worker",
+    system_prompt="Complete the user's task, then call stop.",
+    agent_endpoint=MockLLMEndpoint([
+        {"action": "stop", "rationale": "done", "value": "Ready."}
+    ]),
+    capabilities=(
+        Capability(tools=(stop,)),
+        FileCommands(permissions),
+        FileEditing(permissions),
+    ),
+).build()
+result, messages = agent.invoke()
+```
+
+`roboshed.capabilities` provides `FileCommands`, `FileEditing`, `Compactification`,
+`ConversationSnapshots`, `MemoryConsolidation`, `ArtifactRetention`, and
+`MaintenanceCadence`, alongside the `tools` and `skills` modules. Applications
+choose and configure these capabilities through the presets’ single `capabilities`
+extension argument. A capability owns its tools and any skills used for instructions. `roboshed.deployments.robosprawl`
+provides project composition. `roboshed.agents` supplies the reusable
+orchestrator/Librarian presets. Generic definitions and
+capability contracts live in `roboz.deployment`. Each capability
+builds its tools with explicit endpoint overrides or the agent's default.
+Runtime controls remain separate from endpoints. The Librarian accepts an ordered
+`capabilities` sequence. Snapshot and consolidation capabilities each expose an
+`endpoint`; `agent_endpoint` supplies their shared default. Retention and cadence
+need no model. Each capability owns its settings and project inputs. Select permission policies through
+`roboshed.sandbox.PermissionPolicy`, or configure one `Sandbox` and derive
+the standard tiered policy with `sandbox.permissions(project_slug)`. The sandbox
+also derives all project persistence paths. Compose task-oriented agents directly
+with `AgentDefinition`.
+
+See the [factory and migration guide](../../docs/agent-factories.md).
+
+## Conversation compaction
+
+The following fragment belongs inside an agent or tool builder. `endpoint` is
+the selected compaction model, and `agent_pipe` is the owning agent's event
+pipe. These are independent inputs to the tool.
+
+```python
+from roboshed.tools import get_compactify_messages_when_needed_tool
+
+compact = get_compactify_messages_when_needed_tool(
+    endpoint=endpoint, threshold_percent=60, pipe=agent_pipe, timeout_s=60,
+)
+```
+
+Include this tool in an agent's `default_tools` and pass that agent's owning
+`EventPipe`. The standalone factory defaults to an 80% threshold and no timeout;
+`system_prompt` and `skill_message` override the full continuation instructions.
+The tool preserves the contiguous bootstrap prefix and folds the remaining
+history, including previous summaries, into a new continuation message. Its
+status also carries the summary for event persistence. Each constructed tool
+owns its compaction count; constructing one per agent keeps counters independent.
+
+Successful status reports describe the compacted history's current usage and
+headroom. Summaries are budgeted below the configured threshold and endpoint
+capacity, including the preserved prefix and continuation payload. If there is
+no room for a summary, or the returned replacement still exceeds the budget
+after summarization retries, the tool returns `blocked` without changing history
+or the counter. The continuation payload retains `percent_used_before`.
+
+Cancellation and interruption propagate through the existing Roboz summarizer.
+An optional positive, finite `timeout_s` bounds each provider attempt, not the
+whole compaction. Failed attempts leave history and the counter unchanged;
+late provider results are ignored without forcibly killing worker threads.
+Summarization messages and model-call events use the supplied pipe.
+
+The public tool name and persisted caller are `compactify_messages_when_needed`.
+This tool owns the shared continuation prompts and retains RoboSprawl's caller
+name. The old `robosprawl.compaction` import is
+replaced by `roboshed.tools`. Shed also owns the shared summarizer and Librarian
+memory pipeline; core provides the mechanisms they use.
+
+## Context API migration
+
+Low-level tool factories now use `roboz.Ctx(**values)` directly, with service,
+endpoint, and executable objects supplied without wrappers. The specialized
+context classes have been removed. Existing tool builders retain their keyword
+arguments, defaults, permission checks, cancellation, and timeout behavior.
+See the [migration guide](https://github.com/Tachion-Oy/roboz/blob/main/docs/context-migration.md)
+for low-level context fields and state ownership.
+
+
+Use `RoboSprawl` from `roboshed.deployments.robosprawl` to configure project
+capabilities and a memory endpoint. It derives the persistent orchestrator,
+project instructions, and Librarian maintenance. Its `librarian_capabilities`
+callable can override the default maintenance sequence using each run's project
+and recursive foreground names. For repeatable CLI or server
+construction, pass this recipe to `DeploymentFactory`; custom recipes can return
+`AgenticFactory` directly. Use core's `roboz.llm.ModelSelector` for lazy model
+selection. Recipes allocate fresh stateful inputs while allowing
+explicitly shared lazy clients. The factory returns uninvoked agents; consumers
+own interaction and shutdown. `roboz.dependencies` supplies exact dependency
+registration and binding; `roboshed.dependency_health` supplies probes and health
+monitoring without a web framework or provider SDK.
+Permission policies treat configured folder names literally. Health scheduling
+retries observation failures; timed-out workers retain their concurrency slots
+until completion.
+See [agent factories](../../docs/agent-factories.md) for the contracts and examples.
+
+The `robosprawl` skill from `roboshed.skills` covers sandbox orientation and the HUD
+file-link/markdown contract. Select it through
+`Capability(auto_loaded_skills=(robosprawl,))` for compatible consumers. It uses project
+paths supplied through `RoboSprawl.project_context` instead of choosing a sandbox layout.

roboshed-0.1.0a3/pyproject.toml

@@ -0,0 +1,25 @@
+[project]
+name = "roboshed"
+version = "0.1.0a3"
+description = "roboshed: optional building blocks for Roboz"
+readme = "README.md"
+requires-python = ">=3.13"
+authors = [{ name = "Tachion Oy" }]
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+import-names = ["roboshed"]
+classifiers = ["Development Status :: 3 - Alpha", "Typing :: Typed"]
+dependencies = ["roboz>=0.1.2.dev2,<0.2.0","pydantic>=2.12.4"]
+
+[build-system]
+requires = ["hatchling>=1.32"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/roboshed"]
+
+[project.urls]
+Repository = "https://github.com/Tachion-Oy/roboz"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

roboshed-0.1.0a3/src/roboshed/__init__.py

@@ -0,0 +1 @@
+"""Reusable tools and compositions built on Roboz."""

roboshed-0.1.0a3/src/roboshed/agents/__init__.py

@@ -0,0 +1,6 @@
+"""Reusable agent presets built from Roboz primitives."""
+
+from .librarian import librarian
+from .orchestrator import orchestrator
+
+__all__ = ["librarian", "orchestrator"]