@yottagraph-app/aether-instructions 1.1.50 → 1.1.51

package/AGENTS.md

@@ -12,7 +12,7 @@
 
 **Source of truth:** `DESIGN.md` -- read before starting work, update when changing features. The starter UI is placeholder -- replace freely. Feature docs in `design/` for implementation planning.
 
-**Git:** Commit meaningful units of work. Run `npm run format` before commit. Message format: `[Agent commit] {summary}`. Push directly to `main` with `git push origin main` — do NOT create PRs, do NOT run `gh pr create`, and do NOT use feature branches. Tenant `main` is not protected; Vercel auto-deploys on push to `main`, and that's how the app gets live. (This is the opposite of the `aether-dev` repo, which IS PR-only — do not import that habit.)
+**Git:** Commit meaningful units of work. Run `npm run format` before commit. Message format: `[Agent commit] {summary}`. Push directly to `main` with `git push origin main` — do NOT create PRs, do NOT run `gh pr create`, and do NOT use feature branches. This project's `main` is not protected; Vercel auto-deploys on push to `main`, and that's how the app gets live. A PR blocks the auto-deploy and breaks the smooth first-run flow.
 
 **First action for a new project:** Run `/build_my_app`.
 

package/commands/build_my_app.md

@@ -233,10 +233,9 @@ git commit -m "[Agent commit] Initial app build from project brief"
 
 Vercel auto-deploys on push to `main`, which is how this project gets
 live. Creating a PR blocks that auto-deploy and breaks the smooth
-first-run experience the user is expecting from the wizard. The `main`
-branch on tenant repos is **not** protected — `git push origin main`
-will succeed. Tenant repos follow a different policy than the upstream
-`aether-dev` template (which IS PR-only) — do not import that habit.
+first-run experience the user is expecting from the wizard. This
+project's `main` is **not** protected — `git push origin main` will
+succeed.
 
 ```bash
 git push origin main

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@yottagraph-app/aether-instructions",
-    "version": "1.1.50",
+    "version": "1.1.51",
     "description": "Cursor commands and skills for Aether development",
     "files": [
         "commands",

package/skills/aether/git-support.md

@@ -41,18 +41,13 @@ If a user asks about this error, explain the `npm run format` requirement.
 ## Pushing
 
 **Push directly to main.** Vercel auto-deploys on push to `main`, which
-is how this project gets live. Creating a PR breaks that auto-deploy
-flow and disrupts the smooth first-run experience the wizard sets up.
+is how this project gets live. Creating a PR blocks that auto-deploy
+and disrupts the smooth first-run experience.
 
 **Do NOT create pull requests** — do not run `gh pr create`, do not
 create a feature branch, and do not push to anything other than `main`.
-The `main` branch on tenant repos is **not** protected; `git push
-origin main` will succeed.
-
-> Note: tenant repos follow a different policy than the upstream
-> `aether-dev` template. `aether-dev` is PR-only because its `main` is
-> protected; tenant projects deliberately are not. Do not import the
-> `aether-dev` habit when working in a tenant repo.
+This project's `main` is **not** protected; `git push origin main`
+will succeed.
 
 ```bash
 git push origin main

package/variants/mcp-only/commands/build_my_app.md

@@ -174,10 +174,9 @@ git commit -m "[Agent commit] Initial app build from project brief"
 
 Vercel auto-deploys on push to `main`, which is how this project gets
 live. Creating a PR blocks that auto-deploy and breaks the smooth
-first-run experience the user is expecting from the wizard. The `main`
-branch on tenant repos is **not** protected — `git push origin main`
-will succeed. Tenant repos follow a different policy than the upstream
-`aether-dev` template (which IS PR-only) — do not import that habit.
+first-run experience the user is expecting from the wizard. This
+project's `main` is **not** protected — `git push origin main` will
+succeed.
 
 ```bash
 git push origin main