briar-cli 1.1.45__tar.gz → 1.1.47__tar.gz

{briar_cli-1.1.45 → briar_cli-1.1.47}/.gitignore

@@ -31,3 +31,6 @@ config.json
 
 # Real-company runbooks + planning docs — kept local, not for public repo
 runbooks/
+
+# Local Claude Code workspace (worktrees, caches)
+.claude/

{briar_cli-1.1.45 → briar_cli-1.1.47}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: briar-cli
-Version: 1.1.45
+Version: 1.1.47
 Summary: Terminal client for the Briar agent-orchestration API.
 Project-URL: Homepage, https://usebriar.com
 Project-URL: Source, https://github.com/iklobato/briar
@@ -61,6 +61,7 @@ Requires-Dist: azure-mgmt-subscription<4,>=3.1; extra == 'azure'
 Provides-Extra: dev
 Requires-Dist: black<26,>=25; extra == 'dev'
 Requires-Dist: mypy<2,>=1.13; extra == 'dev'
+Requires-Dist: ruff<1,>=0.6; extra == 'dev'
 Provides-Extra: gcp
 Requires-Dist: google-api-python-client<3,>=2.100; extra == 'gcp'
 Requires-Dist: google-auth<3,>=2.20; extra == 'gcp'
@@ -129,7 +130,7 @@ export ANTHROPIC_API_KEY=sk-ant-...        # LLM key comes from the environment
 # 2. Mine a repo's PR history into a knowledge blob
 briar extract --company acme \
     --include pr-archaeology \
-    --pr-repo acme-co/acme-app --pr-max 50
+    --repo acme-co/acme-app --max 50
 
 # 3. Read it back
 briar context get knowledge:acme
@@ -137,6 +138,41 @@ briar context get knowledge:acme
 
 > **Telemetry:** `briar` ships with opt-out error/usage analytics (Sentry). No prompts, file contents, ticket keys, repo names, paths, or secret values ever leave the machine. Turn it off any time with `briar telemetry off`, `BRIAR_TELEMETRY=off`, or `DO_NOT_TRACK=1`.
 
+### Less typing: shared flags, project config, inference
+
+briar resolves every flag through one chain — **CLI flag > env var > project config > built-in default** — so the stable values move off the command line:
+
+```toml
+# .briar.toml (or [tool.briar] in pyproject.toml), searched upward from cwd
+company = "acme"
+store   = "postgres"
+
+[repo]
+owner = "acme-co"
+repo  = "acme-app"
+```
+
+With that file present, and inside the git checkout, the same extract is just:
+
+```bash
+briar extract --include pr-archaeology        # company + repo come from config/git
+```
+
+- **Canonical extractor flags.** One shared knob per concept — `--repo`, `--since-days`, `--max`, `--top-n`, `--sample`, `--authors-allow/-block`, `--assignees-allow/-block` — applies to every extractor selected with `--include`. The old per-extractor flags (`--pr-repo`, `--risk-since-days`, …) still work but are hidden from `-h`; run `briar extract --advanced-help` to see them.
+- **Inference.** `--owner`/`--repo` are read from the git `origin` remote when neither the flag nor config supplies them.
+- A per-extractor override always wins over the shared flag when both are given.
+
+Helpers for the config + setup loop:
+
+```bash
+briar init                 # write a starter .briar.toml (repo inferred from git)
+briar config show          # see each setting's resolved value AND its source
+briar doctor               # check config, git, credentials, store (CI-usable exit code)
+eval "$(briar completion bash)"   # tab-completion (also: zsh)
+```
+
+Other niceties: `briar --version`, quiet-by-default logs (logs to stderr, `--verbose` for DEBUG), and a once-a-day "new version available" nudge (opt out with `BRIAR_NO_UPDATE_CHECK=1` / `DO_NOT_TRACK=1`).
+
 ---
 
 ## What you can do
@@ -147,8 +183,8 @@ briar context get knowledge:acme
 # PRs + AWS infra in one shot, filtered to your team
 briar extract --company acme \
     --include pr-archaeology --include aws-infra \
