feat: support single-repo profiles via raid.yaml (closes #52) (#79)

* feat: support single-repo profiles using raid.yaml configuration

* fix: address Copilot review — repo-config detection in profile add

- Detect raid.yaml by basename and validate against the repo schema
  directly, so a missing `branch` surfaces as "Invalid raid.yaml" instead
  of a misleading "Invalid Profile" message.
- Drop the redundant ValidateRepoConfig call; SynthesizeFromRepoConfig
  already validates, so the previous flow validated repo configs twice
  (loading embedded schemas on each call).
- Keep a non-raid.yaml fallback path so renamed repo configs still work.

Co-Authored-By: Copilot <copilot@github.com>

* fix: address Copilot review — BuildSingleRepoProfile path + name guards

- Enforce that BuildSingleRepoProfile's path argument is named raid.yaml
  up front. ExtractRepo reads <dir>/raid.yaml unconditionally, so a
  caller passing a renamed or symlinked file would otherwise validate
  one file and load another.
- In buildProfile, refuse to load a single-repo profile whose registered
  name no longer matches the raid.yaml's current `name:` field. Active-
  profile detection compares against the registered key, so silently
  swapping in a different name breaks `profile list` and friends.
- Reword the empty-name error to "missing or empty name" since the check
  fires on `name: ""` as well as a missing key.

Co-Authored-By: Copilot <copilot@github.com>

* test: cover lines flagged by Codecov patch check

Exercises the new code paths added in the previous two Copilot-fix
commits:

- BuildSingleRepoProfile rejects a non-raid.yaml basename.
- buildProfile rejects (and accepts) registered-name vs current-name
  in single-repo mode.
- runAddProfile reports "Invalid raid.yaml" when a raid.yaml fails the
  repo schema.
- runAddProfile falls through to "Invalid Profile" when a renamed file
  fails profile validation and also fails the basename guard.

---------

Co-authored-by: meeseeks-bot <noreply@openclaw.local>
Co-authored-by: Copilot <copilot@github.com>

Author: 3 people

.gitignore

@@ -27,6 +27,10 @@ go.work.sum
 # env file
 .env
 
+# user-specific dev profile (this repo self-registers via its raid.yaml)
+/profile.raid.yml
+/profile.raid.yaml
+
 # AI assistant files
 .claude/
 

CLAUDE.md

@@ -4,7 +4,7 @@ Build: `go build -o raid .` Test: `go test ./...` Run: `go run . <cmd>`
 
 Layout: main.go→src/cmd. src/cmd/raid.go=root cmd+subcommand registration+version check. Reserved built-in subcmds: context/, doctor/, env/, install/, profile/ (user cmds w/ same name ignored w/ warning). context/ has subcmd serve (MCP stdio server). src/raid/=core domain (profile loading, env resolution, cmd execution). src/internal/=lib/ (shared types), sys/ (OS helpers, GitHub release checks), utils/. schemas/=JSON schemas (raid-repo.schema.json, raid-profile.schema.json, raid-defs.schema.json). src/resources/=embedded assets (app.properties, profile-template, repo-template) via go:embed; resources.go exposes them. site/=Docusaurus source (merged from docsite-source 2026-04-10); builds to gh-pages via .github/workflows/docs.yml on site/** changes.
 
-Config: raid.yaml=per-repo (environments+tasks: Shell|Script|HTTP|Wait|Template|Group|Git|Prompt|Confirm|Set|Print). profile.raid.yml=user profile (tracked repos, global settings).
+Config: raid.yaml=per-repo (environments+tasks: Shell|Script|HTTP|Wait|Template|Group|Git|Prompt|Confirm|Set|Print). profile.raid.yml=user profile (tracked repos, global settings). This repo dogfoods single-repo-profile mode (#52): no profile.raid.yml is committed; raid.yaml is registered directly with `raid profile add ./raid.yaml` and activated via `raid profile raid`. profile.raid.yml is in .gitignore so local dev profiles never accidentally get committed.
 
 Versioning: version in src/resources/app.properties. Bump second position (minor) for feature/large changes; bump third position (patch) for small changes or bug fixes.
 

README.md

@@ -601,7 +601,7 @@ Profiles are registered in a [Viper](https://github.com/spf13/viper)-managed con
 
 ### Can I use Raid with a monorepo?
 
-Raid is optimized for multi-repo setups, but it works for a single repo too — you can skip the top-level profile and commit a `raid.yaml` at the repo root to define commands, environments, and tasks for that project.
+Raid is optimized for multi-repo setups, but it works for a single repo too — commit a `raid.yaml` at the repo root and register it as a single-repo profile with `raid profile add ./raid.yaml`. No wrapping profile file required; the profile is named after the raid.yaml's `name` field and behaves like any other profile.
 
 ### How do I share profiles across my team?
 

llms.txt

@@ -28,7 +28,7 @@ Raid is written in Go, distributed as a single self-contained binary, and publis
 
 - [raid install](https://raidcli.dev/docs/usage/install): Clone repositories and run install tasks across your profile
 - [raid env](https://raidcli.dev/docs/usage/env): Switch between development, staging, and production environments
-- [raid profile](https://raidcli.dev/docs/usage/profile): Add profiles from a git repo URL, raw file URL, or local path; list, switch, and remove profiles
+- [raid profile](https://raidcli.dev/docs/usage/profile): Add profiles from a git repo URL, raw file URL, or local path (including single-repo `raid.yaml` configs); list, switch, and remove profiles
 - [Custom commands](https://raidcli.dev/docs/usage/custom): Define and invoke `raid <cmd>` team workflows
 - [raid doctor](https://raidcli.dev/docs/usage/doctor): Diagnose profile and repo configuration issues
 - [raid root command](https://raidcli.dev/docs/usage/raid): Global flags and top-level invocation

profile.raid.yml

@@ -256,7 +256,18 @@ environments:
 
 ```bash
 raid profile add ./my-profile.yaml   # register a profile file
+raid profile add ./raid.yaml          # register a repo config as a single-repo profile
 raid profile list                     # list all registered profiles
 raid my-team                          # switch to the 'my-team' profile
 raid profile remove my-team          # remove a profile
 ```
+
+## Single-repo profiles
+
+For projects that ship only a `raid.yaml` (no wrapping profile file), point `raid profile add` straight at the repo config:
+
+```bash
+raid profile add ./raid.yaml
+```
+
+Raid detects the repo schema and registers it as a single-repo profile named after the raid.yaml's `name` field. Switch to it with `raid profile <name>` like any other profile. The commands, environments, and install tasks declared in the raid.yaml become available at the top level.

site/docs/features/profiles.mdx

@@ -36,6 +36,13 @@ Add a profile from a local file:
 raid profile add ./my-profile.yaml
 ```
 
+Add a repo config (`raid.yaml`) as a single-repo profile — useful for projects that ship only a `raid.yaml` without a wrapping profile file. The profile is named after the raid.yaml's `name` field:
+
+```bash
+raid profile add ./raid.yaml
+raid profile <name>   # activate using the raid.yaml's name
+```
+
 Add a profile from a git repository — raid shallow-clones it and imports `*.raid.yaml`, `*.raid.yml`, and `profile.json` files found at the root. If none of those match, raid falls back to any plain `.yaml` / `.yml` / `.json` at the root, so a single-file gist (or scratch repo) with `profile.yaml` or `myprofile.yml` works without renaming:
 
 ```bash

site/docs/usage/profile.mdx

@@ -9,6 +9,10 @@ description: Feature-by-feature release notes for Raid.
 
 User-visible changes per release, latest first. For full commit history see the [GitHub releases page](https://github.com/8bitalex/raid/releases).
 
+## 0.12.0 — upcoming
+
+**Repo-as-a-profile for single-repo projects.** `raid profile add ./raid.yaml` now accepts a repo config directly — no wrapping profile file required. Raid detects the repo schema, registers the file as a single-repo profile named after the raid.yaml's `name` field, and `raid profile <name>` activates it like any other profile. Commands, environments, and install tasks defined in the raid.yaml become available at the top level. Existing multi-repo profiles continue to work unchanged. Closes [#52](https://github.com/8bitAlex/raid/issues/52).
+
 ## 0.11.1 — upcoming
 
 **Schemas published at a stable URL.** The profile, repo, and shared-defs JSON Schemas are now served at `https://raidcli.dev/schema/v1/raid-profile.schema.json`, `…/raid-repo.schema.json`, and `…/raid-defs.schema.json`. Generated profile and repo templates point at these URLs out of the box, so YAML LSPs and agents get autocomplete and inline validation against the canonical contract. The `/v1/` path is a stability promise — additive changes only; breaking changes will publish to `/v2/`. The docsite build copies `schemas/` into `static/schema/v1/`, so the canonical source remains the single Go-embedded copy. Closes [#48](https://github.com/8bitAlex/raid/issues/48).

site/docs/whats-new.mdx

@@ -2,6 +2,7 @@ package profile
 
 import (
 	"fmt"
+	"path/filepath"
 	"strings"
 
 	"github.com/8bitalex/raid/src/internal/sys"
@@ -12,20 +13,24 @@ import (
 
 // Injectable profile-package functions for testing error paths.
 var (
-	proValidate  = pro.Validate
-	proUnmarshal = pro.Unmarshal
-	proContains  = pro.Contains
-	proAddAll    = pro.AddAll
-	proGet       = pro.Get
-	proSet       = pro.Set
+	proValidate       = pro.Validate
+	proSynthesizeRepo = pro.SynthesizeFromRepoConfig
+	proUnmarshal      = pro.Unmarshal
+	proContains       = pro.Contains
+	proAddAll         = pro.AddAll
+	proGet            = pro.Get
+	proSet            = pro.Set
 )
 
 var AddProfileCmd = &cobra.Command{
 	Use:   "add <path|url>",
 	Short: "Add profile(s) from a local file or URL",
 	Long: `Add one or more profiles from a local file, a git repository URL, or a raw file URL.
 
-Local path: the file is validated and registered directly.
+Local path: the file is validated and registered directly. A repo config
+(raid.yaml) is also accepted and registered as a single-repo profile named
+after the raid.yaml's ` + "`name`" + ` field — handy for projects that ship
+only a raid.yaml without a wrapping profile.
 
 Git URL (git@ prefix, .git suffix, or any HTTP URL that responds to git ls-remote):
   raid shallow-clones the repo and imports *.raid.yaml, *.raid.yml, and profile.json
@@ -58,15 +63,35 @@ func runAddProfile(path string) int {
 		return 1
 	}
 
-	if err := proValidate(path); err != nil {
-		fmt.Printf("Invalid Profile: %v\n", err)
-		return 1
-	}
-
-	profiles, err := proUnmarshal(path)
-	if err != nil {
-		fmt.Printf("Failed to extract profiles: %v\n", err)
-		return 1
+	var profiles []pro.Profile
+	if filepath.Base(path) == raid.RaidConfigFileName {
+		// Files named raid.yaml are repo configs by convention. Validate
+		// against the repo schema directly so a missing `branch` etc.
+		// surfaces as a repo-schema error rather than a misleading
+		// "Invalid Profile" message.
+		single, serr := proSynthesizeRepo(path)
+		if serr != nil {
+			fmt.Printf("Invalid raid.yaml: %v\n", serr)
+			return 1
+		}
+		profiles = []pro.Profile{single}
+	} else if err := proValidate(path); err != nil {
+		// Non-raid.yaml file failed profile-schema validation. Try the
+		// repo schema as a fallback so callers can still register a
+		// renamed repo config; otherwise report the profile error.
+		if single, serr := proSynthesizeRepo(path); serr == nil {
+			profiles = []pro.Profile{single}
+		} else {
+			fmt.Printf("Invalid Profile: %v\n", err)
+			return 1
+		}
+	} else {
+		extracted, err := proUnmarshal(path)
+		if err != nil {
+			fmt.Printf("Failed to extract profiles: %v\n", err)
+			return 1
+		}
+		profiles = extracted
 	}
 
 	var newProfiles []pro.Profile

src/cmd/profile/add.go

@@ -697,6 +697,50 @@ func TestRunAddProfile_allDuplicates(t *testing.T) {
 	})
 }
 
+// TestRunAddProfile_repoConfigAsProfile checks that a raid.yaml (repo schema)
+// can be registered as a single-repo profile. The profile name is the
+// raid.yaml's `name` field.
+func TestRunAddProfile_repoConfigAsProfile(t *testing.T) {
+	setupConfig(t)
+	dir := t.TempDir()
+	repoYaml := filepath.Join(dir, "raid.yaml")
+	if err := os.WriteFile(repoYaml, []byte("name: soloproj\nbranch: main\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	out := captureStdout(t, func() {
+		if code := runAddProfile(repoYaml); code != 0 {
+			t.Errorf("runAddProfile repo-config: code = %d, want 0", code)
+		}
+	})
+	if !strings.Contains(out, "soloproj") {
+		t.Errorf("runAddProfile repo-config: got %q, want 'soloproj'", out)
+	}
+	if !lib.ContainsProfile("soloproj") {
+		t.Error("runAddProfile repo-config: profile not registered")
+	}
+	got := lib.GetProfile()
+	if got.Name != "soloproj" || got.Path != repoYaml {
+		t.Errorf("active profile = %+v, want name=soloproj path=%s", got, repoYaml)
+	}
+}
+
+// TestRunAddProfile_repoConfigMissingName: a raid.yaml that passes the repo
+// schema check but has no name field should report an error.
+func TestRunAddProfile_repoConfigMissingName(t *testing.T) {
+	setupConfig(t)
+	dir := t.TempDir()
+	repoYaml := filepath.Join(dir, "raid.yaml")
+	// Schema-valid (name is a string, just empty) and branch required.
+	if err := os.WriteFile(repoYaml, []byte("name: \"\"\nbranch: main\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	_ = captureStdout(t, func() {
+		if code := runAddProfile(repoYaml); code != 1 {
+			t.Errorf("runAddProfile empty-name: code = %d, want 1", code)
+		}
+	})
+}
+
 func TestRunAddProfile_multiDocSuccess(t *testing.T) {
 	setupConfig(t)
 	dir := t.TempDir()
@@ -1128,3 +1172,47 @@ func TestRunCreateWizardCore_withReposAndConfigCreate(t *testing.T) {
 		t.Error("proCreateRepoConfigs should have been called")
 	}
 }
+
+// TestRunAddProfile_repoConfigInvalidSchema covers the new "raid.yaml fails
+// repo-schema validation" path: when basename is raid.yaml we report it as
+// an invalid raid.yaml, not as an invalid profile.
+func TestRunAddProfile_repoConfigInvalidSchema(t *testing.T) {
+	setupConfig(t)
+	dir := t.TempDir()
+	repoYaml := filepath.Join(dir, "raid.yaml")
+	// Missing required `branch` — repo schema should reject this.
+	if err := os.WriteFile(repoYaml, []byte("name: noBranch\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	out := captureStdout(t, func() {
+		if code := runAddProfile(repoYaml); code != 1 {
+			t.Errorf("runAddProfile invalid raid.yaml: code = %d, want 1", code)
+		}
+	})
+	if !strings.Contains(out, "Invalid raid.yaml") {
+		t.Errorf("expected 'Invalid raid.yaml' in output, got %q", out)
+	}
+}
+
+// TestRunAddProfile_nonRaidYamlFallbackFailsBasenameGuard covers the
+// non-raid.yaml branch where profile validation fails and the fallback
+// synthesis fails BuildSingleRepoProfile's basename guard — the original
+// profile-validation error is the one reported to the user.
+func TestRunAddProfile_nonRaidYamlFallbackFailsBasenameGuard(t *testing.T) {
+	setupConfig(t)
+	dir := t.TempDir()
+	path := filepath.Join(dir, "renamed.raid.yaml")
+	// Contents look like a repo config (has `branch`), so profile schema
+	// rejects them. Basename guard then rejects the repo-schema fallback.
+	if err := os.WriteFile(path, []byte("name: renamed\nbranch: main\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	out := captureStdout(t, func() {
+		if code := runAddProfile(path); code != 1 {
+			t.Errorf("runAddProfile non-raid.yaml repo content: code = %d, want 1", code)
+		}
+	})
+	if !strings.Contains(out, "Invalid Profile") {
+		t.Errorf("expected 'Invalid Profile' in output, got %q", out)
+	}
+}