valise-sh 0.1.0 → 0.3.0

package/examples/e2e/README.md

@@ -1,31 +1,40 @@
 # End-to-end example
 
-This directory is a sample consuming profile. It includes twelve modules
-that exercise dependencies, shell and platform selection, exports, optional
-dependencies, and composition with the shared provider in `examples/shared/`.
+This directory is a valise project used by `tests/e2e.test.sh`. Its modules
+exercise dependencies, shell and platform selection, exports, optional
+dependencies, a Fish module, and composition with the shared provider in
+`examples/shared/`.
 
 ## Modules
 
 | Module | Shells | Platforms | Depends on | Export |
 |---|---|---|---|---|
-| `e2e_env_setup` | sh bash zsh ksh | any | `platform_posix` | `e2e_env_ready` |
-| `e2e_aliases` | sh bash zsh ksh | any | `e2e_env_setup` | `e2e_show_aliases` |
+| `e2e_env_setup` | posix | any | `valise_platform_posix` | `e2e_env_ready` |
+| `e2e_aliases` | posix | any | `e2e_env_setup` | `e2e_show_aliases` |
 | `e2e_completions_bash` | bash | any | `e2e_aliases` | `e2e_bash_completions_loaded` |
 | `e2e_completions_zsh` | zsh | any | `e2e_aliases` | `e2e_zsh_completions_loaded` |
 | `e2e_ksh_features` | ksh | any | `e2e_env_setup` | `e2e_ksh_loaded` |
 | `e2e_fish_features` | fish | any | optional `e2e_env_setup` | `e2e_fish_loaded` |
-| `e2e_platform_tools_darwin` | sh bash zsh ksh | darwin | `platform_macos` | `e2e_darwin_tools_ready` |
-| `e2e_platform_tools_linux` | sh bash zsh ksh | linux | `platform_linux` | `e2e_linux_tools_ready` |
-| `e2e_platform_tools_bsd` | sh bash zsh ksh | bsd | `platform_bsd` | `e2e_bsd_tools_ready` |
-| `e2e_optional_network` | sh bash zsh ksh | any | optional `e2e_env_setup` | `e2e_net_available` |
-| `e2e_generated_config` | sh bash zsh ksh | any | `e2e_env_setup` | `e2e_config_loaded` |
-| `e2e_layer_probe` | sh bash zsh ksh | any | `e2e_env_setup`, optional `contrib_shared_paths` | `e2e_layer_probe_ok` |
-
-`e2e_layer_probe` depends on a primary-root module and optionally on a
-module in the shared layer. It tests dependency resolution in both directions
-across the two roots.
-
-## Build, install, and verify
+| `e2e_platform_tools` | posix | any | `e2e_env_setup`, optional the three below | none |
+| `e2e_platform_tools_darwin` | posix | darwin | `valise_platform_macos` | `e2e_darwin_tools_ready` |
+| `e2e_platform_tools_linux` | posix | linux | `valise_platform_linux` | `e2e_linux_tools_ready` |
+| `e2e_platform_tools_bsd` | posix | bsd | `valise_platform_bsd` | `e2e_bsd_tools_ready` |
+| `e2e_optional_network` | posix | any | optional `e2e_env_setup` | `e2e_net_available` |
+| `e2e_generated_config` | posix | any | `e2e_env_setup` | `e2e_config_loaded` |
+| `e2e_layer_probe` | posix | any | `e2e_env_setup`, optional `contrib_shared_paths` | `e2e_layer_probe_ok` |
+
+`bundles.tsv` gives each shell its roots. The POSIX rows name
+`e2e_platform_tools`, which lists the per-platform modules as optional
+dependencies: a platform module that does not match the running system is
+skipped quietly, while naming it as a root would be a strict-mode failure on
+every other platform. `variants.tsv` has `default` and `no-network`, which
+excludes `e2e_optional_network`.
+
+`e2e_layer_probe` optionally depends on `contrib_shared_paths` from the
+shared provider. Without the provider it reports a standalone load; with the
+provider vendored as a layer it reports that the layer resolved.
+
+## Build, install, and load
 
 Run these commands from the repository root. Installation writes shell
 integration under `HOME`; this example uses a temporary home so it does not
