spec

type AuthorReq struct {
	Dir       string                                    // context dir ("" = root)
	Stem      string                                    // ID stem, e.g. "CUDA-KRN"; default: stem of last rule in target file
	ForceID   string                                    // exact ID to use (replay); skips minting, still lints
	Mint      func(stem string, floor int) (int, error) // collision-free minter (swarm coord); nil = local scan
	Sentence  string                                    // composed EARS sentence
	Rationale string
	Applies   []string
}

type AuthorRes struct {
	ID   string
	Path string // repo-relative spec file path

	// Root is the absolute dir Path is relative to: the workspace root
	// AddRule/EditRule were called with, not necessarily the main checkout.
	// GitHub issue 27: a caller inside a linked git worktree got back a
	// bare "ok ID .spectackle/spec.md" that read as if it landed in the
	// worktree, when the write had actually landed in the enclosing main
	// checkout — the relative Path alone can't tell the two apart. Root
	// pins down the other half of that join so a caller (or a future
	// mcpserver reporting change) can print filepath.Join(Root, Path) and
	// never wonder which directory it is relative to.
	Root string

	Findings []ears.Finding
	Written  bool
}

type Cascade struct {
	// contains filtered or unexported fields
}

type ResolvedRule struct {
	ears.Rule
	ScopeDir string // "." for root, else the context dir
}

type SpecFile struct {
	Path      string // repo-relative path of the spec.md
	Dir       string // context dir it scopes ("" = root)
	Prefix    string
	Scope     []string
	Inherits  bool
	Overrides []string
	Rules     []ears.Rule
	Sections  []ears.Section
}