다운스트림 SDK 업그레이드를 위한 Windows 에이전트 메모리 준비 상태 감사

I can't perform this audit. I don't have access to your repository, the pinned `@byok-sdk/client` tag, your daemon config, or your issue tracker, and I have no tools enabled in this session to read files, search GitHub, or fetch the SDK source. Anything I produced would be fabricated file:line citations, invented gate logic, and made-up issue numbers — exactly the kind of output that would waste your time and pollute the tracker.

Here's what I can do instead: give you a precise, executable plan so you (or an agent with repo access) can complete this in one pass.

## 1. Pin down the SDK version and environment

```bash
# In your repo
cat package.json | grep -A2 byok-sdk
npm ls @byok-sdk/client
git rev-parse HEAD
node --version && npm --version
# Windows specifics
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
```

Record: SDK version + git tag/commit, your repo commit, Node version, OS build, arch (`win32-x64`).

## 2. Locate every platform gate

Search the SDK source (in `node_modules/@byok-sdk/client` or a vendored checkout at the pinned tag):

```bash
# Platform checks
rg -n "win32|platform\(\)|process\.platform|isWindows|darwin|linux" node_modules/@byok-sdk/client
# Secure filesystem availability
rg -n "secure.?fs|secureFilesystem|keytar|dpapi|credential|safeStorage" node_modules/@byok-sdk/client
# Helper release admission
rg -n "helper|release|admission|admit|allowlist|manifest" node_modules/@byok-sdk/client
# DaemonConfig.agentMemory construction
rg -n "agentMemory|DaemonConfig" node_modules/@byok-sdk/client
```

For each hit, capture `file:line` and the exact condition. You're looking for three gate families:
- **Secure filesystem availability** — what makes it unavailable on win32-x64 (missing native module, unsupported API, feature flag).
- **Helper release admission** — how a helper binary/version is admitted or rejected per platform.
- **`DaemonConfig.agentMemory` construction** — where the config object is built and whether it's gated.

## 3. Map features to availability on win32-x64

For each of `memory_recall`, `memory_save`, `agent.memory.projection`, `agent.memory.intent`, trace the call path to the gates above and record: available / unavailable / degraded, with the gating `file:line`. A small table works:

| Feature | Gate(s) hit | win32-x64 status | Citation |
|---|---|---|---|
| memory_recall | … | … | … |
| memory_save | … | … | … |
| agent.memory.projection | … | … | … |
| agent.memory.intent | … | … | … |

## 4. Check your daemon config

```bash
rg -n "agentMemory" --glob '!node_modules'
```

Determine whether `agentMemory` is set unconditionally (no platform guard) — if so, that's the downstream bug: config claims memory is enabled while the SDK silently gates it off on win32-x64.

## 5. Search existing issues before filing

```bash
gh issue list --repo <sdk-org>/<sdk-repo> --state all --search "windows agent memory"
gh issue list --repo <sdk-org>/<sdk-repo> --state all --search "win32 secure filesystem"
gh issue list --repo <sdk-org>/<sdk-repo> --state all --search "helper release admission"
gh issue list --repo <sdk-org>/<sdk-repo> --state all --search "DaemonConfig agentMemory"
gh search issues --repo <sdk-org>/<sdk-repo> "win32-x64 memory" --state all
```

Also check your own repo's tracker for downstream duplicates.

## 6. Issue draft skeleton (fill from steps 1–5)

```
Title: [win32-x64] agent memory features gated off; DaemonConfig.agentMemory set unconditionally downstream

## Versions & environment
- @byok-sdk/client: <version> (tag <tag>, commit <sha>)
- Downstream repo: <repo> @ <sha>
- Node: <ver>, OS: Windows <build>, arch: win32-x64

## Gates found (source citations)
- Secure filesystem availability: <file:line> — <condition>
- Helper release admission: <file:line> — <condition>
- DaemonConfig.agentMemory construction: <file:line> — <condition>

## Feature availability on win32-x64
| Feature | Status | Citation |
|---|---|---|
| memory_recall | … | … |
| memory_save | … | … |
| agent.memory.projection | … | … |
| agent.memory.intent | … | … |

## Minimal reproduction
1. <steps>
2. <expected vs actual>

## Acceptance criteria (mapped to SDK PRD items)
- [ ] PRD-<id>: <criterion> — verified by <test>
- [ ] …

## Downstream impact
<what breaks in your daemon; unconditional agentMemory config>

## Related issues
- #<n> (closed) — <relevance>
- #<n> (closed) — <relevance>
```

If you paste the relevant SDK source snippets (the gate functions and `DaemonConfig` construction) and your daemon config, I can help you interpret the gates, build the feature-availability table, and tighten the issue text — but the citations have to come from real files you share, not from me guessing.