docs(forge-preferences): replace open questions with derived preferences and add conventions

- Replace hardcoded open questions with runtime-derived preferences for
  forge remote, CLI, and host/username detection
- Add issue label mapping reference to triage-labels.md
- Add PR title/body conventions following Conventional Commits
- Add release tagging conventions with semver format

common/personal/forge-preferences/SKILL.md

@@ -22,10 +22,23 @@ Store personal conventions that should not live in the generic forge interaction
 - If the correct CLI is missing, tell the user to install it or add it to `PATH`.
 - Do not use the wrong CLI as a fallback.
 
-## Open Questions To Fill In Later
+## Derived Preferences (auto-detected at runtime)
 
-- Known personal Gitea hosts.
-- GitHub usernames or organizations.
-- Preferred PR title/body format.
-- Preferred issue labels and milestones.
-- Release naming and tagging conventions.
+- Canonical forge remote: prefer `forge`, then default remote, then `origin`.
+- Forge CLI: determined from remote URL (GitHub → `gh`, Gitea → `tea`).
+- Known personal Gitea hosts and GitHub usernames/orgs are collected from the remote URL and git CLI at time of use — no hardcoded list.
+
+## Issue Labels
+
+See `triage-labels.md` in this directory for the canonical-to-actual label mapping.
+
+## PR Conventions
+
+- PR titles follow Conventional Commits: `type(scope): description`.
+  - Common types: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`.
+- PR body is freeform but should summarise the change and any breaking or noteworthy details.
+
+## Release Conventions
+
+- Tags follow semver: `v{major}.{minor}.{patch}` (e.g. `v1.2.3`).
+- Releases are created from the tag with auto-generated or manually curated notes.