Today the first-time flow is two steps: declare the allow-list (dew add / dew add . / dew init --from-gitignore), then dew pack. pack refuses an empty allow-list by design (the allow-list is authoritative — dew never packs "everything ignored").
For first-time setup, a one-shot would be handy, e.g.:
dew pack --from-gitignore — discover candidates, add them, then pack; ordew add . --pack — add discovered candidates and immediately pack.
Constraints
- Must preserve the allow-list-authoritative model — this is opt-in convenience over discovered candidates, never "auto-pack every ignored file."
- Should still write the discovered entries to the manifest (so subsequent
packs are just pack).
- Interactive vs
-y semantics like add ..
Steady-state is unaffected (once files are tracked, dew pack alone re-packages them). This is purely a first-run ergonomics nicety.
Today the first-time flow is two steps: declare the allow-list (
dew add/dew add ./dew init --from-gitignore), thendew pack.packrefuses an empty allow-list by design (the allow-list is authoritative — dew never packs "everything ignored").For first-time setup, a one-shot would be handy, e.g.:
dew pack --from-gitignore— discover candidates, add them, then pack; ordew add . --pack— add discovered candidates and immediately pack.Constraints
packs are justpack).-ysemantics likeadd ..Steady-state is unaffected (once files are tracked,
dew packalone re-packages them). This is purely a first-run ergonomics nicety.