any_file_scope

The active editor may be a requirement file or implementation file ( Python, TypeScript, etc. ).
current_file_context must surface requirement links even when the file contains no block ideas.
Signals for non-. rq files ( and. rq files without a caret idea ):
- file_reference_links: `.rq` ideas whose outbound `file_reference` edges target this file path ( e. g. `apythonfile.py` ).
- folder_reference_links: `.rq` ideas whose `file_reference` targets a parent folder of this file.
- comment_reference_links: ideas resolved from `rq:…` tokens in this file's comments per references_in_functional_code_comments.
- git_context: focus-centric git history ( recent commits, authors, branch ); working-tree dirty badge secondary.
Focus behaviour:
- `.rq` file with caret in a block → idea focus ( unchanged ).
- Any file with linked requirements → file focus; effective_center_id defaults to the first linked requirement.
- No links → file focus with empty related lists; graph / refs panes stay idle until a requirement is focused.
Implementation: context-model.ts uses file-path-match.ts and `file_related_requirements` analyser; comment links are also resolved from live buffer text when indexed edges are absent.

Interactive page: any_file_scope