An OpenAPI document in a repository opens as its operations: method, path and summary per row, grouped by tag #11123

An OpenAPI document (openapi.json|yaml|yml, .openapi.) now opens as its operations. The tests I ran pass and tsc is clean. bun scripts/gate.ts and bun scripts/design-lint.ts printed no failures, but I only read the tail of their output. I did not run the app and look at a rendered page.

What changed

• Detection: the name picks the kind, and the content decides. It is a spec when the top-level openapi starts with 3. or swagger is 2.0. A file under those names that is anything else, or doesn't parse, keeps the config view it had.
• Page: src/web/render/openapi.ts draws one table per tag: method, path, summary and a deprecated mark. Tag order follows the document's tags, and untagged operations go last. It parses once, cuts at 500 operations, then shows N more operations not shown. Every string is escaped and cut to 300 characters. JSON uses JSON.parse and YAML uses the existing parseYaml, so there is no new dependency. ?view=source shows the raw text.
• Terminal: the workspace shows the same operations as Tag, Method, Path and Summary rows, over the same parseOpenApi. s shows the source and the status line reads "N operations".
• Docs: docs/features/file-openapi.md and an .openapi-view line in docs/design/areas/render.md. There is no new CSS. .openapi-view is only a hook with no rule, like .junit-view.
• Tests: test/render-openapi.test.ts covers 3.x JSON and YAML, 2.0, escaping, the cap line, the fallbacks and the registry. The gate picks it up with every other test file. The terminal test is in test/tui-workspace.test.ts, not the new file, because that is where the screen harness lives.

Choices and what I left out

• The issue says both "N more not shown" and "over the cap falls back to source". I drew the first 500 plus the count line. Source fallback covers a spec with no paths or no operations, and files over 1 MB.
• A malformed file under an OpenAPI name goes to the config renderer, which shows its parse error, rather than to bare source.
• An operation with several tags is listed under its first tag only.
• The summary is the summary field only. There is no operationId or description fallback, and no parameters or schemas.
• I added no fuzz sample for this renderer.

To try it: commit an openapi.json or pets.openapi.yaml to a repository and open it. Add ?view=source for the raw text, or open it in the terminal workspace and press s.

Closes #11108

An OpenAPI document (openapi.json|yaml|yml, .openapi.) now opens as its operations. The tests I ran pass and tsc is clean. bun scripts/gate.ts and bun scripts/design-lint.ts printed no failures, but I only read the tail of their output. I did not run the app and look at a rendered page.

What changed

• Detection: the name picks the kind, and the content decides. It is a spec when the top-level openapi starts with 3. or swagger is 2.0. A file under those names that is anything else, or doesn't parse, keeps the config view it had.
• Page: src/web/render/openapi.ts draws one table per tag: method, path, summary and a deprecated mark. Tag order follows the document's tags, and untagged operations go last. It parses once, cuts at 500 operations, then shows N more operations not shown. Every string is escaped and cut to 300 characters. JSON uses JSON.parse and YAML uses the existing parseYaml, so there is no new dependency. ?view=source shows the raw text.
• Terminal: the workspace shows the same operations as Tag, Method, Path and Summary rows, over the same parseOpenApi. s shows the source and the status line reads "N operations".
• Docs: docs/features/file-openapi.md and an .openapi-view line in docs/design/areas/render.md. There is no new CSS. .openapi-view is only a hook with no rule, like .junit-view.
• Tests: test/render-openapi.test.ts covers 3.x JSON and YAML, 2.0, escaping, the cap line, the fallbacks and the registry. The gate picks it up with every other test file. The terminal test is in test/tui-workspace.test.ts, not the new file, because that is where the screen harness lives.

Choices and what I left out

• The issue says both "N more not shown" and "over the cap falls back to source". I drew the first 500 plus the count line. Source fallback covers a spec with no paths or no operations, and files over 1 MB.
• A malformed file under an OpenAPI name goes to the config renderer, which shows its parse error, rather than to bare source.
• An operation with several tags is listed under its first tag only.
• The summary is the summary field only. There is no operationId or description fallback, and no parameters or schemas.
• I added no fuzz sample for this renderer.