-    --pr-repo acme-co/acme-app \
-    --pr-authors-allow alice --pr-authors-allow bob \
+    --repo acme-co/acme-app \
+    --authors-allow alice --authors-allow bob \
     --aws-extract-region us-east-1 \
     --aws-extract-service ecs --aws-extract-service rds
 
@@ -161,12 +197,11 @@ FIREFLIES_ACME_API_KEY=ff_xxx briar extract --company acme \
     --include meeting-digest --meeting-since-days 14 \
     --meeting-attendee-allow alice@acme.com
 
-# Code-quality signal from git history + the repo-host API
-briar extract --company acme \
-    --include defect-hotspots --risk-repo acme-co/acme-app \
-    --include pr-hygiene --prhygiene-repo acme-co/acme-app \
-    --include review-nits --nits-repo acme-co/acme-app \
-    --include ci-health --cihealth-repo acme-co/acme-app
+# Code-quality signal from git history + the repo-host API.
+# One --repo feeds every selected extractor.
+briar extract --company acme --repo acme-co/acme-app \
+    --include defect-hotspots --include pr-hygiene \
+    --include review-nits --include ci-health
 ```
 
 **Code-quality extractors** (all `--provider github|bitbucket`): `defect-hotspots`
@@ -181,8 +216,8 @@ briar extract --company acme \
 ```bash
 # Merge a knowledge index into CLAUDE.md; full detail lands in
 # .briar/knowledge/<company>.md for the agent to read when relevant.
-briar extract --company acme --include defect-hotspots --include ci-health \
-    --risk-repo acme-co/acme-app --cihealth-repo acme-co/acme-app \
+briar extract --company acme --repo acme-co/acme-app \
+    --include defect-hotspots --include ci-health \
     --merge-claude-md
 ```
 
@@ -254,33 +289,40 @@ Plus `briar context` (local knowledge blobs), `briar dashboard` (read-only HTML
 ### Repeatable flags — fan out across repos, projects, services
 
 Most list-style flags accept multiple occurrences: repeat the flag, once
-per value (there's no comma form — `--pr-repo a,b` is one repo named
-`a,b`). Mix them to cover a whole fleet in a single command.
+per value (there's no comma form — `--repo a,b` is one repo named `a,b`).
+The canonical `--repo` feeds every extractor selected with `--include`.
 
 ```bash
-# Mine several repos, keep the team's PRs, drop the bots, across two boards.
-# --pr-max applies per repo; author allow/block compose as allow ∩ ¬block.
+# Mine several repos, keep the team's PRs, drop the bots — one --repo,
+# every selected extractor. --max applies per repo; author allow/block
+# compose as allow ∩ ¬block.
 briar extract --company acme \
-    --include pr-archaeology --include active-tickets \
-    --tracker jira \
-    --pr-repo acme-co/web --pr-repo acme-co/api --pr-repo acme-co/mobile \
-    --pr-max 75 \
-    --pr-authors-block "dependabot[bot]" --pr-authors-block "renovate[bot]" \
-    --ticket-project ACME --ticket-project PLAT
-
-# Scaffold a triage flow from two sources, filtered by author + assignee.
-# Each tracker source carries its own repeatable *-authors/assignees-*.
+    --include pr-archaeology --include defect-hotspots \
+    --repo acme-co/web --repo acme-co/api --repo acme-co/mobile \
+    --max 75 \
+    --authors-block "dependabot[bot]" --authors-block "renovate[bot]"
+
+# Scaffold a triage flow from two sources — one shared author/assignee
+# filter applies to every --source.
 briar scaffold implementation --prefix acme-triage \
     --source github --source jira \
     --owner acme-co --repo acme-app --github-secret-id <uuid> \
