First submitted message can hang invisibly while Honcho initialization is pending

## Summary

When the extension is enabled, the first message submitted in a new Pi session can disappear from the TUI: the user message is not rendered and no agent response begins. The session appears unresponsive.

The same behavior occurs in a regular terminal, so it does not appear to be specific to a GUI wrapper.

## Environment

- Pi CLI: `0.82.0`
- `@agney/pi-honcho-memory`: `0.1.0`
- OS: macOS

## Reproduction

1. Enable and configure `@agney/pi-honcho-memory`.
2. Start a new interactive Pi session.
3. Submit a simple first message such as `hello`.
4. Observe that the message is not displayed and no response starts.

## Isolation results

- Pi with no extensions: works normally.
- Pi with the other configured extensions but without `@agney/pi-honcho-memory`: works normally.
- Pi with only `@agney/pi-honcho-memory`: reproduces consistently.
- Disabling this extension and restarting Pi restores normal message submission.

## Suspected cause

`before_agent_start` waits for the bootstrap promise:

```ts
if (initializing) {
await initializing;
}
```

If a Honcho network operation during bootstrap stalls, the first agent turn remains blocked. Because the user message is not rendered before that hook completes, the failure looks like the submitted message disappeared.

## Expected behavior

Honcho initialization should not indefinitely block message submission. It should use a bounded timeout and fail open, or continue asynchronously so Pi remains interactive when Honcho is slow or unavailable.

Start at the before_agent_start hook in @agney/pi-honcho-memory and reproduce the first-message hang with Honcho enabled, then trace the bootstrap promise and its network operation. Verify that a stalled or unavailable Honcho initialization no longer prevents the user message or agent turn from starting, using the listed isolation cases as the completion check.

索引モデルが issue の本文から書いたものです。