Fix organization setup records and console regressions
This commit is contained in:
1 parent
ac63a187e8
commit
61e4e76520
21 files changed
+308
-39
No files matched your search
+5
-1
@@ -1320,7 +1320,11 @@ refuses `project-no-commit` if the layout has no readable HEAD commit. It
|
||||
exits 0 when valid, 2 for project/record problems (including an undeclared
|
||||
project), 3 for configuration loading problems and 4 for usage. The optional business project `repo` is a normalized absolute
|
||||
record-repository path; the default is
|
||||
`<dataRoot>/projects/<business>/<project>/`. `root` remains the code checkout.
|
||||
`<dataRoot>/projects/<business>/<project>/`. For a registered organization,
|
||||
`<dataRoot>` is that organization's data root for both the CLI and its bus.
|
||||
If an instance-root records repository already exists, initialization and reads
|
||||
refuse and name both locations for inspection; they never move or copy it.
|
||||
`root` remains the code checkout.
|
||||
The package README describes schemas and the shared agent record writer; agent
|
||||
writes never enter `spec/`, never absorb pending edits and refuse remotes.
|
||||
|
||||
|
||||
Reference in new issue
Block a user