docs: validate bug reports against v1.0.0-beta-1 and reorganize

- validate all 10 upstream bug reports against contextforge v1.0.0-beta-1
- rename bug report files with contextforge-xxx prefix for clarity
- add 4 new bug reports (007-010) discovered during validation
- update contextforge-002 status to partially fixed (empty string still accepted)
- update contextforge-006 test to expect 422 (fastapi standard behavior)
- add compatibility section to readme noting v1.0.0-beta-1 support
- remove redundant documentation files
- update all file references in tests and readme

Author: leefowlercu

CLAUDE.md

@@ -249,12 +249,20 @@ Some integration tests are skipped due to confirmed bugs in the upstream Context
 
 | Bug ID | Summary | Skipped Tests |
 |--------|---------|---------------|
-| CONTEXTFORGE-001 | Toggle endpoints return stale state | 1 test |
-| CONTEXTFORGE-002 | API accepts empty template field | 1 test |
+| CONTEXTFORGE-001 | Toggle endpoints return stale state | 4 tests |
+| CONTEXTFORGE-002 | API accepts empty template string | 1 test |
 | CONTEXTFORGE-003 | Toggle returns 400 instead of 404 | 1 test |
 | CONTEXTFORGE-004 | Teams endpoints reject valid auth | 12 tests |
 | CONTEXTFORGE-005 | Teams slug field ignored | 2 tests |
-| CONTEXTFORGE-006 | Teams returns 422 vs 400 | 1 test |
+| CONTEXTFORGE-007 | Gateway tags not persisted | 2 tests |
+| CONTEXTFORGE-008 | Agent bearer auth requires auth_token | 1 test |
+| CONTEXTFORGE-009 | Tag filtering returns empty results | 5 tests |
+| CONTEXTFORGE-010 | Team ID filter returns 403 | 1 test |
+
+**Resolved Issues (tests re-enabled):**
+| Bug ID | Summary | Resolution |
+|--------|---------|------------|
+| CONTEXTFORGE-006 | 422 for validation errors | By design (FastAPI standard)
 
 To re-enable a skipped test once the upstream bug is fixed:
 1. Verify the bug is fixed in the ContextForge version you're testing against

README.md

