fix: resolve repo root from working directory, not script location

Scripts are now in the package, not the project. Fallback repo root
detection was walking up from the script's location (inside pi-spec-kit)
instead of from the current working directory (the user's project).
This caused specs/ to be created in the wrong repo.

Author: michellejw

scripts/create-new-feature.sh

@@ -164,13 +164,12 @@ clean_branch_name() {
 # Resolve repository root. Prefer git information when available, but fall back
 # to searching for repository markers so the workflow still functions in repositories that
 # were initialised with --no-git.
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
 if git rev-parse --show-toplevel >/dev/null 2>&1; then
     REPO_ROOT=$(git rev-parse --show-toplevel)
     HAS_GIT=true
 else
-    REPO_ROOT="$(find_repo_root "$SCRIPT_DIR")"
+    # Walk up from current working directory, not script location
+    REPO_ROOT="$(find_repo_root "$PWD")"
     if [ -z "$REPO_ROOT" ]; then
         echo "Error: Could not determine repository root. Please run this script from within the repository." >&2
         exit 1

scripts/setup-plan.sh

@@ -26,9 +26,9 @@ get_repo_root() {
     if git rev-parse --show-toplevel >/dev/null 2>&1; then
         git rev-parse --show-toplevel
     else
-        # Walk up from script directory looking for project markers
+        # Walk up from current working directory looking for project markers
         local dir
-        dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+        dir="$PWD"
         while [ "$dir" != "/" ]; do
             if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
                 echo "$dir"