hive-forge: add --label to issue-create and pr-create

docs/tools/forge.md

@@ -48,9 +48,11 @@ hive-forge assign 42 damocles
 hive-forge close 42
 hive-forge labels 42 add feature
 hive-forge issue-create --title "..." --body "..."
+hive-forge issue-create --title "..." --body "..." --label area/ops --label type/bug  # repeatable
 hive-forge issue-edit 42 --title "new title"
 hive-forge pr 42                            # PR metadata as JSON
 hive-forge pr-create --title "..." --head my-branch --push    # also `git push forge my-branch`
+hive-forge pr-create --title "..." --head my-branch --label area/ops  # repeatable, same as issue-create
 hive-forge pr-reviews 42                    # list reviews; inline comments included per review
 hive-forge pr-reviews 42 --approve         # submit APPROVED review
 hive-forge pr-reviews 42 --request-changes -m "msg"  # submit REQUEST_CHANGES review
@@ -266,3 +268,12 @@ to discover valid label names before triaging or to audit the label set.
   workflow — there is no single-job variant.
 - Do NOT use raw `curl` for forge access -- the CLI handles auth,
   error checking, and output formatting.
+- `issue-create --label <name>` / `pr-create --label <name>` are
+  repeatable and take the same spelling `labels <n> add` does. Unknown
+  names are silently dropped (matching `labels add`'s existing
+  behavior) rather than erroring, so a typo just means the label
+  doesn't land — check `hive-forge repo-labels` if one's missing. On
+  `pr-create --agit`, labels are applied as a follow-up call once the
+  PR number is parsed back out of the push output (the AGit push
+  itself has no label field), so they're silently skipped if that
+  parse fails — same fallback as the deferred multi-line body.