@ankhorage/devtools 1.10.7 → 1.10.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -14,7 +14,7 @@ Apply a repository profile instead of forcing one folder tree onto every package
|
|
|
14
14
|
Before deciding structure:
|
|
15
15
|
|
|
16
16
|
1. Read the repository `AGENTS.md`, `package.json`, exports, source tree, and representative tests.
|
|
17
|
-
2. Load `ankhorage-coding-rules` and
|
|
17
|
+
2. Load `ankhorage-coding-rules` as the complementary implementation and testing authority.
|
|
18
18
|
3. Identify the repository's owning capability and its profile below.
|
|
19
19
|
4. Identify current public subpaths and cross-package release boundaries.
|
|
20
20
|
|
|
@@ -9,8 +9,8 @@ one domain only -> src/<domain>/utils/<functionName>.ts
|
|
|
9
9
|
semantic/domain behavior -> owning domain, not utils
|
|
10
10
|
```
|
|
11
11
|
|
|
12
|
-
Do not retain local copies while waiting for a Utility release. Follow the Utility
|
|
13
|
-
release, dependency-update
|
|
12
|
+
Do not retain local copies while waiting for a Utility release. Follow the Utility repository's
|
|
13
|
+
current PR, merge, release, and dependency-update workflow.
|
|
14
14
|
|
|
15
15
|
## Strong cross-repository candidates
|
|
16
16
|
|
package/package.json
CHANGED