[#2512] Add global search panel (#2526)

The file search feature only supports searching within a single
repository under one author.

Students in SWE courses find it useful to search across all
repositories to see how others implement certain files (e.g., testing
files, **/ug.md) by glob.

Let's add global search panel with mode toggle button in the summary
header. 

The implementation preserves the existing local search functionality
while introducing a new global search mode. A mode toggle button
replaces the text field to switch between local and global search. The
global search panel displays results across all authors and
repositories.

Author: FisherSkyi

docs/dg/report.md

@@ -127,6 +127,10 @@ The authorship module retrieves the relevant information from the corresponding
 ### Showing relevant information by authors
 The files will be filtered, picking only files the selected author has written in. The lines are then split into chunks of "touched" and "untouched" code segments displayed in the tab view which will be popped up on the right side of the screen.
 
+<!-- ==================================================================================================== -->
+## Global file browser view ([c-global-file-browser.vue](https://github.com/reposense/RepoSense/blob/master/frontend/src/views/c-global-file-browser.vue))
+The `c-global-file-browser` module is responsible for file filtering across repositories. It allows users to find files by glob and displays the results by path or by repository.
+
 <!-- ==================================================================================================== -->
 
 ## Zoom view ([c-zoom.vue](https://github.com/reposense/RepoSense/blob/master/frontend/src/views/c-zoom.vue))

docs/ug/usingReports.md

@@ -36,8 +36,7 @@ Here is an example of how a typical report looks like:
 
 ![report](../images/report-features.png)
 
-The report is divided into two sections: [_**Chart panel**_](#chart-panel) and the [_**Code panel**_](#code-panel). In some situations, the [_**Commits panel**_](#commits-panel) will appear in place of the _code panel_. All three are explained in the sections below.
-
+The report is divided into two sections: [_**Chart panel**_](#chart-panel) and the [_**Code panel**_](#code-panel). In some situations, the [_**Commits panel**_](#commits-panel) or the [_**Global file browser**_](#global-file-browser) will appear in place of the Code panel.
 <box type="info" seamless>
 
 Links to external webpages (repository link, author's profile, blame view, etc.) is only properly supported when RepoSense analyzes a remote repository belonging to GitHub, GitLab or BitBucket.
@@ -189,3 +188,81 @@ The `Commits panel` allows users to see the commits attributed to a specific aut
 * To promote and encourage the 50/72 rule for commit messages, a dotted vertical line will be shown for:
   * Commit message subject that exceeds 50 characters.
   * Commit message body after the 72nd character mark.
+
+## Global file browser panel
+
+The `Global file browser` provides a way to search and browse files across all repositories in the report. Unlike the [Code panel](#code-panel), which shows code attributed to a single author within one repository, the global file browser lets you explore files from every repository at once.
+
+#### Accessing the global file browser
+
+1. Locate the **filter mode** dropdown at the top of the tool bar.
+2. Select **Global** from the dropdown.
+3. The global file browser will appear on the right side of the report, replacing the Code panel.
+
+To return to the normal view, select **Local** from the dropdown. You can also click any author's %%:fas-code:%% or %%:fas-list-ul:%% icon in the Chart panel, which automatically switches the filter mode back to Local and opens the corresponding Code or Commits panel.
+
+<box type="info" seamless>
+
+When you switch to global mode, any previously highlighted author in the Chart panel is deselected. Likewise, switching back to Local mode (or clicking an author icon) closes the global file browser.
+</box>
+
+#### Filtering files with glob patterns
+
+The search input at the top of the panel filters files using [glob patterns](https://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob). The file count updates in real-time as you type.
+
+<box type="tip" seamless>
+
+Glob matching uses the `matchBase` option, so a pattern like `*.java` will match `src/main/App.java` even though the file is nested in subdirectories. You do not need to prefix every pattern with `**/`.
+</box>
+
+#### View modes
+
+The global file browser offers two view modes, toggled by the buttons below the search input:
+
+##### Sort By Path (default)
+
+Files from all repositories are displayed in a single flat list, sorted alphabetically by file path.
+
+##### Group By Repo
+
+Files are organized under collapsible repository headers, sorted alphabetically by repository name.
+
+Each repository group shows:
+* The **repository name** and **total file count** in the group header.
+* A **badge** that reads _Click to expand_ or _Click to collapse_, indicating the current state.
+* A **preview** of the top 3 matching files when the group is collapsed.
+* An **"and N more file(s)..."** link if the repository has more than 3 matching files. Clicking this link lists all remaining files (without expanding their contents).
+
+**Expanding all files in a repository group:** Click the **repository group header** to expand (or collapse) _all_ files in that group at once. This opens every file's content simultaneously, which is useful for quickly scanning an entire repository. Each repository group can be expanded and collapsed independently.
+
+<box type="info" seamless>
+
+Switching between _Sort By Path_ and _Group By Repo_ collapses all currently expanded files.
+</box>
+
+#### Viewing file contents
+
+Click on any non-binary, non-ignored file header to expand it and view its contents. Click the same header again to collapse it.
+
+The file content is displayed as **author-colored segments**:
+* Each contiguous block of lines written by the same author is shown as a segment with a **colored left border** identifying the author.
+* Hover over a segment to see a **tooltip** showing the author's name and whether they are the primary author or a co-author.
+
+<box type="info" seamless>
+
+Binary files (such as images, executables, and archives) and ignored files cannot be expanded. These files are indicated with yellow **binary** or **ignored** badges.
+</box>
+
+#### Use cases
+
+The global file browser is particularly useful for:
+
+* **Cross-repository code search**: Find files matching a specific pattern (e.g., `*.yml` for CI configs) across all repositories.
+* **Code review**: Quickly browse all files of a specific type and see who wrote each line.
+* **Comparing implementations**: Filter for files with similar names or extensions across different repositories to compare how they are implemented.
+* **Identifying authorship**: Expand files to see author-colored segments, making it easy to identify who contributed which parts of a file.
+
+<box type="tip" seamless>
+
+Combine glob patterns with the Group By Repo view to see how a specific file type is distributed across repositories. For example, filter by `**/*Test*.java` and switch to Group By Repo to see which repositories have Java test files and how many.
+</box>

frontend/cypress/tests/chartView/chartView_optimiseTimeline.cy.js

@@ -122,6 +122,10 @@ describe('optimise timeline', () => {
   it('subzoom panel range should work correctly when timeline is optimised', () => {
     const zoomKey = Cypress.platform === 'darwin' ? '{meta}' : '{ctrl}';
 
+    // Set granularity to commit to show individual commit slices
+    cy.get('div.mui-select.granularity > select:visible')
+      .select('Commit');
+
     cy.get('#summary label.optimise-timeline > input:visible')
       .should('be.visible')
       .check()

frontend/cypress/tests/chartView/chartView_reload.cy.js

@@ -5,10 +5,6 @@ describe('reload page', () => {
       .should('be.visible')
       .type('eugene');
 
-    // filter file
-    cy.get('.tooltip .mui-textfield.filter_file > input:visible')
-      .should('be.visible');
-
     // group by
     cy.get('div.mui-select.grouping > select:visible')
       .select('groupByAuthors');

frontend/cypress/tests/chartView/chartView_toolBar_searchBox.cy.js

@@ -1,9 +1,9 @@
 describe('search bar', () => {
   it('non-existent author shows no result', () => {
     cy.get('#app #tab-resize .tab-close').click();
-    // First one is the global file search, second one is the search for repos
+    // Get the search box (now the only text input after filter mode became a dropdown)
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('abcdef')
       .type('{enter}');
 
@@ -20,7 +20,7 @@ describe('search bar', () => {
   it('unique author shows one result', () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('Metta')
       .type('{enter}');
 
@@ -36,7 +36,7 @@ describe('search bar', () => {
   it('searching by non-existent tag shows no results', () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('tag: asdfghjkl')
       .type('{enter}');
 
@@ -50,7 +50,7 @@ describe('search bar', () => {
   it("searching tag that only exists in one author's commits shows one result", () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('tag: v1.8')
       .type('{enter}');
 
@@ -73,7 +73,7 @@ describe('search bar', () => {
   it("searching tag that only exists in two authors' commits shows two results", () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('tag: v1.10')
       .type('{enter}');
 
@@ -97,7 +97,7 @@ describe('search bar', () => {
   it("search field doesn't start with 'tag:' prefix but still contains it shows no results", () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('v1.10 tag: v1.10')
       .type('{enter}');
 
@@ -111,7 +111,7 @@ describe('search bar', () => {
   it("search field doesn't contain 'tag:' at all shows no results", () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('v1.10')
       .type('{enter}');
 
@@ -125,7 +125,7 @@ describe('search bar', () => {
   it('searching for multiple tags shows results containing all the tags searched', () => {
     cy.get('#app #tab-resize .tab-close').click();
     cy.get('#summary-wrapper input[type=text]')
-      .eq(1)
+      .eq(0)
       .type('tag: bb v1.10')
       .type('{enter}');
 

frontend/cypress/tests/codeView/codeView_renderFilterHash.cy.js

@@ -9,24 +9,6 @@ Cypress.on('uncaught:exception', (err) => {
 });
 
 describe('render filter hash', () => {
-  it('filter files: url params should persist after change and reload', () => {
-    cy.get('.tooltip .mui-textfield.filter_file > input:visible')
-      .should('be.visible')
-      .invoke('val')
-      .should('eq', '');
-
-    cy.get('.mui-textfield.filter_file > input:visible')
-      .should('be.visible')
-      .type('**java**{enter}');
-
-    cy.url()
-      .should('contain', 'filteredFileName=**java**');
-
-    cy.reload();
-
-    cy.url()
-      .should('contain', 'filteredFileName=**java**');
-  })
 
   it('search: url params should persist after change and reload', () => {
     /* Check initial state */