@@ -33,7 +42,7 @@ touch your normal startup files.
 
 ```sh
 export PATH="$PWD/bin:$PATH"
-sh examples/e2e/build-manifest.sh
+valise -C examples/e2e build
 
 _demo=$(mktemp -d)
 mkdir -p "$_demo/home"
@@ -42,39 +51,24 @@ export XDG_DATA_HOME="$_demo/data"
 export XDG_CONFIG_HOME="$_demo/config"
 export XDG_STATE_HOME="$_demo/state"
 
-(cd examples/e2e && valise install)
-valise verify-active
+(cd examples/e2e/build/release && valise install)
+valise release verify
 ```
 
-The build script copies the engine runtime and shared example into the e2e
-tree, then writes `shell/install/profile-release.manifest` with each file's
-size and SHA-256 digest. Generated release files are ignored by Git and can
-be rebuilt at any time.
+`valise build` writes the release to `examples/e2e/build/release`: one plan
+per POSIX shell class under `plans/`, the Fish runtime under `runtime/fish/`,
+and only the modules some shell loads. `valise install` seals it, makes it
+active, and writes the managed block to `~/.profile` (plus `~/.bashrc` or
+`~/.zshrc` for those shells) and the Fish hook.
 
-Load sample modules in a POSIX shell:
+Start a shell through the startup file valise wrote:
 
 ```sh
-_active=$(cd "$XDG_CONFIG_HOME/valise/active" && pwd -P)
-VALISE_MODULE_ROOT="$_active" \
-VALISE_MODULES='e2e_env_setup e2e_aliases e2e_generated_config e2e_optional_network' \
-VALISE_MODE=strict \
-. "$_active/entrypoints/profile.sh"
-
-e2e_env_ready
-e2e_show_aliases
-e2e_config_loaded
+bash -c '. "$HOME/.bashrc"; e2e_env_ready; e2e_show_aliases; e2e_config_loaded'
+fish -c 'functions -q e2e_fish_loaded; and valise release verify'
 ```
 
-Try the Fish module in a new Fish process. The installed `conf.d` hook loads
-the sealed release at startup, so set the module list in the child's
-environment before starting Fish:
-
-```sh
-VALISE_MODULES=e2e_fish_features VALISE_MODE=strict fish -c \
-  'functions -q e2e_fish_loaded; and valise verify-active'
-```
-
-When finished, stop using the functions and remove the temporary installation:
+When finished, remove the temporary installation:
 
 ```sh
 chmod -R u+w "$_demo"
@@ -83,31 +77,30 @@ rm -rf "$_demo"
 
 ## Shared provider composition
 
-The build script vendors `examples/shared/` under `layer/shared/` and records
-its source revision in `layer/shared/layer-pin.txt`. The release manifest
-covers both the profile and provider files. After the build, installation,
-and verification above, load the cross-root probe and shared utilities:
+A project composes a provider by vendoring its tree as `layers/<provider>/`.
+To try it, copy this project, vendor `examples/shared/` as `layers/shared/`,
+and add the provider's modules to the POSIX roots:
 
 ```sh
