[EXPLORATION] plugin lifecycle model + sandboxing concept page - #84
Draft
djsauble wants to merge 2 commits into
Draft
[EXPLORATION] plugin lifecycle model + sandboxing concept page#84djsauble wants to merge 2 commits into
djsauble wants to merge 2 commits into
Conversation
The plugins concept page covered only the released v1.14.0 surface: profile.d scripts plus opaque [plugins.<name>] data. The prototype/sandbox-plugins branch of flox/flox adds generic lifecycle hooks (session-wrap, env, sidecar, on-deactivate.d), a typed [plugin-hooks] manifest section (schema v1.16.0), and a consent model. Present the full lifecycle extension-point model as the spec-review artifact called for by docs/plugin-lifecycle-hooks.md §7 step 8. Also fix a pre-existing bug in the vault example: the script prefixed 'secret/' onto table values that already carry it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MuU9JsLoiuwnY31UQcRicv
The sandbox-plugin analogue of the secrets-management page: sandboxing as a class of plugin built on the lifecycle-hook framework, with the sandboxed activation pattern, the consent/security model, and implementation examples for all fifteen sandbox plugins on the flox-plugins daniel/wave-a-session-wrap branch (session boundaries, advisory mediation, and the ten hand-off generators). Registers the page in docs.json and regenerates llms.txt so check-llms-txt stays green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MuU9JsLoiuwnY31UQcRicv
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
djsauble
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The spec-review artifacts called for by
docs/plugin-lifecycle-hooks.md§7 step 8 on flox/floxprototype/sandbox-plugins. Both pages document prototype behavior (schema v1.16.0,features.plugin_hooks) and are intended for team review alongside that branch and flox-pluginsdaniel/wave-a-session-wrap— not for merge before the feature ships.What's here
concepts/plugins.mdx(expanded) — presents the full lifecycle extension-point model: the environment-lifecycle table, the hook tree, the typed[plugin-hooks]declaration and its threat model (what declarations gate and whyprofile.d/on-deactivate.dstay undeclared), the consent model (default-No auto-activation prompt, include-stripping), the hook protocol (ctx file + env vars), per-hook contracts forsession-wrap/env/sidecar/on-deactivate.d, and the store-path dev/test loop. Also fixes a pre-existing bug in the vault example (secret/double-prefix).concepts/sandboxing.mdx(new) — the sandbox analogue ofconcepts/secrets-management: sandboxing as a class of plugin built on the framework, the sandboxed activation pattern, key security properties, the three plugin shapes (session boundaries, hand-off generators, advisory mediation), and implementation examples for all fifteen sandbox plugins, plus a reference table and backend-choosing guidance.docs.jsonnav entry and regeneratedllms.txt(keepscheck-llms-txtgreen).Fact-checking
Content was verified against the implementations rather than the design doc alone: the
[plugin-hooks]schema, flag, prompts, warning strings, and hook contracts against the flox/flox prototype branch; every plugin example's config keys, prerequisites, bail points, and policy vocabulary against the plugin READMEs and hook scripts. Where the implementation diverges from the design doc (e.g. no published ctx JSON schema, container wrappers needing no re-entry marker), the pages follow the implementation.Known open item
The pages link
github.com/flox/flox-plugins, which 404s for readers without access while the repo is private. The published secrets-management page carries the same link, so this PR keeps it consistent; worth resolving before either page ships.🤖 Generated with Claude Code
https://claude.ai/code/session_01MuU9JsLoiuwnY31UQcRicv