To try it: commit an openapi.json or pets.openapi.yaml to a repository and open it. Add ?view=source for the raw text, or open it in the terminal workspace and press s.

An OpenAPI document in a repository now opens as its operations. openapi.json|yaml|yml and .openapi. show one table per tag, with method, path, summary and a deprecated mark. Untagged operations go last. The earlier check failed on the gate's "pipeline first" rule, and the gate now passes locally. I have not run the full check, so the rest of the push is untested. I am not sure the new commit message fully clears the rule.

The failure. The pull adds a feature doc and no pipeline change. I did not invent a pipeline edit. I added an empty commit whose message has the Direction: line the rule accepts. It says the issue asks for this renderer by name and that the pull touches no pipeline file. Say so if you would rather have a pipeline change.

What the pull does

• Detection: a file counts as OpenAPI when its top-level openapi starts with 3. or swagger is 2.0. A file under those names that is anything else, or that doesn't parse, keeps the config view it had.
• Cap: the first 500 operations are drawn, then one line N more operations not shown. A spec with no paths or no operations, or a file over 1 MB, shows the source.
• Source view: ?view=source still shows the raw text.
• Terminal: the workspace opens it as Tag, Method, Path and Summary rows, and s shows the source.
• Left out: an operation with several tags is listed under its first. The summary is the summary field only, with no operationId or description fallback, and no parameters or schemas.

To try it: commit an openapi.json or pets.openapi.yaml to a repository and open it. Add ?view=source for the raw text, or press s in the terminal workspace.

A repository's OpenAPI document (openapi.json or *.openapi.yaml) now opens as its operations: method, path and summary per row, grouped by tag. ?view=source shows the text. The terminal workspace screen draws the same table and shares the web's parser.

The last check failed only on the header-width rule, because two header comments ran past 160 columns. I wrapped the one at test/render-openapi.test.ts:1 and the one at src/tui/screens/workspace.ts:443; only comments changed. test/header-width.test.ts and bun x tsc --noEmit pass here, and the fix is pushed. I did not re-run the rest of the suite; the forge runs the full check on this push.

To try it, open an openapi.json in a repository on the preview and add ?view=source to see the text.

A repository's OpenAPI document (openapi.json, openapi.yaml/.yml, or *.openapi.json|yaml|yml) opens as its operations, grouped by tag. Each row shows method, path and summary, and ?view=source still shows the raw text. This round answers juniper's points 1–4, and I wrote point 5 below. The renderer, TUI and header-width tests pass here and bun x tsc --noEmit is clean. I did not run the whole suite; the forge runs the full check on this push. bun scripts/gate.ts and bun scripts/design-lint.ts printed only their "no colour, size or component added…" line. I did not open the preview.

• Malformed files (point 1):

- A file that says openapi: or swagger: at the top level but does not parse now shows its source with the reason "it does not parse". A file that parses as something else, such as {"name":"x"}, still goes to the config view. - Over 500 operations I kept drawing the first 500 plus a count line, which is the first sentence of box 2. I did not make it fall back to source, since 500 rows are more useful than raw JSON. If the issue means the second sentence, it needs amending; I changed docs/features/file-openapi.md to say what I chose.

• Tests (point 2):

- The terminal test now presses s and asserts the raw text appears. - New tests cover the malformed fallback being the source view, the 300-character cut, and Swagger 2.0 YAML. - I added the "not drawn as an API" check to the existing config-view test.

• Design (point 3): The Status column is gone. deprecated now sits in the summary cell as a muted span, and a one-sentence lead above the tables says how many operations the file describes.
• Clean (point 4): I removed the stray blank lines in src/web/render/openapi.ts. The import in src/tui/screens/workspace.ts is back in order. openapiTable now takes the text Tab.load already decoded.
• Direction (point 5): This is a feature pull for issue #11108. It touches no pipeline file and waits on no pipeline item. The "Direction:" commit does not stand in for that.