-    --github-authors-block "dependabot[bot]" \
-    --github-assignees-allow alice --github-assignees-allow bob \
+    --authors-block "dependabot[bot]" \
+    --assignees-allow alice --assignees-allow bob \
     --jira-project ACME --jira-project PLAT --jira-secret-id <uuid> \
     --auth-mode pat
 ```
 
-The same lists map onto runbook YAML as arrays — e.g. `pr_repo:
-[acme-co/web, acme-co/api]` is two `--pr-repo` flags.
+The same lists map onto runbook YAML as arrays — e.g. `repo:
+[acme-co/web, acme-co/api]` under an extractor's `args:`.
+
+> **Divergent identifiers in one run.** Some extractors key off a tracker
+> *project* (`active-tickets`, `ticket-archaeology`) rather than an
+> `owner/repo` slug. When you run those alongside repo-based extractors in
+> a single invocation and they need *different* values, reach for the
+> per-extractor override flags (`--ticket-project`, `--pr-repo`, … — listed
+> by `briar extract --advanced-help`), or split into two invocations. The
+> runbook YAML models this cleanly: one `args:` block per extractor.
 
 ### Handy patterns
 

{briar_cli-1.1.45 → briar_cli-1.1.47}/README.md

@@ -37,7 +37,7 @@ export ANTHROPIC_API_KEY=sk-ant-...        # LLM key comes from the environment
 # 2. Mine a repo's PR history into a knowledge blob
 briar extract --company acme \
     --include pr-archaeology \
-    --pr-repo acme-co/acme-app --pr-max 50
+    --repo acme-co/acme-app --max 50
 
 # 3. Read it back
 briar context get knowledge:acme
@@ -45,6 +45,41 @@ briar context get knowledge:acme
 
 > **Telemetry:** `briar` ships with opt-out error/usage analytics (Sentry). No prompts, file contents, ticket keys, repo names, paths, or secret values ever leave the machine. Turn it off any time with `briar telemetry off`, `BRIAR_TELEMETRY=off`, or `DO_NOT_TRACK=1`.
 
+### Less typing: shared flags, project config, inference
+
+briar resolves every flag through one chain — **CLI flag > env var > project config > built-in default** — so the stable values move off the command line:
+
+```toml
+# .briar.toml (or [tool.briar] in pyproject.toml), searched upward from cwd
+company = "acme"
+store   = "postgres"
+
+[repo]
+owner = "acme-co"
+repo  = "acme-app"
+```
+
+With that file present, and inside the git checkout, the same extract is just:
+
+```bash
+briar extract --include pr-archaeology        # company + repo come from config/git
+```
+
+- **Canonical extractor flags.** One shared knob per concept — `--repo`, `--since-days`, `--max`, `--top-n`, `--sample`, `--authors-allow/-block`, `--assignees-allow/-block` — applies to every extractor selected with `--include`. The old per-extractor flags (`--pr-repo`, `--risk-since-days`, …) still work but are hidden from `-h`; run `briar extract --advanced-help` to see them.
+- **Inference.** `--owner`/`--repo` are read from the git `origin` remote when neither the flag nor config supplies them.
+- A per-extractor override always wins over the shared flag when both are given.
+
+Helpers for the config + setup loop:
+
+```bash
+briar init                 # write a starter .briar.toml (repo inferred from git)
+briar config show          # see each setting's resolved value AND its source
+briar doctor               # check config, git, credentials, store (CI-usable exit code)
+eval "$(briar completion bash)"   # tab-completion (also: zsh)
+```
+
+Other niceties: `briar --version`, quiet-by-default logs (logs to stderr, `--verbose` for DEBUG), and a once-a-day "new version available" nudge (opt out with `BRIAR_NO_UPDATE_CHECK=1` / `DO_NOT_TRACK=1`).
+
 ---
 
 ## What you can do
@@ -55,8 +90,8 @@ briar context get knowledge:acme
 # PRs + AWS infra in one shot, filtered to your team
 briar extract --company acme \
     --include pr-archaeology --include aws-infra \
-    --pr-repo acme-co/acme-app \
-    --pr-authors-allow alice --pr-authors-allow bob \
+    --repo acme-co/acme-app \
+    --authors-allow alice --authors-allow bob \
     --aws-extract-region us-east-1 \
     --aws-extract-service ecs --aws-extract-service rds
 
@@ -69,12 +104,11 @@ FIREFLIES_ACME_API_KEY=ff_xxx briar extract --company acme \
     --include meeting-digest --meeting-since-days 14 \
     --meeting-attendee-allow alice@acme.com
 
-# Code-quality signal from git history + the repo-host API
-briar extract --company acme \
-    --include defect-hotspots --risk-repo acme-co/acme-app \
-    --include pr-hygiene --prhygiene-repo acme-co/acme-app \
-    --include review-nits --nits-repo acme-co/acme-app \
-    --include ci-health --cihealth-repo acme-co/acme-app
+# Code-quality signal from git history + the repo-host API.
+# One --repo feeds every selected extractor.
+briar extract --company acme --repo acme-co/acme-app \
+    --include defect-hotspots --include pr-hygiene \
+    --include review-nits --include ci-health
 ```
 
 **Code-quality extractors** (all `--provider github|bitbucket`): `defect-hotspots`
