Adapt new context api in monobean Related: #1164

[pleasedontbreak123]

Related: #1164

1. adapt new context api
2. revise the new method in appcontext to adapt Tokio multithreaded runtime

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mega	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 1, 2025 9:22am

[Copilot]

Pull Request Overview

This PR adapts the code to the new context API and revises methods to support the Tokio multithreaded runtime for monobean. Key changes include:

• Switching from the old jupiter context to the new context::AppContext in multiple modules.
• Revising VaultCore initialization and key handling to support the new API.
• Updating Cargo.toml files to include new dependencies and align versioning with the new context.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
vault/src/integration/vault_core.rs	Consolidated imports and added debug prints for key paths.
monobean/src/core/servers.rs	Updated context usage, now passing storage where needed.
monobean/src/core/mega_core.rs	Refactored vault API calls and updated context propagation.
monobean/Cargo.toml	Added dependency for the new context module.
context/src/lib.rs	Adapted AppContext initialization with spawn_blocking.
context/Cargo.toml	Added Tokio dependency.

[Copilot]

Consider using a logging framework (e.g., tracing::debug) instead of println to ensure consistent logging across the application.

Suggested change

	println!("{:?}", key_path);
	tracing::debug!("Vault key path: {:?}", key_path);