aw-spec-cli 0.1.16 → 0.1.17

package/assets/.appweaver/scripts/bash/aw-xref.sh

@@ -7,10 +7,9 @@
 #
 #   aw-xref.sh record         --using X --design <design.md> [--origin ...] [--date YYYY-MM-DD] [--root DIR]
 #   aw-xref.sh list           --aggregate Y [--root DIR] [--bundle knowledge]
-#   aw-xref.sh concept-upsert   --aggregate X [--source-files a,b,c] [--lane backend|frontend] [--merge] [--description D] [--origin ...] [--root DIR]
+#   aw-xref.sh concept-upsert   --aggregate X [--source-files a,b,c] [--description D] [--origin ...] [--root DIR]
 #   aw-xref.sh concept-overview --aggregate X (--text PROSE | --text-file F) [--root DIR]
 #   aw-xref.sh concept-paths    --aggregate X | --feature-dir <dir> [--root DIR] [--bundle knowledge]
-#   aw-xref.sh concept-coverage --aggregate X | --feature-dir <dir> [--ids "FR-001,BR-002"] [--max-list N] [--root DIR] [--bundle knowledge]
 set -euo pipefail
 DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 exec python3 "$DIR/../python/aw-xref.py" "$@"

package/assets/.appweaver/scripts/bash/common.sh

@@ -50,6 +50,53 @@ get_repo_root() {
 # reads. Callers that need to act on a specific feature take an explicit `--feature-dir`
 # argument, which wins over feature.json at the call site.
 
+# CONTEXT RESOLUTION IS THE SAME SINGLE CHANNEL, one level up:
+# `.appweaver/context.json`, written by select-bounded-context. A bounded context is
+# the container a feature lives in — specs/<Context>/<Feature>/ — and it owns the one
+# domain-model.md every spec inside it references.
+#
+# ABSENCE IS A VALID STATE, not a failure. A repo that predates bounded contexts has
+# features directly under specs/, and every caller keeps that flat layout when no
+# context is active. That is what lets the context be adopted per repo instead of
+# forcing a migration on every tree at once.
+read_context_json_context_directory() {
+    local repo_root="$1"
+    local cj="$repo_root/.appweaver/context.json"
+    [[ -f "$cj" ]] || { printf '%s' ''; return 0; }
+
+    local _cd=''
+    if command -v jq >/dev/null 2>&1; then
+        if ! _cd=$(jq -r '.context_directory // empty' "$cj" 2>/dev/null); then
+            _cd=''
+        fi
+    elif command -v python3 >/dev/null 2>&1; then
+        if ! _cd=$(python3 -c "import json,sys; d=json.load(open(sys.argv[1])); v=d.get('context_directory'); print(v if v else '')" "$cj" 2>/dev/null); then
+            _cd=''
+        fi
+    else
+        _cd=$( { grep -E '"context_directory"[[:space:]]*:' "$cj" 2>/dev/null || true; } \
+            | head -n 1 \
+            | sed -E 's/^[^:]*:[[:space:]]*"([^"]*)".*$/\1/' )
+    fi
+
+    printf '%s' "$_cd"
+    return 0
+}
+
+# The specs/ subtree the active context owns, as a repo-relative path: the context
+# directory when one is active, plain "specs" when none is. Every caller that
+# enumerates or creates a feature goes through this, so the flat and nested layouts
+# differ in exactly one place.
+feature_base_rel() {
+    local repo_root="$1"
+    local cd_rel; cd_rel=$(read_context_json_context_directory "$repo_root")
+    if [[ -n "$cd_rel" ]] && [[ -d "$repo_root/$cd_rel" ]]; then
+        printf '%s' "$cd_rel"
+    else
+        printf '%s' 'specs'
+    fi
+}
+
 # Safely read .appweaver/feature.json's "feature_directory" value.
 # Prints the raw value (possibly relative) to stdout, or empty string if the file
 # is missing, unparseable, or does not contain the key. Always returns 0 so callers