Skip to content

chore: remove local repository map command - #109

Merged
justinhelmer merged 1 commit into
mainfrom
plan/in-https-github-com-core-6c8727/u1
Sep 22, 2026
Merged

justinhelmer merged 1 commit into
mainfrom
plan/in-https-github-com-core-6c8727/u1

Conversation

@justinhelmer

@justinhelmer justinhelmer commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

The CLI no longer exposes polylane map or carries machinery used only to launch local repository mapping. This keeps setup focused on connections and removes a dead fallback coordinated with the installer and platform cleanup.

Why: Local repository mapping backed an installer path that is being removed across Polylane. Leaving the command and headless-agent recipes behind would preserve an unsupported entry point and unnecessary maintenance surface.

Rollout hold: Do not merge or publish this PR until the polylanedotcom installer change is merged and live. The nominal MCP/server removal follows this CLI release.

Where to look

  1. Command registration shows the remaining CLI surface without map. ⚠ A stale registration would keep the removed command reachable.
  2. Agent registry keeps setup metadata while dropping mapping-only launch recipes.
  3. Resolution regression pins map as removed and excludes it from resource groups.

Feedback wanted: Check that no remaining setup behavior depends on the removed headless-run metadata and that the command surface is fully closed.

Risk: A missed reference could expose stale help or break agent setup. Roll back this single commit if coordinated installer/platform removal is delayed.

Verified: 87 focused tests, scoped ESLint, diff check, and removal-residue check passed; full CI is pending.

Decisions (1)
  • Remove mapping-only agent metadata. The headless recipes and lookup helpers had no supported consumer once polylane map was removed, so retaining them would create dead API surface.
Validation (4 criteria)
Criterion Proof
Removed command no longer resolves Focused command-resolution tests passed (87 focused tests total)
Mapping-only symbols and references are absent Removal-residue check passed
Touched TypeScript satisfies lint rules Scoped ESLint passed
Complete repository validation CI pending
For agents

This is one part of a coordinated three-repository removal: polylanedotcom removes the installer fallback and nominal removes the platform mapping APIs and storage. Review this PR for CLI-local completeness without expecting those sibling changes in this diff.

Co-Authored-By: coreplane-switchboard[bot] <318072483+coreplane-switchboard[bot]@users.noreply.github.com>

@coreplane-switchboard coreplane-switchboard Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM: The unsupported map surface and its mapping-only machinery are removed completely without disturbing setup or MCP behavior.

Note

Approved · head ecc024c · no findings

Full review

No findings; the removal is complete and preserves unrelated setup and MCP behavior.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved: coreplane-switchboard[bot] reviewed this PR and posted an LGTM verdict (see its review). A repo admin enabled this via the auto-approve workflow.

@justinhelmer
justinhelmer merged commit 0d1d047 into main Sep 22, 2026
4 checks passed
@justinhelmer
justinhelmer deleted the plan/in-https-github-com-core-6c8727/u1 branch September 22, 2026 18:31
@justinhelmer

Copy link
Copy Markdown
Contributor Author

Rollout hold: do not merge or publish this CLI removal until the coordinated polylanedotcom setup-script change is merged and confirmed live. After the CLI release is published, remove/deploy the nominal MCP/server mapping surface last.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant