@awebai/pi 0.1.12 → 0.1.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/aweb-bootstrap/SKILL.md +1 -1
  3. package/skills/aweb-team-membership/references/team-membership-reference.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/pi",
3
- "version": "0.1.12",
3
+ "version": "0.1.13",
4
4
  "description": "Aweb for Pi: real-time channel awakenings, aw CLI onboarding, and aweb skills.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
package/skills/aweb-bootstrap/SKILL.md CHANGED
@@ -171,7 +171,7 @@ Policy guidance:
171
171
  - Prefer API key or invite when the team already exists but the caller is not already inside it.
172
172
  - Prefer current workspace forwarding when you are already inside the target team.
173
173
  - Prefer BYOT when you need local control over the team namespace/domain and routing.
174
- - Use `--dry-run` for planning only. The old manual "print commands after installing server state from caller cwd" flow is not coherent and should not be recommended.
174
+ - Use `--dry-run` for planning only. It prints the resolved plan (template ref, work directory, team source, generated workspaces) without writing identities, files, or server state. Do not pair it with side-effecting flags expecting partial provisioning.
175
175
 
176
176
  ## Worktree agents (team.yaml worktrees:)
177
177
 
package/skills/aweb-team-membership/references/team-membership-reference.md CHANGED
@@ -51,7 +51,7 @@ Addressability and delivery authorization are separate:
51
51
  - `did:aw` is identity binding, not a first-contact delivery route.
52
52
  - `inbound_mode=open|team_and_contacts` controls delivery after route validation.
53
53
  - `team_and_contacts` accepts verified same-team senders plus exact active identity contacts for trusted non-team senders. Contacts do not create routes or resolver visibility.
54
- - Legacy reachability fields may still appear in support or migration output, but they are compatibility/audit state, not live delivery authority.
54
+ - Reachability fields that appear in support or migration output are compatibility/audit state, not live delivery authority.
55
55
  - `aw contacts ...` manages saved contact relationships.
56
56
  - `aw id namespace resolve <domain>/<alias> --json` performs a workspace-free directory lookup.
57
57