Namespace Kuestenlogik.Bowire.Projects

BowireProjectFile: The checked-in .bowire/project.json convention (#172): a version-controlled MANIFEST that makes a repository the source of truth for "what this repo's API looks like". It does not carry the artifacts itself — it POINTS at them (schemas, collection/suite files, an auth flow, a rules file) with project-relative paths, so CI, the PR bot, and onboarding all resolve the same setup automatically instead of re-configuring per job.

BowireProjectLoader: Auto-discovery + loading for the .bowire/project.json convention (#172). Discover(string?) walks UP the directory tree from a start directory (default: the current working directory) looking for .bowire/project.json — the same "find the nearest config walking toward the repo root" shape git, npm, and dotnet use — so a command run anywhere inside a checkout picks up the project without a flag. It never throws on "not found": it returns null, and the caller decides whether that's an error. Load(string) reads a specific file and hands the text to Parse(string?) (which throws on malformed / shape-invalid content).

BowireProjectLocation: A located manifest: the resolved file path plus the project root — the directory that CONTAINS .bowire/, so the manifest's project-relative paths (schemas, suites, auth flow, rules) resolve against it.

BowireProjectSecurity: The security block: the auth flow to run and the scan profiles to apply.

BowireProjectSource: An API source the project exposes: a base URL and its schema files.

BowireStorageRoot: Decides where a Bowire instance keeps its collections, environments, recordings and presets (#591).

Sections