AI Fix Prompts for Pi Aaf Extensions

Fix a hardcoded credential in repository 'rayshawnmccall21__pi-aaf-extensions'.

**Issue**: Hard-coded api_key found (Vault Token)
**File**: aaf-implementation/agents/developer.ts
**Line**: 779
**Severity**: CRITICAL

**Current code around the issue:**
```
     774 |   learningSignals: DeveloperLearningSignals,
     775 |   mode: DeveloperMode,
     776 | ): Promise<GeneratedImplementationPatternSkill | undefined> {
     777 |   const projectRoot = path.resolve(input.projectRoot ?? ".");
     778 |   const focusAreas = unique([
>>>  779 |     ...learningSignals.implementationPatternCandidates,
     780 |     learningSignals.testStrategy,
     781 |     ...focus.acceptanceCriteria,
     782 |     ...focus.suggestedCodeAreas,
     783 |     ...focus.suggestedTestAreas,
     784 |   ]).slice(0, 8);
```

**Required fix:**
1. Remove the hardcoded credential from the source code
2. Replace it with an environment variable read: `os.environ.get('API_KEY_KEY')` (Python) or `process.env.API_KEY_KEY` (JS)
3. Add the variable name to a `.env.example` file with a placeholder value
4. Ensure `.env` is in `.gitignore`
5. If this credential was ever committed to git, it should be considered compromised and rotated

**Do NOT:**
- Move the secret to a config file that gets committed
- Use a default fallback value that is a real credential
- Leave the old credential in a comment

Address OWASP A02 (Cryptographic Failures) compliance gap in 'rayshawnmccall21__pi-aaf-extensions'.

**OWASP Category**: A02 -- Cryptographic Failures
**Fix guidance**: Remove hardcoded secrets, use strong encryption (AES-256-GCM), enforce TLS, never store passwords in plaintext (use bcrypt/argon2).

**Steps:**
1. Identify all code paths related to cryptographic failures
2. Apply the fixes described above
3. Add automated tests to verify the fix
4. Document any security assumptions in code comments

Address OWASP A07 (Auth Failures) compliance gap in 'rayshawnmccall21__pi-aaf-extensions'.

**OWASP Category**: A07 -- Auth Failures
**Fix guidance**: Implement proper session management, use MFA where possible, enforce strong passwords, protect against brute force.

**Steps:**
1. Identify all code paths related to auth failures
2. Apply the fixes described above
3. Add automated tests to verify the fix
4. Document any security assumptions in code comments

Repository 'rayshawnmccall21__pi-aaf-extensions' is failing the quality gate.

Failed conditions:
- overall_score: actual 0.0 >= 50 (FAILED)
- security_score: actual 0.0 >= 40 (FAILED)
- critical_credentials: actual 1.0 <= 0 (FAILED)
- duplication_pct: actual 21.9 <= 20 (FAILED)

Fix each failing condition to make the repo pass the quality gate.

Repository 'rayshawnmccall21__pi-aaf-extensions' has 1 open issues:

- [CRITICAL] Hard-coded api_key: Vault Token (aaf-implementation/agents/developer.ts)

Resolve each issue. For security issues, apply the appropriate fix. For quality issues, refactor the affected code.