Rename the project spec and update every reference to it

The charter file carried a tool-specific name while being the repository's own
document: mission, non-negotiable constraints, the pinned stack, repo
conventions and phase status, cited as authority by thirty files across the
agent, api, deploy, docs, search and terraform trees.

PROJECT-SPEC.md says what it is. All 42 references are updated in the same
commit, including the relative link in docs/status.md, so nothing points at a
filename that no longer exists.
This commit is contained in:
2026-08-28 15:57:12 -07:00
parent 25d5d9ce2e
commit f756a9d4f6
31 changed files with 41 additions and 41 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
# terraform-provider-cairnobs
Cairn OBS's Terraform provider -- `CLAUDE.md`'s "Repo conventions" section
Cairn OBS's Terraform provider -- `PROJECT-SPEC.md`'s "Repo conventions" section
names this a first-class deliverable alongside `cairnobsctl`
("CLI and Terraform provider are first-class, not afterthoughts"), but
no phase before this one had actually built any of it. Four resources
+1 -1
View File
@@ -2,7 +2,7 @@
// built on HashiCorp's terraform-plugin-framework (not the legacy
// SDKv2 -- the framework is the actively-developed, currently-
// recommended library for a provider started from scratch, matching
// CLAUDE.md's "prefer boring, well-understood dependencies" read
// PROJECT-SPEC.md's "prefer boring, well-understood dependencies" read
// forward rather than backward).
package provider
+1 -1
View File
@@ -1,5 +1,5 @@
// Command terraform-provider-cairnobs is Cairn OBS's Terraform provider --
// CLAUDE.md names it a first-class deliverable alongside cairnobsctl
// PROJECT-SPEC.md names it a first-class deliverable alongside cairnobsctl
// ("CLI and Terraform provider are first-class, not afterthoughts"),
// but this is the first phase to actually build any of it.
//