@@ -8,6 +8,7 @@ A Go SDK for the [IBM ContextForge MCP Gateway](https://github.com/IBM/mcp-conte
 ## Table of Contents
 
 - [Overview](#overview)
+  - [Compatibility](#compatibility)
 - [Installation](#installation)
 - [Quick Start](#quick-start)
 - [Usage Guide](#usage-guide)
@@ -72,6 +73,10 @@ The SDK provides full management of A2A agents including creation, configuration
 
 For more information about the A2A protocol, see the [official specification](https://a2a-protocol.org/latest/specification/) and [project website](https://a2aprotocol.ai/).
 
+### Compatibility
+
+This SDK is tested against **ContextForge v1.0.0-BETA-1** (PyPI: `mcpgateway==1.0.0b1`).
+
 ## Installation
 
 ```bash
@@ -1185,22 +1190,22 @@ This SDK follows the service-oriented architecture pattern established by [googl
 The SDK integration tests have identified six bugs in ContextForge (confirmed in both v0.8.0 and v1.0.0-BETA-1). These bugs are in the upstream API, not the SDK implementation. Affected tests are skipped and will be re-enabled once upstream bugs are fixed.
 
 **CONTEXTFORGE-001: Toggle Endpoints Return Stale State**
-The `POST /prompts/{id}/toggle` and `POST /resources/{id}/toggle` endpoints return stale `isActive` state despite correctly updating the database. See [`docs/upstream-bugs/prompt-toggle.md`](docs/upstream-bugs/prompt-toggle.md).
+The `POST /prompts/{id}/toggle` and `POST /resources/{id}/toggle` endpoints return stale `isActive` state despite correctly updating the database. See [`docs/upstream-bugs/contextforge-001-prompt-toggle.md`](docs/upstream-bugs/contextforge-001-prompt-toggle.md).
 
 **CONTEXTFORGE-002: Prompts API Accepts Empty Template Field**
-The `POST /prompts` endpoint accepts prompt creation without the `template` field, allowing semantically invalid prompts. See [`docs/upstream-bugs/prompt-validation-missing-template.md`](docs/upstream-bugs/prompt-validation-missing-template.md).
+The `POST /prompts` endpoint accepts prompt creation without the `template` field, allowing semantically invalid prompts. See [`docs/upstream-bugs/contextforge-002-prompt-validation-missing-template.md`](docs/upstream-bugs/contextforge-002-prompt-validation-missing-template.md).
 
 **CONTEXTFORGE-003: Prompts Toggle Returns 400 Instead of 404**
-The `POST /prompts/{id}/toggle` endpoint returns HTTP 400 for non-existent prompts instead of 404. See [`docs/upstream-bugs/prompt-toggle-error-code.md`](docs/upstream-bugs/prompt-toggle-error-code.md).
+The `POST /prompts/{id}/toggle` endpoint returns HTTP 400 for non-existent prompts instead of 404. See [`docs/upstream-bugs/contextforge-003-prompt-toggle-error-code.md`](docs/upstream-bugs/contextforge-003-prompt-toggle-error-code.md).
 
 **CONTEXTFORGE-004: Teams Individual Resource Endpoints Reject Valid Authentication**
-Individual team endpoints (`GET/PUT/DELETE /teams/{id}/*`) reject valid JWT tokens with 401 Unauthorized, despite list/create working correctly. See [`docs/upstream-bugs/teams-auth-individual-endpoints.md`](docs/upstream-bugs/teams-auth-individual-endpoints.md).
+Individual team endpoints (`GET/PUT/DELETE /teams/{id}/*`) reject valid JWT tokens with 401 Unauthorized, despite list/create working correctly. See [`docs/upstream-bugs/contextforge-004-teams-auth-individual-endpoints.md`](docs/upstream-bugs/contextforge-004-teams-auth-individual-endpoints.md).
 
 **CONTEXTFORGE-005: Teams API Ignores User-Provided Slug Field**
-The `POST /teams` endpoint ignores the `slug` field and always auto-generates from team name. See [`docs/upstream-bugs/teams-slug-ignored.md`](docs/upstream-bugs/teams-slug-ignored.md).
+The `POST /teams` endpoint ignores the `slug` field and always auto-generates from team name. See [`docs/upstream-bugs/contextforge-005-teams-slug-ignored.md`](docs/upstream-bugs/contextforge-005-teams-slug-ignored.md).
 
 **CONTEXTFORGE-006: Teams API Returns 422 Instead of 400 for Validation Errors**
-The `POST /teams` endpoint returns HTTP 422 (Unprocessable Entity) for validation errors instead of 400 (Bad Request). See [`docs/upstream-bugs/teams-validation-error-code.md`](docs/upstream-bugs/teams-validation-error-code.md).
+The `POST /teams` endpoint returns HTTP 422 (Unprocessable Entity) for validation errors instead of 400 (Bad Request). See [`docs/upstream-bugs/contextforge-006-teams-validation-error-code.md`](docs/upstream-bugs/contextforge-006-teams-validation-error-code.md).
 
 All bug reports include root cause analysis, proposed solutions, and workarounds.
 

contextforge/resources_test.go

@@ -312,7 +312,7 @@ func TestResourcesService_Delete(t *testing.T) {
 }
 
 func TestResourcesService_Toggle(t *testing.T) {
-	t.Skip("Skipping due to upstream ContextForge API bug - toggle returns stale isActive state. See docs/upstream-bugs/prompt-toggle.md")
+	t.Skip("Skipping due to upstream ContextForge API bug - toggle returns stale isActive state. See docs/upstream-bugs/contextforge-001-prompt-toggle.md")
 	client, mux, _, teardown := setup()
 	defer teardown()
 

contextforge/types.go

@@ -522,8 +522,8 @@ type Server struct {
 
 	// Association fields
 	AssociatedTools     []string `json:"associatedTools,omitempty"`
-	AssociatedResources []int    `json:"associatedResources,omitempty"`
-	AssociatedPrompts   []int    `json:"associatedPrompts,omitempty"`
+	AssociatedResources []string `json:"associatedResources,omitempty"`
+	AssociatedPrompts   []string `json:"associatedPrompts,omitempty"`
 	AssociatedA2aAgents []string `json:"associatedA2aAgents,omitempty"`
 
 	// Organizational fields