chore: use upstream/main and remove skip-ci exception

- Update AGENTS.md: use upstream/main (micasa-dev/micasa) for rebases
  and PR bases instead of origin/main
- Remove skip-ci exception for AGENTS.md-only commits from /commit
  and /create-pr skills. CI always runs now.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: cpcloud

.claude/commands/commit.md

@@ -35,14 +35,12 @@ Use conventional commits with scopes:
 ## Scope conventions
 
 - Reference the issue number: `closes #42`, `fixes #42`
-- AGENTS.md-only commits: add the standard no-ci marker to the message.
-  There's nothing to build or test.
 - Do not amend unless explicitly requested
 - Do not use `--no-verify` under any circumstances
 
 ## Avoid CI trigger phrases
 
 The tokens `[skip ci]`, `[ci skip]`, `[no ci]`, `[skip actions]`, and
-`[actions skip]` suppress CI runs. Never include them in commit messages
-unless you intend to suppress CI (e.g. AGENTS.md-only changes). When
-referring to the mechanism, paraphrase instead of writing the literal token.
+`[actions skip]` suppress CI runs. Never include them in commit messages.
+When referring to the mechanism, paraphrase instead of writing the literal
+token.

.claude/commands/create-pr.md

@@ -26,7 +26,7 @@ Create a pull request for the current branch.
   omit them from the summary. Only mention AGENTS.md if the PR is solely
   about agent rules.
 - **Avoid CI trigger phrases**: Never put `[skip ci]`, `[ci skip]`, etc.
-  in the PR title or body unless you intend to suppress CI.
+  in the PR title or body.
 
 ## Closing issues
 

AGENTS.md

@@ -182,8 +182,13 @@ details; do not duplicate that detail here.
   independent, sequential when dependent).
 - **Use `jq`, not Python, for JSON**: Use `jq` directly, or `--jq` flags on
   `gh` subcommands.
-- **Treat "upstream" conceptually**: Use the repo's canonical mainline remote
-  (e.g. `origin/main`) even if no `upstream` remote exists.
+- **Discover the mainline remote once per session**: Run
+  `gh repo view --json nameWithOwner --jq .nameWithOwner` to get the
+  canonical repo (e.g. `micasa-dev/micasa`), then match it against
+  `git remote -v` to find the local remote name (e.g. `upstream`). Use
+  that remote's default branch for rebases, PR bases, and diff
+  comparisons. Cache the result for the session — don't re-discover on
+  every command.
 - **Modern CLI tools**: Use `rg` not `grep`, `fd` not `find`, `sd` not
   `sed` where possible.
 - **Read deps locally**: To read a dependency's source, look in the local