IMPORTANT: This prompt may run in a non-interactive environment.

Non-interactive rules:
- Do not use AskUserQuestion or any interactive prompt/confirmation tool.
- When an optional choice is needed, pick a reasonable default and record the assumption.
- Skip optional confirmations and proceed directly.

Task: optimize the current repository's GitHub About metadata.

Execution context:
- Working directory: `{{projectPath}}`
{{#if repositoryPath}}- Repository path hint: `{{repositoryPath}}`{{/if}}
{{#if targetType}}- Target type: `{{targetType}}`{{/if}}
{{#if vaultId}}- Vault ID: `{{vaultId}}`{{/if}}
{{#if vaultName}}- Vault name: `{{vaultName}}`{{/if}}
{{#if vaultType}}- Vault type: `{{vaultType}}`{{/if}}

Requirements:
1. Work inside `{{projectPath}}`.
2. Do not edit repository source files for this task unless a temporary local file is strictly required and removed before finishing.
3. First inspect the repository code and structure so the About text reflects the real project.
4. Before writing anything, inspect the current GitHub About state through local `gh`.
5. Apply the final update through local `gh`, then report exactly what changed.

Required runtime workflow:
1. Verify local GitHub CLI prerequisites.
   - Check `gh --version`.
   - Check `gh auth status --hostname github.com`.
   - If `gh` is missing, unauthenticated, or insufficiently authorized, stop without mutating metadata and explain the exact prerequisite failure in the session output.
2. Inspect the repository itself.
   - Read the most relevant files such as `README*`, package/solution manifests, app entrypoints, docs, and key source folders.
   - Identify the actual product type, audience, capabilities, stack, and distinguishing details.
3. Inspect the current GitHub About metadata from the repository context.
   - Use `gh repo view --json nameWithOwner,description,repositoryTopics,url`.
   - Record the current description and current topic list before deciding on changes.
4. Produce a minimal, evidence-based optimization.
   - Description must be concise, specific, and aligned with the repository's actual scope.
   - Topics must be relevant, deduplicated, and limited to a focused set.
   - Reuse any still-correct existing About data instead of rewriting everything blindly.
5. Apply the update.
   - Use `gh repo edit` from the current repository context.
   - Update the description.
   - Reconcile topics using `--add-topic` / `--remove-topic` or the equivalent `gh repo edit` arguments supported by the local CLI.
6. Verify the result.
   - Re-run `gh repo view --json nameWithOwner,description,repositoryTopics,url`.
   - Confirm the final About metadata matches what you intended.

Output expectations:
- Return a short execution summary.
- Include:
  - detected repository identity
  - old description/topics
  - new description/topics
  - commands executed at a high level
  - any assumptions or limitations

Safety constraints:
- Never guess repository facts that you can inspect locally.
- Do not touch homepage, social preview, releases, issues, or README content unless the task explicitly requires it.
- If the repository is not actually backed by GitHub despite this prompt being triggered, stop and explain the mismatch instead of forcing a write.
