onepub-dev / onepub-dev/reVault
test core api without the session agent.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
We need to ensure that users of the core api can do so without accidentally starting an session agent.
Where is the boundary here. I think the session agent is really about the cli tooling and the core api should only about creating/maintaining vaults.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the core API entry points and the session-agent startup path, then compare them with the CLI tooling boundary described in the issue. Determine how vault creation and maintenance can be exercised without starting a session agent, and add tests that demonstrate the intended separation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100