@@ -89,8 +123,8 @@ briar extract --company acme \
 ```bash
 # Merge a knowledge index into CLAUDE.md; full detail lands in
 # .briar/knowledge/<company>.md for the agent to read when relevant.
-briar extract --company acme --include defect-hotspots --include ci-health \
-    --risk-repo acme-co/acme-app --cihealth-repo acme-co/acme-app \
+briar extract --company acme --repo acme-co/acme-app \
+    --include defect-hotspots --include ci-health \
     --merge-claude-md
 ```
 
@@ -162,33 +196,40 @@ Plus `briar context` (local knowledge blobs), `briar dashboard` (read-only HTML
 ### Repeatable flags — fan out across repos, projects, services
 
 Most list-style flags accept multiple occurrences: repeat the flag, once
-per value (there's no comma form — `--pr-repo a,b` is one repo named
-`a,b`). Mix them to cover a whole fleet in a single command.
+per value (there's no comma form — `--repo a,b` is one repo named `a,b`).
+The canonical `--repo` feeds every extractor selected with `--include`.
 
 ```bash
-# Mine several repos, keep the team's PRs, drop the bots, across two boards.
-# --pr-max applies per repo; author allow/block compose as allow ∩ ¬block.
+# Mine several repos, keep the team's PRs, drop the bots — one --repo,
+# every selected extractor. --max applies per repo; author allow/block
+# compose as allow ∩ ¬block.
 briar extract --company acme \
-    --include pr-archaeology --include active-tickets \
-    --tracker jira \
-    --pr-repo acme-co/web --pr-repo acme-co/api --pr-repo acme-co/mobile \
-    --pr-max 75 \
-    --pr-authors-block "dependabot[bot]" --pr-authors-block "renovate[bot]" \
-    --ticket-project ACME --ticket-project PLAT
-
-# Scaffold a triage flow from two sources, filtered by author + assignee.
-# Each tracker source carries its own repeatable *-authors/assignees-*.
+    --include pr-archaeology --include defect-hotspots \
+    --repo acme-co/web --repo acme-co/api --repo acme-co/mobile \
+    --max 75 \
+    --authors-block "dependabot[bot]" --authors-block "renovate[bot]"
+
+# Scaffold a triage flow from two sources — one shared author/assignee
+# filter applies to every --source.
 briar scaffold implementation --prefix acme-triage \
     --source github --source jira \
     --owner acme-co --repo acme-app --github-secret-id <uuid> \
-    --github-authors-block "dependabot[bot]" \
-    --github-assignees-allow alice --github-assignees-allow bob \
+    --authors-block "dependabot[bot]" \
+    --assignees-allow alice --assignees-allow bob \
     --jira-project ACME --jira-project PLAT --jira-secret-id <uuid> \
     --auth-mode pat
 ```
 
-The same lists map onto runbook YAML as arrays — e.g. `pr_repo:
-[acme-co/web, acme-co/api]` is two `--pr-repo` flags.
+The same lists map onto runbook YAML as arrays — e.g. `repo:
+[acme-co/web, acme-co/api]` under an extractor's `args:`.
+
+> **Divergent identifiers in one run.** Some extractors key off a tracker
+> *project* (`active-tickets`, `ticket-archaeology`) rather than an
+> `owner/repo` slug. When you run those alongside repo-based extractors in
+> a single invocation and they need *different* values, reach for the
+> per-extractor override flags (`--ticket-project`, `--pr-repo`, … — listed
+> by `briar extract --advanced-help`), or split into two invocations. The
+> runbook YAML models this cleanly: one `args:` block per extractor.
 
 ### Handy patterns
 

{briar_cli-1.1.45 → briar_cli-1.1.47}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "briar-cli"
-version = "1.1.45"
+version = "1.1.47"
 description = "Terminal client for the Briar agent-orchestration API."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -59,6 +59,7 @@ test = [
 dev = [
     "black>=25,<26",
     "mypy>=1.13,<2",
+    "ruff>=0.6,<1",  # linter — same tool the quality hook + `make lint` use
 ]
 # Adapter SDKs are opt-in extras so a base install stays minimal. Operators
 # only install what they actually use. Each adapter's `is_available()`

{briar_cli-1.1.45 → briar_cli-1.1.47}/src/briar/cli.py

@@ -10,6 +10,11 @@ from __future__ import annotations
 
 import warnings
 
+# E402 is expected here: the warnings filter below MUST run before any
+# pydantic-importing module loads, so the rest of the imports follow it.
+# ruff: noqa: E402
+
+
 # pydantic's plugin loader scans installed packages for plugins at import
 # time. When logfire is installed but its pinned opentelemetry-sdk symbol
 # drifts (ReadableLogRecord was renamed upstream), the loader emits a
@@ -37,7 +42,7 @@ from briar.logging import env_verbose
 #   GLOBAL_FLAGS_WITH_VALUE: `--format yaml` / `--format=yaml`
 #   GLOBAL_BOOL_FLAGS:       `--verbose` / `-v` (no value)
 _GLOBAL_FLAGS_WITH_VALUE: Set[str] = {"--format"}
-_GLOBAL_BOOL_FLAGS: Set[str] = {"--verbose", "-v"}
+_GLOBAL_BOOL_FLAGS: Set[str] = {"--verbose", "-v", "--version", "-V"}
 
 
 def _extract_global_flags(argv: List[str]) -> Tuple[Dict[str, str], Set[str], List[str]]:
@@ -94,6 +99,14 @@ def _build_parser(commands: Dict[str, Command]) -> argparse.ArgumentParser:
         action="store_true",
         help="enable DEBUG-level logging (also honours BRIAR_VERBOSE=1 env var)",
     )
+    # `--version` is short-circuited in `main()` before any I/O; declared
+    # here so `briar --help` lists it.
+    parser.add_argument(
+        "--version",
+        "-V",
+        action="store_true",
+        help="print client version and exit",
+    )
     sub = parser.add_subparsers(dest="command", required=True, metavar="COMMAND")
     for name, cmd in commands.items():
         sp = sub.add_parser(name, help=cmd.help)
@@ -101,6 +114,40 @@ def _build_parser(commands: Dict[str, Command]) -> argparse.ArgumentParser:
     return parser
 
 
+def _notify_update(log: logging.Logger) -> None:
+    """Best-effort 'newer version available' notice on stderr. Throttled +
+    opt-out + swallow-on-error inside `update_check.maybe_notify`; the
+    extra guard here keeps even an import error from touching the exit."""
+    try:
+        from briar import __version__
+        from briar.update_check import maybe_notify
+
+        notice = maybe_notify(__version__)
+        if notice:
+            print(notice, file=sys.stderr)
+    except Exception:  # noqa: BLE001 — an update nudge must never break the CLI
+        log.debug("update-check: notify failed", exc_info=True)
+
+
+def _warn_legacy_flags(raw_argv: List[str], log: logging.Logger) -> None:
+    """One consolidated stderr note when the command line uses a legacy
+    per-extractor / per-source flag that a canonical flag now covers.
+
+    A plain print, NOT a `warnings.warn` — the test suite runs with
+    `filterwarnings=error`, and this is user guidance, not a code smell."""
+    from briar.extract.canonical import legacy_flag_suggestions
+
+    suggestions = legacy_flag_suggestions(raw_argv)
+    if not suggestions:
+        return
+    pairs = ", ".join(f"{old} → {new}" for old, new in sorted(suggestions.items()))
+    print(
+        f"note: these flags are deprecated in favour of shared canonical flags: {pairs}. " "They still work; see `briar extract --advanced-help`.",
+        file=sys.stderr,
+    )
+    log.debug("legacy-flags: %s", pairs)
+
+
 def _install_default_journal(log: logging.Logger) -> None:
     """Install the process-wide default journal. Honours
     BRIAR_JOURNAL=off to disable entirely; otherwise wires the
@@ -141,6 +188,15 @@ def main(argv: Optional[List[str]] = None) -> int:
         print(f"error: {exc}", file=sys.stderr)
         return 1
 
+    # `--version` is pure metadata: print and exit before ANY logging,
+    # credential bootstrap, journal, or telemetry I/O — same contract as
+    # `-h`. Mirrors `briar version`, but as the conventional top-level flag.
+    if "--version" in flags or "-V" in flags:
+        from briar import __version__
+
+        print(f"briar-cli {__version__}")
+        return 0
+
     # Configure logging before anything else so module imports that
     # log at import-time still inherit the right level.
     verbose = "--verbose" in flags or "-v" in flags or env_verbose()
@@ -197,6 +253,25 @@ def main(argv: Optional[List[str]] = None) -> int:
     commands = CommandRegistry.build()
     parser = _build_parser(commands)
 
+    # Fold project config (.briar.toml / [tool.briar]) + env into the
+    # parser defaults so a bare command inherits stable values (company,
+    # store, repo, model, …) and explicit flags still override. Skipped
+    # for help/usage so `briar -h` touches no config file.
+    if not metadata_only:
+        from briar.config import apply_config_defaults, load_project_config
+
+        satisfied = apply_config_defaults(parser, load_project_config())
+        if satisfied:
+            log.debug("config: satisfied defaults for %s", sorted(set(satisfied)))
+
+        # Below config in the precedence chain: infer --owner/--repo from
+        # the local git `origin` remote for whatever config didn't supply.
+        from briar.infer import apply_inference_defaults
+
+        inferred = apply_inference_defaults(parser, satisfied)
+        if inferred:
+            log.debug("infer: filled %s from git remote", sorted(set(inferred)))
+
     normalised: List[str] = []
     for flag, value in kv.items():
         normalised.extend([flag, value])
@@ -205,6 +280,8 @@ def main(argv: Optional[List[str]] = None) -> int:
     args = parser.parse_args(normalised)
     log.debug("dispatching command=%s args=%r", args.command, vars(args))
 
+    _warn_legacy_flags(raw_argv, log)
+
     # Wrap dispatch in a telemetry span so duration + outcome land
     # in one place. The span captures uncaught exceptions, scrubs
     # them, and ships an error event — then re-raises into the
@@ -214,6 +291,7 @@ def main(argv: Optional[List[str]] = None) -> int:
     try:
         with telemetry.command_span(args.command, args):
             rc = commands[args.command].run(args)
+        _notify_update(log)
         return rc
     except CliError as exc:
         log.error("command %s failed: %s", args.command, exc)

{briar_cli-1.1.45 → briar_cli-1.1.47}/src/briar/commands/__init__.py

@@ -11,10 +11,14 @@ from typing import Dict, List, Type
 from briar.commands.agent import CommandAgent
 from briar.commands.auth import CommandAuth
 from briar.commands.base import Command, confirm
+from briar.commands.completion import CommandCompletion
+from briar.commands.config import CommandConfig
 from briar.commands.context import ContextCommand
 from briar.commands.dashboard import CommandDashboard
+from briar.commands.doctor import CommandDoctor
 from briar.commands.extract import CommandExtract
 from briar.commands.iac import CommandScaffold
+from briar.commands.init import CommandInit
 from briar.commands.journal import CommandJournal
 from briar.commands.plan import CommandPlan
 from briar.commands.runbook import CommandRunbook
@@ -40,6 +44,10 @@ class CommandRegistry:
         CommandJournal,
         CommandTelemetry,
         CommandVersion,
+        CommandCompletion,
+        CommandInit,
+        CommandConfig,
+        CommandDoctor,
     ]
 
     @classmethod

briar_cli-1.1.47/src/briar/commands/completion.py

@@ -0,0 +1,32 @@
+"""`briar completion <shell>` — print a shell-completion script.
+
+Dependency-free: the script bakes in the command/subcommand/flag names by
+introspecting the parser at generation time. See `briar.completion`."""
+
+from __future__ import annotations
+
+import argparse
+
+from briar.commands.base import Command
+from briar.completion import SUPPORTED_SHELLS, render
+
+
+class CommandCompletion(Command):
+    name = "completion"
+    help = "Print a shell-completion script (bash/zsh)."
+
+    def add_arguments(self, parser: argparse.ArgumentParser) -> None:
+        parser.add_argument(
+            "shell",
+            choices=list(SUPPORTED_SHELLS),
+            help='Shell to emit completion for. Install with: eval "$(briar completion bash)"',
+        )
+
+    def run(self, args: argparse.Namespace) -> int:
+        from briar.commands import CommandRegistry
+
+        # Introspect the full registry minus this command (completing
+        # `briar completion` itself adds nothing useful).
+        commands = {name: cmd for name, cmd in CommandRegistry.build().items() if name != self.name}
+        print(render(args.shell, commands))
+        return 0

briar_cli-1.1.47/src/briar/commands/config.py

@@ -0,0 +1,37 @@
+"""`briar config show` — inspect the resolved project configuration.
+
+Makes the precedence chain (CLI > env > .briar.toml > git inference >
+default) debuggable: every setting's effective value and where it came
+from. The table goes to stdout (honours `--format`); the config-file path
+is a status line on stderr."""
+
+from __future__ import annotations
+
+import argparse
+import sys
+
+from briar.commands.base import Subcommand, SubcommandCommand
+
+
+class ConfigShowOp(Subcommand):
+    name = "show"
+    help = "Print each setting's resolved value and its source."
+
+    def run(self, command: "SubcommandCommand", args: argparse.Namespace) -> int:
+        from briar.config import find_config_file, resolve_with_source
+        from briar.formatting import render
+
+        path = find_config_file()
+        print(f"config file: {path if path else '(none found — using env / git / defaults)'}", file=sys.stderr)
+        rows = [{"setting": r.setting, "value": r.value, "source": r.source} for r in resolve_with_source()]
+        render(rows, args.format, ["setting", "value", "source"])
+        return 0
+
+
+class CommandConfig(SubcommandCommand):
+    name = "config"
+    help = "Inspect resolved project configuration (config show)."
+
+    dest = "config_op"
+    op_noun = "config op"
+    ops = {"show": ConfigShowOp()}

briar_cli-1.1.47/src/briar/commands/doctor.py

@@ -0,0 +1,25 @@
+"""`briar doctor` — offline environment health check.
+
+Prints a status line per check (python, config, git, credentials, store)
+and exits non-zero only on a hard failure, so it is CI-usable."""
+
+from __future__ import annotations
+
+import argparse
+
+from briar.commands._enums import ExitCode
+from briar.commands.base import Command
+
+
+class CommandDoctor(Command):
+    name = "doctor"
+    help = "Check the local environment (config, git, credentials, store)."
+
+    def run(self, args: argparse.Namespace) -> int:
+        from briar.doctor import FAIL, run_checks, worst_status
+        from briar.formatting import render
+
+        checks = run_checks()
+        rows = [{"check": c.name, "status": c.status, "detail": c.detail} for c in checks]
+        render(rows, args.format, ["check", "status", "detail"])
+        return ExitCode.GENERAL_ERROR if worst_status(checks) == FAIL else ExitCode.OK