Retire scripts/Get-EpicReport once star gh issues report ships from the base layer; declare gh.repositories and gh.exempt in star/config.yaml #797

Feature: NobleFactor/noblefactor-ops#140 — the epic report as a star extension shipped by the base layer.

Rewritten 2026-09-05 after that feature's Phase 1 landed; the earlier text named a command, a config
file and a config shape that no longer exist.

When the extension ships from the base layer, this repository:

• declares its config in star/config.yaml:

  gh:
      repositories:
          - NobleFactor/devlore-cli
          - NobleFactor/noblefactor-ops
      exempt: [65]

  Threads are not declared — they are discovered from Thread:<Name> labels. exempt is flat
  under gh, not gh.issues.exempt: the extension spec accepts a nested: block and the runtime
  does not build it (a bug filed from that Phase 1).

• removes scripts/Get-EpicReport, and its mention from make shell-lint's sweep if any

• says in the development-process guide that the report is
  star gh issues report --epic <Name> --view table --state all --markdown -o value

Phase 1 is at byte parity with the script on this repository: --view tree --state all, 775 lines,
with gh.exempt: [65] supplied. Blocked on the remaining phases of noblefactor-ops#140 — the
configured repository set, threads in beat order, the empty-level states — since retiring the script
before --by thread works would lose the thread report.