Fork issue tracking can be enabled without detaching

GitHub rejected issue creation on a fork with HTTP 410 and an explicit Issues disabled message. With owner authorization, gh repo edit OWNER/REPO --enable-issues succeeded, and gh repo view OWNER/REPO --json hasIssuesEnabled verified the setting before issue submission. Fork status did not require detaching the repository or reporting fork-specific bugs upstream. A connector that supports issue creation may still lack repository-settings controls, so use an authorized CLI fallback and verify the setting separately from issue creation.