ginee-file-framework-buglisted

# File framework-bug — upstream Run the file-an-issue workflow per `.agents/ginee/core/protocols/github-integration.md § Outbound — file an issue` with target = framework upstream, template = framework-bug-report. ## Activation - User asks to "file a framework bug" / "report an issue against ginee" / "file a bug against the framework". - User describes a defect in framework files (`core/*`, `adapters/*`, `extras/*`, templates). ## Procedure 1. Load `.agents/ginee/core/protocols/github-integration.md` and `.agents/ginee/core/templates/issues/framework-bug-report.md`. 2. Resolve target repo: - `local/framework.config.yaml § github.framework-repo` is required. - If unset → fail fast: "framework-repo not configured. Set `github.framework-repo: <owner>/ginee` in `local/framework.config.yaml` first." Offer to populate it. 3. Draft the body from the framework-bug-report template. Populate `## Summary`, `## Affected framework artefact` (process / role-kernel / role-details / template / adapter / extras-role / spec), `## Framework version` (from `.agents/ginee/core/VERSION`), `## Adapter in use`, `## Reproduction`, `## Expected framework behavior`, `## Actual framework behavior`, `## Blocking severity`, `## Workaround`, `## Owner-history pointers` (optional — short slugs into PLAN.md if the bug overlaps prior decisions), `## Acceptance criteria`. 4. **Self-lint the draft** against `.agents/ginee/core/process.md § Mandatory checks before report-as-done` — **every section, in