-_active=$(cd "$XDG_CONFIG_HOME/valise/active" && pwd -P)
-VALISE_MODULE_ROOT="$_active" \
-VALISE_MODULE_PATH="$_active/layer/shared" \
-VALISE_MODULES='e2e_layer_probe contrib_shared_paths contrib_shared_umask' \
-VALISE_MODE=strict \
-. "$_active/entrypoints/profile.sh"
-
-e2e_layer_probe_ok
-contrib_shared_paths_setup
-contrib_shared_umask_secure  # explicitly changes umask to 077
+_proj=$(mktemp -d)
+cp -R examples/e2e/valise.conf examples/e2e/variants.tsv \
+  examples/e2e/module.d examples/e2e/modules "$_proj/"
+mkdir -p "$_proj/layers/shared"
+cp -R examples/shared/module.d examples/shared/modules "$_proj/layers/shared/"
+awk -F '\t' 'BEGIN { OFS = "\t" } NR > 1 && $2 != "fish" { $3 = $3 " contrib_shared_umask" } { print }' \
+  examples/e2e/bundles.tsv >"$_proj/bundles.tsv"
+valise -C "$_proj" build
 ```
 
-The provider modules are POSIX-only; Fish users can load the profile's Fish
-modules but not these utilities. To update the provider in a real consuming
-project, vendor a reviewed commit, inspect the diff, then rebuild and verify
-the release. See [the module ABI](../../docs/module-abi.md) for multi-root
-resolution and [the installation guide](../../docs/installation.md) for the
-integrity and provenance limits.
-
-`tests/e2e.test.sh` runs the install, verification, tamper, and composition
-scenarios in quarantined homes. It also runs available host-shell lanes;
-configured Lima Linux, BusyBox, and BSD lanes run when their VMs are present.
+The release then carries the provider's modules under `layers/shared/`, and
+`e2e_layer_probe_ok` reports that the shared layer resolved. The provider
+modules are POSIX-only, so the Fish closure is unchanged. To update a
+vendored provider in a real project, copy a reviewed commit, inspect the
+diff, then rebuild and verify. See [the module ABI](../../docs/module-abi.md)
+for dependency resolution and [the installation guide](../../docs/installation.md)
+for the integrity and provenance limits.
+
+`tests/e2e.test.sh` runs these scenarios in quarantined homes: every
+available host shell, a tamper lane, and the composition lane. Configured
+Lima Linux, BusyBox, and BSD guests run the same install and load checks
+when their VMs are present.

package/examples/e2e/bundles.tsv

@@ -0,0 +1,6 @@
+bundle	shell	roots
+default	sh	e2e_env_setup e2e_generated_config e2e_optional_network e2e_layer_probe e2e_platform_tools
+default	bash	e2e_env_setup e2e_generated_config e2e_optional_network e2e_layer_probe e2e_platform_tools e2e_aliases e2e_completions_bash
+default	zsh	e2e_env_setup e2e_generated_config e2e_optional_network e2e_layer_probe e2e_platform_tools e2e_aliases e2e_completions_zsh
+default	ksh	e2e_env_setup e2e_generated_config e2e_optional_network e2e_layer_probe e2e_platform_tools e2e_ksh_features
+default	fish	e2e_fish_features

package/examples/e2e/module.d/e2e_aliases.meta

@@ -1,9 +1,8 @@
 name=e2e_aliases
 requires=e2e_env_setup
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=e2e_show_aliases
-updates=
 load=modules/e2e/aliases.sh

package/examples/e2e/module.d/e2e_completions_bash.meta

@@ -5,5 +5,4 @@ shells=bash
 platforms=any
 side_effect=read-only
 exports=e2e_bash_completions_loaded
-updates=
 load=modules/e2e/completions_bash.sh

package/examples/e2e/module.d/e2e_completions_zsh.meta

@@ -5,5 +5,4 @@ shells=zsh
 platforms=any
 side_effect=read-only
 exports=e2e_zsh_completions_loaded
-updates=
 load=modules/e2e/completions_zsh.sh

package/examples/e2e/module.d/e2e_env_setup.meta

@@ -1,9 +1,8 @@
 name=e2e_env_setup
-requires=platform_posix
+requires=valise_platform_posix
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=e2e_env_ready
-updates=
 load=modules/e2e/env_setup.sh

package/examples/e2e/module.d/e2e_fish_features.meta

@@ -5,5 +5,4 @@ shells=fish
 platforms=any
 side_effect=read-only
 exports=e2e_fish_loaded
-updates=
 load=modules/e2e/fish_features.fish

package/examples/e2e/module.d/e2e_generated_config.meta

@@ -1,9 +1,8 @@
 name=e2e_generated_config
 requires=e2e_env_setup
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=e2e_config_loaded
-updates=
 load=modules/e2e/generated_config.sh

package/examples/e2e/module.d/e2e_ksh_features.meta

@@ -5,5 +5,4 @@ shells=ksh
 platforms=any
 side_effect=read-only
 exports=e2e_ksh_loaded
-updates=
 load=modules/e2e/ksh_features.sh

package/examples/e2e/module.d/e2e_layer_probe.meta

@@ -1,9 +1,8 @@
 name=e2e_layer_probe
 requires=e2e_env_setup
 optional=contrib_shared_paths
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=e2e_layer_probe_ok
-updates=
 load=modules/e2e/layer_probe.sh

package/examples/e2e/module.d/e2e_optional_network.meta

@@ -1,9 +1,8 @@
 name=e2e_optional_network
 requires=
 optional=e2e_env_setup
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=e2e_net_available
-updates=
 load=modules/e2e/optional_network.sh

package/examples/e2e/module.d/e2e_platform_tools.meta

@@ -0,0 +1,8 @@
+name=e2e_platform_tools
+requires=e2e_env_setup
+optional=e2e_platform_tools_darwin e2e_platform_tools_linux e2e_platform_tools_bsd
+shells=posix
+platforms=any
+side_effect=read-only
+exports=
+load=

package/examples/e2e/module.d/e2e_platform_tools_bsd.meta

@@ -1,9 +1,8 @@
 name=e2e_platform_tools_bsd
-requires=platform_bsd
+requires=valise_platform_bsd
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=bsd freebsd openbsd netbsd
 side_effect=read-only
 exports=e2e_bsd_tools_ready
-updates=
 load=modules/e2e/platform_tools_bsd.sh

package/examples/e2e/module.d/e2e_platform_tools_darwin.meta

@@ -1,9 +1,8 @@
 name=e2e_platform_tools_darwin
-requires=platform_macos
+requires=valise_platform_macos
 optional=e2e_env_setup
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=darwin
 side_effect=read-only
 exports=e2e_darwin_tools_ready
-updates=
 load=modules/e2e/platform_tools_darwin.sh

package/examples/e2e/module.d/e2e_platform_tools_linux.meta

@@ -1,9 +1,8 @@
 name=e2e_platform_tools_linux
-requires=platform_linux
+requires=valise_platform_linux
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=linux
 side_effect=read-only
 exports=e2e_linux_tools_ready
-updates=
 load=modules/e2e/platform_tools_linux.sh

package/examples/e2e/valise.conf

@@ -0,0 +1,4 @@
+# valise project configuration.
+bundle=default
+variant=default
+requires_valise=0.3.0

package/examples/e2e/variants.tsv

@@ -0,0 +1,3 @@
+variant	description	excluded
+default	Every e2e module	
+no-network	Without the network probe	e2e_optional_network

package/examples/local/module.d/hello_valise.meta

@@ -1,9 +1,8 @@
 name=hello_valise
 requires=
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=read-only
 exports=hello_valise_loaded
-updates=
 load=modules/hello_valise.sh

package/examples/profile-project/README.md

@@ -0,0 +1,151 @@
+# profile-project: a small valise project
+
+This project has two modules of its own, one module from a provider layer, a
+bundle, and two variants. Everything is plain text; `valise` reads the
+metadata and generates the rest.
+
+## What is in it
+
+```
+valise.conf                          default bundle and variant
+module.d/
+  profile_main.meta                  the root: requires greeting
+  greeting.meta                      defines greet
+modules/
+  greeting.sh
+layers/demo/                         a provider layer
+  module.d/contrib_demo_greeting.meta
+  modules/shared/contrib_demo_greeting.sh
+bundles.tsv                          the roots for bash, zsh, and ksh
+variants.tsv                         default and workstation-lean
+```
+
+`profile_main` is a meta module: it has `requires=greeting` and no body. It
+names what the project loads. `greeting` is an ordinary module with
+`shells=posix`.
+
+The layer module is named `contrib_demo_greeting`, following the
+`contrib_<owner>_<thing>` convention. A release copies it to
+`layers/demo/`, so it cannot collide with the project's own files.
+
+## Build it
+
+From this directory:
+
+```sh
+valise build
+```
+
+```
+build/release/
+  valise-release.conf                bundle, variant, roots, modules
+  manifest.tsv                       every file with its size and SHA-256
+  plans/bash.sh                      the compiled plan for bash
+  plans/zsh.sh
+  plans/ksh.sh
+  runtime/capabilities.sh            the sp_cap_* helpers
+  module.d/, modules/                the project's modules
+  layers/demo/                       the layer module
+```
+
+The plans are plain POSIX shell; read one to see what will run at startup.
+`bundles.tsv` has no `sh` row, so dash and other plain `sh` shells load
+nothing.
+
+## Load it
+
+Run this in a scratch `HOME` (see the main README) unless you want it in your
+real startup files:
+
+```sh
+valise apply
+bash -l -c greet
+# hello from the valise profile project
+```
+
+`apply` builds the release, installs it under your XDG data directory, and
+writes a managed block into `~/.profile`, `~/.zprofile` when zsh is
+installed, and `~/.bashrc` or `~/.zshrc` when that is your shell. It prints
+each file it wrote. `valise apply --dry-run` prints what it would change
+without changing it.
+
+```sh
+valise status
+```
+
+```
+project: /path/to/profile-project
+project default bundle: default
+project default variant: default
+integration: /home/you/.profile: managed block present
+integration: /home/you/.zprofile: managed block present
+active release: ad98ea2ba30bb6c6d4f08b6dec59585228cdf855b814543a37f80ee0f0518773
+active bundle: default
+active variant: default
+active built by valise: 0.3.0
+build output: /path/to/profile-project/build/release (bundle default, variant default)
+drift: active release matches build output
+```
+
+Edit a module and run `valise status` again after `valise build`: the drift
+line reports that the active release no longer matches the build.
+
+`valise uninstall` removes the managed blocks, the Fish hook, and the
+installed releases.
+
+## Try a variant
+
+`workstation-lean` leaves out the layer module:
+
+```sh
+valise explain-variant workstation-lean
+```
+
+```
+Variant: workstation-lean
+Description: No provider layer
+Excluded modules: contrib_demo_greeting@layers/demo/module.d
+
+Per-shell impact (bundle default):
+  bash: 1 of 2 roots, 2 of 3 modules
+  zsh: 1 of 2 roots, 2 of 3 modules
+  ksh: 1 of 2 roots, 2 of 3 modules
+```
+
+Build it with `valise apply --variant=workstation-lean`, or set
+`variant=workstation-lean` in `valise.conf`. An exclusion that removes a
+module something else still requires fails the build and names both
+modules.
+
+## Try a bundle
+
+`bundles.tsv` lists the roots for each shell:
+
+```
+default	bash	profile_main contrib_demo_greeting
+```
+
+A bare name means the project's own module when there is one, otherwise the
+only module with that name. `name@layers/demo/module.d` names the layer's
+copy exactly, which you need when two sources define the same name.
+
+```sh
+valise explain-bundles
+```
+
+## Check it
+
+```sh
+valise lint          # metadata, layers, every bundle and variant, syntax
+valise layer-lint demo
+# layer demo: 1 module(s) validated
+```
+
+## Where to go next
+
+- [Projects](../../docs/projects.md): bundles, variants, compile, and build.
+- [Writing modules](../../docs/contrib-modules.md): authoring, linting, and
+  testing.
+- [The module ABI](../../docs/module-abi.md): every metadata field.
+- [Shared modules](../../docs/shared-modules.md): how layer modules are
+  named and owned.

package/examples/profile-project/bundles.tsv

@@ -0,0 +1,8 @@
+bundle	shell	roots
+# Each row names a bundle, a shell (sh bash zsh ksh fish), and the
+# space-separated root modules for that shell. A bare name means the module
+# in module.d/, else the only module of that name; name@layers/<p>/module.d
+# names a layer module exactly.
+default	bash	profile_main contrib_demo_greeting
+default	zsh	profile_main contrib_demo_greeting
+default	ksh	profile_main contrib_demo_greeting

package/examples/profile-project/layers/demo/module.d/contrib_demo_greeting.meta

@@ -0,0 +1,9 @@
+name=contrib_demo_greeting
+version=1.0.0
+side_effect=read-only
+requires=
+optional=
+shells=posix
+platforms=any
+exports=contrib_demo_greeting_ready
+load=modules/shared/contrib_demo_greeting.sh

package/examples/profile-project/layers/demo/modules/shared/contrib_demo_greeting.sh

@@ -0,0 +1,4 @@
+# A provider layer module. Layer-only modules must carry the `contrib_`
+# prefix; `valise layer-lint demo` enforces that, along with the version,
+# the load target, the file modes, and the dependency closure.
+contrib_demo_greeting_ready() { :; }

package/examples/profile-project/module.d/greeting.meta

@@ -0,0 +1,9 @@
+name=greeting
+version=1.0.0
+side_effect=read-only
+requires=
+optional=
+shells=posix
+platforms=any
+exports=greet
+load=modules/greeting.sh

package/examples/profile-project/module.d/profile_main.meta

@@ -0,0 +1,8 @@
+name=profile_main
+version=1.0.0
+side_effect=read-only
+requires=greeting
+optional=
+shells=bash zsh ksh
+platforms=any
+exports=

package/examples/profile-project/modules/greeting.sh

@@ -0,0 +1,5 @@
+# A plain POSIX module. `shells=posix` covers every POSIX shell: sh, bash,
+# zsh, ksh, and dash.
+greet() {
+  printf '%s\n' "hello from the valise profile project"
+}

package/examples/profile-project/valise.conf

@@ -0,0 +1,4 @@
+# valise project configuration. `valise build` and `valise apply` read these
+# defaults; --bundle and --variant override them.
+bundle=default
+variant=default

package/examples/profile-project/variants.tsv

@@ -0,0 +1,3 @@
+variant	description	excluded
+default	Every module in the project	
+workstation-lean	No provider layer	contrib_demo_greeting@layers/demo/module.d

package/examples/shared/README.md

@@ -9,41 +9,20 @@ be pinned to a reviewed commit in the consuming project.
 
 | Module | Version | Export | Behavior |
 |---|---|---|---|
-| `contrib_shared_paths` | 1.0.0 | `contrib_shared_paths_setup` | Adds `$HOME/.local/bin` and `$HOME/.go/bin` using `contrib_path_prepend`. |
+| `contrib_shared_paths` | 1.0.0 | `contrib_shared_paths_setup` | Adds `$HOME/.local/bin` and `$HOME/.go/bin` using `valise_path_prepend`. |
 | `contrib_shared_umask` | 1.0.0 | `contrib_shared_umask_secure` | Sets `umask 077` when explicitly called. |
 
 The modules and their metadata are under `modules/shared/` and
 `module.d/`. Layer-only modules use the `contrib_` prefix. The paths module
-requires the engine's `contrib_path` module; this exercises dependency
-resolution from a layer into the primary module root.
-
-## Use in the sample profile
-
-From the repository root, build the sample release and install it from the
-e2e directory. Installation adds an integration hook under `HOME`; use a
-temporary home to avoid changing your own shell startup files (see the top
-level README).
-
-```sh
-sh examples/e2e/build-manifest.sh
-cd examples/e2e
-valise install
-valise verify-active
-```
-
-Then load the shared modules from a POSIX shell. The active release path
-below uses the default XDG locations; if you set `XDG_CONFIG_HOME`, use that
-instead.
-
-```sh
-_active=$(cd "$HOME/.config/valise/active" && pwd -P)
-VALISE_MODULE_ROOT="$_active" \
-VALISE_MODULE_PATH="$_active/layer/shared" \
-VALISE_MODULES='e2e_layer_probe contrib_shared_umask' \
-VALISE_MODE=strict \
-. "$_active/entrypoints/profile.sh"
-```
-
-For a Fish example and details about provider pinning, see
-[the end-to-end walkthrough](../e2e/README.md) and the
-[module ABI](../../docs/module-abi.md).
+requires the engine's `valise_path` module; this exercises dependency
+resolution from a layer into the engine's modules.
+
+## Use in a project
+
+A consuming project vendors this directory as `layers/<provider>/`, for
+example `layers/shared/`, and names the modules it wants in `bundles.tsv` or
+in the `requires=` and `optional=` fields of its own modules. `valise build`
+then copies only the provider modules some plan loads into the release under
+`layers/shared/`. [The end-to-end walkthrough](../e2e/README.md) shows the
+steps against the sample project; see the [module ABI](../../docs/module-abi.md)
+for dependency resolution across a project and its layers.

package/examples/shared/module.d/contrib_shared_paths.meta

@@ -1,10 +1,9 @@
 name=contrib_shared_paths
-requires=contrib_path
+requires=valise_path
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=path-env
 exports=contrib_shared_paths_setup
-updates=
 version=1.0.0
 load=modules/shared/contrib_shared_paths.sh

package/examples/shared/module.d/contrib_shared_umask.meta

@@ -1,10 +1,9 @@
 name=contrib_shared_umask
 requires=
 optional=
-shells=sh bash zsh ksh
+shells=posix bash zsh ksh
 platforms=any
 side_effect=work-only
 exports=contrib_shared_umask_secure
-updates=
 version=1.0.0
 load=modules/shared/contrib_shared_umask.sh