[GPCAPIM-304] Update repo documentation

.github/instructions/copilot-instructions.md

@@ -24,6 +24,10 @@ The container must be running in order to successfully run any of the test suite
 
 The schema for this API can be found in `gateway-api/openapi.yaml`.
 
+## Code reviews
+
+When reviewing code, ensure you compare the changes made to files to all README.md containing directory structures, and update the directory structures accordingly.
+
 ## Docstrings and comments
 
 - Use precise variable and function names to reduce the need for comments

bruno/README.md

@@ -1,18 +1,38 @@
 # Bruno
 
+## Bruno/ Structure
+
+```text
+bruno/
+├── README.md
+└── gateway-api/
+    ├── workspace.yml                                  # Bruno workspace configuration
+    └── collections/
+        ├── Steel_Thread/                              # Steel Thread request collection
+        │   ├── bruno.json                             # Bruno collection metadata
+        │   ├── collection.bru                         # Collection-level headers, auth config
+        │   ├── .env.template                          # Template for required env vars (see below)
+        │   ├── Access_Structured_Record.bru            # Request: POST $gpc.getstructuredrecord
+        │   └── environments/                          # Per-target environment configs
+        │       ├── local.bru                           # Points at local container
+        │       └── PR_Proxy.bru                        # Points at Apigee PR proxy
+```
+
+> **Note:** `.env` files are git-ignored and must be created locally from the `.env.template`.
+
 ## `gateway-api` Workspace
 
 ### Steel Thread Collection
 
 #### Environment Setup
 
-The collection pulls in secrets from a `.env` file from the top level of the collection, `bruno/gateway-api/preview-env`. To reference these variables within the collection you use `{{process.env.<key>}}`, where `<key>` is the environment variable name in `.env`.
+The collection pulls in secrets from a `.env` file at the top level of the collection (`bruno/gateway-api/collections/Steel_Thread/.env`). To reference these variables within the collection you use `{{process.env.<key>}}`, where `<key>` is the environment variable name in `.env`.
 
-There is a template `.env` file, `bruno/gateway-api/collections/preview-env/.env.template`, to fill in as described below.
+There is a template `.env` file, `bruno/gateway-api/collections/Steel_Thread/.env.template`, to fill in as described below.
 
 ##### Test application
 
-The proxy for Gateway API is hosted in Apigee. In order to call an Apigee proxy, a consumer of the API needs an Apigee application. As such, we need an Apigee application through which we can test our API. A static test application has been created for this purpose. You can view its details by going through In order to view its details, go to [the Clinical Data Sharing APIs applications](https://dos-internal.ptl.api.platform.nhs.uk/). when making a call to the API through the proxy, the test applications API key and secret are fed in to the OAuth 2.0 journey as the `CLIENT_KEY` and `CLIENT_SECRET` respectively. As such, you will need a `bruno/gateway-api/preview-preview-env/.env` file containing
+The proxy for Gateway API is hosted in Apigee. To call this proxy, you need an Apigee application. A static test application has been created for this purpose. You can view its details in [the Clinical Data Sharing APIs applications](https://dos-internal.ptl.api.platform.nhs.uk/). When making a call to the API through the proxy, the test application's API key and secret are fed into the OAuth 2.0 journey as the `CLIENT_KEY` and `CLIENT_SECRET` respectively. As such, you will need a `bruno/gateway-api/collections/Steel_Thread/.env` file containing
 
 ```plaintext
 CLIENT_ID=<test application's api key>