fix(suggest-path): remove GROWI.cloud and GC references from spec docs

Address PR review feedback to remove commercial service references
(GROWI.cloud paid-plan gating, GC billing) from OSS spec documents,
replacing with neutral "independent access control" phrasing.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.kiro/specs/suggest-path/design.md

@@ -13,7 +13,7 @@
 - Provide a single POST endpoint that returns path suggestions with metadata (type, path, label, description, grant)
 - Phase 1 (MVP): Return personal memo path with fixed metadata — zero external dependencies
 - Phase 2: Add search-based and category-based suggestions using GROWI AI keyword extraction and search service
-- Enable GROWI.cloud paid-plan gating via separate namespace from `/page`
+- Enable independent access control via separate namespace from `/page`
 
 ### Non-Goals
 

.kiro/specs/suggest-path/requirements.md

@@ -29,7 +29,7 @@ The following are explicitly **not** part of this feature:
 1. When the client sends a POST request with a `body` field containing page content, the Suggest Path Service shall return a response containing an array of path suggestions.
 2. The Suggest Path Service shall include `type`, `path`, `label`, `description`, and `grant` fields in each suggestion.
 3. The Suggest Path Service shall return `path` values as directory paths with a trailing slash (`/`).
-4. The Suggest Path Service shall expose the endpoint under a namespace separate from `/_api/v3/page/` to support independent access control (e.g., GROWI.cloud paid-plan gating).
+4. The Suggest Path Service shall expose the endpoint under a namespace separate from `/_api/v3/page/` to support independent access control.
 
 ### Requirement 2: Memo Path Suggestion (Phase 1 MVP)
 

.kiro/specs/suggest-path/research.md

@@ -73,21 +73,21 @@
 
 | Option | Description | Strengths | Risks / Limitations | Notes |
 |--------|-------------|-----------|---------------------|-------|
-| Route under `routes/apiv3/ai-tools/` | New namespace in standard routes | Clean separation, follows `ai-tools` naming decision from review | New directory, needs registration in index.js | Aligns with GROWI.cloud access control needs |
-| Route under `features/openai/` | Extend existing AI feature module | Reuses AI infrastructure, minimal setup | Provider-specific name, harder to separate for GC billing | Rejected in review — namespace should be provider-agnostic |
-| Route under `routes/apiv3/page/` | Add to existing page routes | Close to page creation | Cannot gate independently for GC paid plans | Rejected in review — yuki requested separation |
+| Route under `routes/apiv3/ai-tools/` | New namespace in standard routes | Clean separation, follows `ai-tools` naming decision from review | New directory, needs registration in index.js | Aligns with independent access control needs |
+| Route under `features/openai/` | Extend existing AI feature module | Reuses AI infrastructure, minimal setup | Provider-specific name, harder to separate for independent access control | Rejected in review — namespace should be provider-agnostic |
+| Route under `routes/apiv3/page/` | Add to existing page routes | Close to page creation | Cannot gate independently for access control | Rejected in review — yuki requested separation |
 
 ## Design Decisions
 
 ### Decision: Route Namespace Placement
 
-- **Context**: Endpoint needs independent access control for GROWI.cloud paid plans
+- **Context**: Endpoint needs independent access control
 - **Alternatives Considered**:
   1. `/openai/suggest-path` — groups with AI features but provider-specific
   2. `/page/suggest-path` — close to page creation but cannot gate independently
   3. `/ai-tools/suggest-path` — new provider-agnostic namespace
 - **Selected Approach**: `/_api/v3/ai-tools/suggest-path` under `routes/apiv3/ai-tools/`
-- **Rationale**: Matches existing unmerged PR naming, provider-agnostic, enables independent GC access control
+- **Rationale**: Matches existing unmerged PR naming, provider-agnostic, enables independent access control
 - **Trade-offs**: Requires new directory and route registration. Namespace is tentative (pending yuki confirmation)
 - **Follow-up**: Confirm `ai-tools` namespace with yuki