fix: resolve SRS conflicts from batch verification analysis (CONFLICT-1~4)

Conflict Resolutions:
- CONFLICT-1 (High): Fix REQ-006 ownership scope — implement owner_user_id filtering
  * Change app/api/v1_assets.py: owner_user_id=None → owner_user_id=auth.user_id
  * Update docs/runtime-flows.md to reflect service-token owner-scoped portfolio filtering
  * Add regression test in tests/test_v1.py for ownership boundary

- CONFLICT-2 (Medium): Transition REQ-001/002/003 to Implemented
  * REQ-001: local-db-validation-scenarios (via confirm-req-implemented bat-007)
  * REQ-002: alembic-runtime-schema-ownership (via confirm-req-implemented bat-007)
  * REQ-003: local-db-operations-runbook-and-baseline-updates (via confirm-req-implemented bat-007)
  * Update docs/srs/index.md with status transitions

- CONFLICT-3 (Low): Document REQ-012 rotate lifecycle
  * Add rotate lifecycle notes to REQ-012 (change-req req-012)
  * Clarify runtime_id change behavior and trex-basic reconnection requirements

- CONFLICT-4 (Low): Clarify REQ-005 AC-2 endpoint path
  * Change REQ-005 AC-2: 'POST /auth/tokens or equivalent' → 'POST /auth/service-tokens'
  * Update docs/srs/index.md change log with change-req entries

Documentation Updates:
- Update BAT-001 verification status with conflict resolution evidence
- Update release rel-001 with verified status confirmation
- Add change log entries for all conflict resolutions with dates and references

Testing:
- Add ownership boundary test to test_v1.py
- Verify filter works with auth.user_id context

docs/srs/Migration/req-002_alembic-runtime-schema-ownership.md

@@ -1,6 +1,6 @@
 # req-002: Alembic와 runtime schema ownership 경계 정리
 
-- Status: Approved
+- Status: Implemented
 - Type: Migration
 - Priority: High
 - Owner: repository-maintainers
@@ -29,6 +29,35 @@
 
 ## Change Log
 
+### CHG-20260511-01
+- Date: 2026-05-11
+- Author: repository-maintainers
+
+#### Change Summary
+- Implemented 전환 — BAT-007 verification passed, confirm-req-implemented 게이트 통과
+
+#### Intent
+- BAT-007 verification.md AC-1~3 모두 PASS. Blocking Issues 없음. docs/project-structure.md "Schema Ownership Boundary", docs/runtime-flows.md "Alembic vs ensure_schema() Schema Ownership Boundary" evidence 연결 확인 완료. 잔여 리스크(idx_auth_tokens_service_name_unique Alembic 미등록)는 후속 batch 검토 항목으로 남겨둠.
+
+#### Acceptance Criteria Delta
+- none
+
+#### Impacted Area Delta
+- none
+
+#### Delivery Trace Delta
+- Batches: BAT-007 (release-candidate)
+- Releases: none
+
+#### Revalidation Impact
+- Reverification Needed: no
+- Existing Implementation Invalidated: no
+- Status Recommendation: implemented
+- Follow-up Action: draft-release (BAT-007); idx_auth_tokens_service_name_unique Alembic revision 추가 검토 권장
+
+#### Validation Plan
+- BAT-007 verification.md AC-1~3 evidence 연결 확인 완료
+
 ### CHG-20260430-02
 - Date: 2026-04-30
 - Author: GitHub Copilot