Rename the app to vscode-markdown-cowriting-plugin (markdown-only identity) #35

New Issue

2026-06-12T08:09:16Z

benstull commented

2026-06-12 08:09:16 +00:00

Rename the app to vscode-markdown-cowriting-plugin (markdown-only identity)

Summary

Rename the app/repos from vscode-cowriting-plugin to
vscode-markdown-cowriting-plugin to match the affirmed markdown-only product
identity — a coordinated rename across the Gitea repos, app.json, the content
repo, and the session-history paths.

Problem / pain

F10 (#29) and the capture that preceded it (#29 / session 0028) locked the product
as markdown-only — non-markdown review was dropped as a goal. The current name
vscode-cowriting-plugin implies a general cowriting tool, not a markdown one. The
F10 spec affirms the markdown-only identity but explicitly defers the rename as
"a separate, deliberate gesture" because it touches several coordinated surfaces.

Who feels it

The developer / operator (and any future contributor) — the name sets
expectations; a general-sounding name on a markdown-specific product is a small but
persistent source of confusion, and the longer it waits the more references accrue.

Desired outcome / value

The repo, app manifest, content repo, and session-history paths all carry the
markdown-specific name, so the identity is consistent end-to-end and the dropped
non-markdown scope is reflected in the name.

Acceptance — "done right"

The Gitea code repo, content repo (…-content), and (as applicable) the
session-history target are renamed to the vscode-markdown-cowriting-plugin
family (via wgl-gitea-admin, not raw git).
app.json (name + every repos[] entry/remote) and the VS Code extension
manifest (package.json name/displayName) are updated.
Local clones' origin remotes are updated (SSH, namespace preserved); the
session-history sessions/ path layout still resolves.
Existing session transcripts and content (specs/, plans/, issues/) are
preserved/redirected — no history loss.
A green build + tests after the rename; the extension still activates under the
new id.

Scope / non-goals

In scope: the coordinated rename across Gitea repos, app.json, the extension
manifest, content + session-history paths, and local remotes.

Non-goals: any functional/behavioral change; publishing to a marketplace;
changing the cowriting.* command namespace unless trivially coordinated (decide
at execution).

Assumptions · constraints · dependencies

Deferred gesture from F10 (#29). Touches multiple repos, so it is a deliberate,
coordinated change — best done when no other session is mid-flight to avoid
path races.
Gitea repo renames go through wgl-gitea-admin (HTTP API + admin token), not
plain git. Local remotes are then re-pointed (SSH-only, namespace preserved).
Must preserve all existing transcripts/content and keep the app.json-driven
resolution working after the rename.

Source / signal

Self-originated — capture session vscode-cowriting-plugin-0031 (2026-06-12),
from the F10 spec's deferred identity decision. Spec:
specs/coauthoring-interactive-review.md §1.7 ("the rename … is a separate
deliberate gesture") / §9 ("OPEN → later: the repo rename"). Affirmed by the
markdown-only product lock (#29, capture session 0028).

Priority (WSJF)

Provisional: Value low–medium (identity clarity; not user-blocking) ·
Time-criticality low–medium (cost grows as references accrue — cheaper sooner)
· Opportunity low ÷ Size medium (coordinated, multi-repo) →
provisional priority/P3. (Decision aid, not auto-scored.)

Decomposition

Task (a coordinated rename chore, no independent feature value). Checklist:

Rename Gitea repos (code, content, session-history target as applicable) via wgl-gitea-admin.
Update app.json (name + repos[] remotes) and the extension package.json (name/displayName).
Re-point local clones' origin (SSH, namespace preserved); verify session/content resolution.
Confirm transcripts/content preserved; build + tests + activation green.

Solution notes (optional — NOT a design)

Non-binding: do this as a standalone session with nothing else in flight (avoids
session-claim path races). Gitea supports repo rename with redirect; verify
resolve-app.py still resolves the app afterward.

# Rename the app to vscode-markdown-cowriting-plugin (markdown-only identity) ## Summary Rename the app/repos from `vscode-cowriting-plugin` to `vscode-markdown-cowriting-plugin` to match the affirmed **markdown-only** product identity — a coordinated rename across the Gitea repos, `app.json`, the content repo, and the session-history paths. ## Problem / pain F10 (#29) and the capture that preceded it (#29 / session 0028) locked the product as **markdown-only** — non-markdown review was dropped as a goal. The current name `vscode-cowriting-plugin` implies a general cowriting tool, not a markdown one. The F10 spec affirms the markdown-only identity but explicitly **defers** the rename as "a separate, deliberate gesture" because it touches several coordinated surfaces. ## Who feels it The **developer / operator** (and any future contributor) — the name sets expectations; a general-sounding name on a markdown-specific product is a small but persistent source of confusion, and the longer it waits the more references accrue. ## Desired outcome / value The repo, app manifest, content repo, and session-history paths all carry the markdown-specific name, so the identity is consistent end-to-end and the dropped non-markdown scope is reflected in the name. ## Acceptance — "done right" - The Gitea code repo, content repo (`…-content`), and (as applicable) the session-history target are renamed to the `vscode-markdown-cowriting-plugin` family (via `wgl-gitea-admin`, not raw git). - `app.json` (`name` + every `repos[]` entry/remote) and the VS Code extension manifest (`package.json` `name`/`displayName`) are updated. - Local clones' `origin` remotes are updated (SSH, namespace preserved); the session-history `sessions/` path layout still resolves. - Existing session transcripts and content (`specs/`, `plans/`, `issues/`) are preserved/redirected — no history loss. - A green build + tests after the rename; the extension still activates under the new id. ## Scope / non-goals **In scope:** the coordinated rename across Gitea repos, `app.json`, the extension manifest, content + session-history paths, and local remotes. **Non-goals:** any functional/behavioral change; publishing to a marketplace; changing the `cowriting.*` command namespace unless trivially coordinated (decide at execution). ## Assumptions · constraints · dependencies - Deferred gesture from F10 (#29). Touches multiple repos, so it is a **deliberate, coordinated** change — best done when no other session is mid-flight to avoid path races. - Gitea repo renames go through `wgl-gitea-admin` (HTTP API + admin token), not plain git. Local remotes are then re-pointed (SSH-only, namespace preserved). - Must preserve all existing transcripts/content and keep the `app.json`-driven resolution working after the rename. ## Source / signal Self-originated — **capture session vscode-cowriting-plugin-0031** (2026-06-12), from the F10 spec's deferred identity decision. Spec: `specs/coauthoring-interactive-review.md` §1.7 ("the rename … is a separate deliberate gesture") / §9 ("OPEN → later: the repo rename"). Affirmed by the markdown-only product lock (#29, capture session 0028). ## Priority (WSJF) Provisional: Value **low–medium** (identity clarity; not user-blocking) · Time-criticality **low–medium** (cost grows as references accrue — cheaper sooner) · Opportunity **low** ÷ Size **medium** (coordinated, multi-repo) → **provisional priority/P3**. (Decision aid, not auto-scored.) ## Decomposition Task (a coordinated rename chore, no independent feature value). Checklist: - [ ] Rename Gitea repos (code, content, session-history target as applicable) via `wgl-gitea-admin`. - [ ] Update `app.json` (`name` + `repos[]` remotes) and the extension `package.json` (`name`/`displayName`). - [ ] Re-point local clones' `origin` (SSH, namespace preserved); verify session/content resolution. - [ ] Confirm transcripts/content preserved; build + tests + activation green. ## Solution notes (optional — NOT a design) Non-binding: do this as a standalone session with nothing else in flight (avoids session-claim path races). Gitea supports repo rename with redirect; verify `resolve-app.py` still resolves the app afterward.

benstull added the type/task priority/P3 labels 2026-06-12 08:09:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: benstull/vscode-cowriting-plugin#35