## What changed
- authorize mobile issue-filing metadata once, then load labels, milestones, and templates concurrently
- isolate section failures so blank filing and healthy metadata remain usable
- route searchable, restored-draft, and native repository selection through one stale-response-safe loader
- keep the aggregate UI controller in the lazy issue-capture feature chunk
## Verification
- RED: aggregate route test failed with 404 before implementation
- RED: aggregate client test failed because `loadFilingMetadata` was absent
- RED: stale repository response test accepted old metadata before request generation was added
- focused tests passed
- `python3 -m pytest tests/ -q` → 1605 passed
Closes #847
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What changed
Verification
loadFilingMetadatawas absentpython3 -m pytest tests/ -q→ 1605 passedCloses #847