Core PR Helper

When the user asks for a branch name and PR description for core:

1. Infer the change from the conversation (recent edits, stated scope, or ask briefly if unclear).
2. Output one branch name, then the PR body in the exact format below.

Branch name

• One name only. Use lowercase, hyphens; no slashes.
• Pattern: {type}-{scope}-{short-summary} (e.g. feat-meroctl-install-flow, fix-runtime-wasm-imports).
• Types (match repo commit types): feat, fix, docs, refactor, test, chore, perf, build, ci, style, revert.
• Scope: crate or area (e.g. meroctl, runtime, sdk, server, network, storage). Omit scope if change is cross-cutting.

PR description format

Use this structure exactly (matches .github/pull_request_template.md). Fill each section from the inferred change; keep placeholders only where the user must fill in (e.g. issue number, links).

markdown
1# [product] short description
2
3Replace `[product]` with the crate or area (e.g. `[meroctl]`, `[runtime]`, `[sdk]`). Use imperative mood for the description (e.g. "Add install flow" or "Fix WASM import resolution").
4
5## Description
6
7Brief description of the change and which issue is fixed (if any). Include relevant motivation and context. List any dependencies that are required for this change.
8
9## Test plan
10
11What was run to verify (e.g. `cargo test -p crate-name`, manual steps). Is it possible to add a test case to the e2e tests? For UI changes, mention screenshots or videos if applicable.
12
13## Documentation update
14
15Which public or internal docs (if any) need updates. If none, state "None" or "N/A". Note: documentation **has to be updated** no later than **one day** after merge.

Output

1. Branch: single-branch-name
2. PR description: (the filled template as above)

Do not offer multiple branch names; choose the single most appropriate one.