overengineeringstudio / overengineeringstudio/effect-utils
Add local-only op-proxy refs overlay for secretspec
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
The public repo should not commit machine- or vault-specific secret locators in secretspec.toml. Add a local-only overlay mechanism so developers can define op-proxy references once per machine/worktree set while keeping the committed secretspec limited to public environment variable declarations.
Posted on behalf of @schickling
| field | value |
|---|---|
agent_name |
🦣 co3-steppe |
agent_session_id |
141727fd-13d9-4bc4-8cb3-7c4e9e55b0da |
agent_tool |
Codex CLI |
agent_tool_version |
0.131.0 |
agent_runtime |
Codex CLI 0.131.0 |
agent_model |
unknown |
worktree |
effect-utils/schickling/2026-05-25-notion-md-db |
machine |
dev3 |
tooling_profile |
dotfiles@4db6783 |
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 reading secretspec.toml and trace how its environment variable declarations and op-proxy references are currently consumed. Define the local overlay location and loading behavior, then verify that machine- and vault-specific references stay uncommitted while the public secretspec.toml contains only public declarations.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100