Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[docs] Core Client Boundary still lists the retired Workspace repository routes

Open Beginner friendly
  • Is something wrong?
#189 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Start with docs/specs/20260528-core_client_boundary.md: line 88 names the default repository setup routes under client.repositories, and lines 147-154 list the retired repository routes and methods. Read the hosting decision (docs/decisions/20261002-hosting_through_gateway_mcp.md) and the Workspace Data Source Catalog to find the current owners to link. Done when the retired routes and client.repositories methods are gone, the links are in place, and the documentation checks pass.

Written by the indexing model from the issue text.

Description

documentation

Problem

docs/specs/20260528-core_client_boundary.md still describes the Workspace repository routes as part of the App API: lines 147 to 154 list GET /api/app/workspaces/:workspaceId/repositories, its /diagnostics route, PUT .../repositories/default and client.repositories.list/diagnostics/setDefault, and line 88 lists "default repository setup routes" under client.repositories.

These describe the Workspace host repository resource that Hosting Goes Through The Gateway MCP retired "entirely". At 47fd8e9db52d6f4cf749dd50b4db126d67e130b1 the cutover drops workspace_repository_resources (apps/nanocore/src/storage/host-repository-cutover.ts), no production route serves these paths, and no production client.repositories owner exists. A repository is now a Workspace data source (URL and commit) under the Workspace Data Source Catalog, and remote branch, file and pull-request writes go through the Gateway-mediated vendor MCP.

A reader of the Core Client Boundary can conclude that a Workspace needs a "default repository setup" before Task work. The same stale concept appeared in the direct-Task fixed escalation condition, where it stopped the issue-to-pull-request journey during v0.1.0-rc.1 acceptance; that instruction is fixed separately.

Suggested fix

Remove the repository-resource slice from the Core Client Boundary and point readers to the Workspace Data Source Catalog for repository sources and to the hosting decision for remote writes. Documentation only; no route, client or data change. The first-release interface scope decision (item 5) already asks for old-design documents to be removed or moved to the new design.

Acceptance criteria

  • The Core Client Boundary no longer lists the retired repository routes, the client.repositories methods or "default repository setup routes".
  • It links the current owners for repository sources and hosting writes.
  • The documentation checks pass.

Not a release blocker under the rc.1 blockers-only triage: documentation only, no runtime effect. Disclosed in the release notes.

Filed from the v0.1.0-rc.1 acceptance program.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
12h 53m
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lingkaix/openkit

All issues in lingkaix/openkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.