diff --git a/.planning/research/questions.md b/.planning/research/questions.md
index 6443aba0..7f5698c7 100644
--- a/.planning/research/questions.md
+++ b/.planning/research/questions.md
@@ -15,4 +15,4 @@
 
 ## From the plugin marketplace exploration (2026-10-29)
 
-- **Is `--module` for git-URL installs worth supporting?** `summer plugin:install <git-url>` defaults to a submodule checkout. Installing a private repo as a Go module needs `GOPRIVATE`/`GONOSUMDB` and git `insteadOf` rules so `go` can authenticate, which is fragile across GitHub, GitLab and Gitea and across SSH and HTTPS tokens. Find out what the setup costs in practice, whether `plugin:install` can detect and explain a misconfiguration, and decide whether `--module` ships or git URLs stay submodule-only. See `.planning/notes/2026-10-29-plugin-marketplace.md`. Phase: plugin marketplace.
+- ~~**Is `--module` for git-URL installs worth supporting?**~~ **Answered 2026-10-29: not in v1.** Git URLs install as submodules only (Phase 34, D-11; `summer plugin:install <git-url>` shipped in 34-04 without `--module`). Revisit only if submodule-only installs prove limiting; adding the flag later is additive. Original question: `summer plugin:install <git-url>` defaults to a submodule checkout. Installing a private repo as a Go module needs `GOPRIVATE`/`GONOSUMDB` and git `insteadOf` rules so `go` can authenticate, which is fragile across GitHub, GitLab and Gitea and across SSH and HTTPS tokens. Find out what the setup costs in practice, whether `plugin:install` can detect and explain a misconfiguration, and decide whether `--module` ships or git URLs stay submodule-only. See `.planning/notes/2026-10-29-plugin-marketplace.md`. Phase: plugin marketplace.