@boxes-dev/dvb-runtime 1.0.1014 → 1.0.1016

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 (28) hide show
  1. package/dist/agent-init-guides/env-files.md +29 -3
  2. package/dist/agent-init-guides/flow.md +14 -1
  3. package/dist/agent-init-guides/manifest.md +4 -0
  4. package/dist/bin/dvb.mjs +2046 -1961
  5. package/dist/bin/dvbd.mjs +8 -8
  6. package/dist/product-docs/SKILL.md +4 -0
  7. package/dist/product-docs/references/agent-tools.md +3 -3
  8. package/dist/product-docs/references/automations.md +10 -6
  9. package/dist/product-docs/references/aws.md +4 -3
  10. package/dist/product-docs/references/billing-and-limits.md +6 -4
  11. package/dist/product-docs/references/core-concepts.md +3 -3
  12. package/dist/product-docs/references/desktop-workbench.md +17 -4
  13. package/dist/product-docs/references/files-git-and-review.md +8 -5
  14. package/dist/product-docs/references/fork-workflows.md +21 -9
  15. package/dist/product-docs/references/glossary.md +5 -2
  16. package/dist/product-docs/references/linear.md +10 -7
  17. package/dist/product-docs/references/member-managed-files.md +5 -2
  18. package/dist/product-docs/references/mobile.md +2 -0
  19. package/dist/product-docs/references/onbox-agent-tools.md +4 -3
  20. package/dist/product-docs/references/ports-terminal-and-runtime.md +15 -5
  21. package/dist/product-docs/references/project-setup.md +20 -10
  22. package/dist/product-docs/references/security-and-data.md +43 -26
  23. package/dist/product-docs/references/slack.md +8 -6
  24. package/dist/product-docs/references/tailscale.md +3 -0
  25. package/dist/product-docs/references/team-template.md +30 -41
  26. package/dist/product-docs/references/threads-and-agents.md +32 -15
  27. package/dist/product-docs/references/troubleshooting.md +36 -23
  28. package/package.json +2 -2
@@ -32,7 +32,18 @@ How to investigate (read-only; base every entry on evidence, never guess):
32
32
  - Always prune `node_modules`, `.git`, `.devbox`, `dist`, `build`, `.next`,
33
33
  `.turbo`, `.vite`, `coverage`. Never use shell globstar (`**`) patterns —
34
34
  prefer `find ... -prune` or `rg --glob '!node_modules/**'`.
35
- - Verify every path you list exists on disk before adding it.
35
+ - Verify every source file exists on disk before adding it. When using `from:`,
36
+ the destination `path` does not need to exist locally.
37
+
38
+ For a linked worktree, use the main checkout path reported by `start`, when
39
+ available. Compare only relevant paths inferred from setup docs, example env
40
+ files, app config, and ignore rules. Check whether expected files are missing
41
+ from the selected worktree and present in that checkout; do not recursively
42
+ inventory other checkouts or assume their configuration is appropriate.
43
+ Inspect relevant config symlinks with `readlink`/`realpath`, including broken
44
+ links, and call out targets outside the selected worktree. Never print secret
45
+ values while comparing files. If no main checkout is available, ask where the
46
+ user normally runs the app when required configuration is missing.
36
47
 
37
48
  Entry shape:
38
49
 
@@ -49,8 +60,23 @@ files:
49
60
  note: GCP SA for the local pubsub emulator
50
61
  ```
51
62
 
52
- Optional `from:` sends an edited copy from the staging folder instead of the
53
- real file (see `guide manifest`).
63
+ Optional `from:` selects another source file, including an edited staging copy
64
+ or a user-approved file in the main checkout (see `guide manifest`). For example,
65
+ after the user chooses to import the main checkout's development configuration:
66
+
67
+ ```yaml
68
+ files:
69
+ env:
70
+ - path: .env.local
71
+ from: /Users/alex/project/.env.local
72
+ note: Use the main checkout's development configuration
73
+ ```
74
+
75
+ This will place the file at `.env.local` on the Template box without modifying
76
+ either local checkout. For an outside config symlink, select the desired file
77
+ contents explicitly instead of relying on the link's local target surviving
78
+ on the Template box. Review the source, destination, and suitability of the
79
+ configuration with the user; do not automatically copy every main-checkout file.
54
80
 
55
81
  Present to the user as a short table (file → why it's needed → secret vars
56
82
  by name). Ask about anything you're unsure belongs — the user knows which
@@ -41,11 +41,17 @@ everything detectable (agent config, repos, untracked-file defaults), plus
41
41
  the live instance-type catalog and the team's current default. It prints the
42
42
  manifest path — that file is now the working document.
43
43
 
44
- Read any project-overlap or skipped-repository explanations printed by `start`.
44
+ Read any worktree, project-overlap, or skipped-repository explanations printed by `start`.
45
45
  Explain them to the user during review and confirm the intended project scope.
46
46
  `check` repeats these explanations in the launch summary; an overlap does not
47
47
  automatically prevent setup.
48
48
 
49
+ For a linked worktree, check whether the app's expected local config is present;
50
+ Git shares history between worktrees but does not copy ignored `.env` files or
51
+ other local configuration. Follow `guide env-files` to investigate missing files
52
+ and symlinks that depend on another checkout. Keep the selected worktree unless
53
+ the user chooses to set up a different checkout.
54
+
49
55
  ## Phase 3: Investigate and compose
50
56
 
51
57
  Fill in every section marked `TODO(agent)`. Each has a guide:
@@ -97,6 +103,13 @@ databases will be dumped, how the app runs, what is excluded. Concise tables
97
103
  work well. The user can reply in chat or edit the manifest file directly —
98
104
  mention its path so they can open it.
99
105
 
106
+ For a worktree, call out missing expected configuration and any files or symlink
107
+ targets outside it. If a needed file exists in the main checkout, offer to use
108
+ that file through an explicit `from:` entry, obtain the configuration another
109
+ way, or start from the checkout where the app already runs. Show source and
110
+ destination paths and get the user's choice before selecting outside files.
111
+ Record unresolved requirements in `setupNotes` for remote setup and validation.
112
+
100
113
  Do not silently choose approval-sensitive options. Before `check`, explicitly
101
114
  confirm runtime agents and imported agent config/history, dirty and untracked
102
115
  files, databases, instance type, GitHub access, Git SSH/signing, devbox
@@ -41,6 +41,10 @@ Rules:
41
41
  `files.other`, `external.configs`, and individual files in `artifacts`.
42
42
  It copies the file's exact contents without changing the original;
43
43
  `from` does not support directories.
44
+ - `from:` also accepts an absolute path or `~/...` to select a source file
45
+ outside staging, such as configuration from the main checkout when setting
46
+ up a linked worktree. Review that source with the user before selecting it.
47
+ The entry's `path` is the destination and need not already exist locally.
44
48
 
45
49
  Sections (each has its own guide topic):
46
50