Skip to content

mcpx docs: level 1 -- the 30-second layer: home, overview, quick start, install (tracker) #1894

Open

Description

@dezren39

Relocated from dezren39/darwin-nix#92 on 2026-10-28 (placement audit): mcpx's single source lives in developing-today/code (pkgs/mcpx); re-home tracked at #309. Original body below; issue references inside it are historical (dezren39/nix numbering).

Parent: #89

Purpose

Level 1: the thirty-second look. Home page, overview, quick start, install -- simple enough that a reader skimming
while doing three other things learns what mcpx is and how to get it before closing the tab.

Original notes

  • documentation
    • make a book using whatever is the most common and simple modern choice
      • 3 main things, not book sections jsut like levels of detail-
        • the 30 seconds look at home page click the overview page, click the quick start page, ctrl+w should be simple enough that even this person skimming while doing 3 different things will accidentally learn

(Lines 9-48 are quoted in the children.)

Children

Proposed order

  1. amd host fails at evaluation: no outputHashes for p2panda-core-0.7.1 #158 is the critical path for the whole docs tree: there is no tag, no release, no install script and no
    published image today (a pkgs/mcpx/Containerfile exists since Phase 5: tag event bodies must travel with the event #182 and builds locally, but nothing builds or
    pushes it), and the version is hard-coded in four places (package.nix:19, :61, cmd/mcpx/main.go:18,
    Containerfile:40). Without it the home page has no download link and no curl | sh, and the compendium has
    no version to stamp. Settle "monorepo vs its own repo" first (it decides
    tag names, go install, and the short URL).
  2. Consider moving opencode and openchamber forks to developing-today-forks organization #157 overview / quick start / install, with an honest status column per channel. It can be written before
    amd host fails at evaluation: no outputHashes for p2panda-core-0.7.1 #158 finishes (nix works today; the rest are "not started" or "partly"), and its status column is then
    regenerated from what each release publishes.
  3. 🎨 Palette: Add aria-labels to buttons and inputs #155 the home page, once chore(deps): update rust crate actix-files to v0.6.10 - autoclosed #117 has chosen the generator and amd host fails at evaluation: no outputHashes for p2panda-core-0.7.1 #158 exists.
  4. Phase 1: events, storage, crash safety, and the identity store #156 last, staged: copy-as-mcpx exec plus an in-browser run against a fake daemon now; local-daemon mode later;
    never a hosted public daemon.

Ease and impact

# Title Kind Ease Impact
#158 release.yaml, artifacts, install channels design, enhancement L (parts S-XL) high
#157 overview, quick start, install, now what docs M high
#155 home page design M high
#156 runnable editable example research, design S / M (XL if hosted) med

Warnings

Related

#117, #120 (bot home page carries the install prompt), #44 (closed, fixed in #53: plugin without the binary =
"justThePlugin"), #48, #79 (typecheck default affects quick start), #86 (daemon-served web UI), #102, #134 (container
image), #136 (platform coverage, static-build policy).

Ease · Impact · Related

See the table above; related issues listed above.

Security/auth deferred; see tracker.

Activity

  1. developing-today commented on Oct 28, 2026

    @developing-today
    Contributor
  2. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    History carried over from dezren39/darwin-nix#92 (verbatim, oldest first):


    @dezren39 · 2026-09-30T07:20:07Z

    Integration pass. Placed in the DAG rooted at #181.


    @dezren39 · 2026-09-30T11:49:26Z

    Issues pass (2026-09-30, at 05c78b2).

  3. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  4. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    agent-note:v1 · agent: repo-queue-worker-shift-b (lane B) · task 2788 · kind: triage · outcome: picked up — dedupe, child mapping, and scope confirmation against current pkgs/mcpx main; no implementation in this triage task

  5. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Triage verdict — tracker confirmed, no duplicate; all four children present as relocated code issues; critical-path claim verified against current main.

    Verified fresh at developing-today/code origin/main 2c4e7434 (2026-10-29, task 2788):

    Dedupe: #1894 is the only level-1 docs tracker; the other levels (#1898 level 2, #1907 level 3, #1888 the book, #1890 site platform) are distinct layers, not duplicates. Parent (nix #89) is the docs book tracker #1888.

    Children (historical nix numbers → code issues, all OPEN):

    nix code subject
    #158 #1881 release.yaml, release artifacts, install channels — critical path, first
    #157 #1878 overview, quick start, install page and 'now what'
    #155 #1874 the home page
    #156 #1876 runnable, editable example on the home page

    No missing children this time — all four arrived in the relocation. The generator decision the home page waits on (nix #117) is #1939.

    Scope spot-checks against current main — the critical-path claim still holds:

    Route: tracker stays open as the ordering parent. Head child #1881's triage is the follow-up (idempotent enqueue in this run returned its queue task — see the task line below); the remaining children follow in the tracker's order (#1878 can be drafted before #1881 finishes, per the tracker; #1874 waits on #1939's generator choice and #1881; #1876 last, staged). No implementation in this triage task.

    agent-note:v1 · agent: repo-queue-worker-shift-b (lane B) · task 2788 · kind: triage · outcome: triaged — tracker confirmed, 4 children mapped (1881/1878/1874/1876), critical-path scope verified on main, head-child triage enqueued/confirmed

  6. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    queue/claimedQueue worker lifecycle state
    on Oct 29, 2026
  7. 23 remaining items

  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  9. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  10. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 6855 (triage, claimed, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off (re-handoff)

  12. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Queue task 6855 is handed off to its bound OpenCode worker session ses_e5e5c6fa906ffeBFjYWRK6noer.

  13. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 6855 (triage, execution lane opencode)
    state: picked up
    checked_at: 2026-11-03T22:44:20Z
    worker: repo-worker-code
    session_id: ses_e5e5c6fa906ffeBFjYWRK6noer
    next: Re-derive tracker scope from current main and verify child issue/route state; publish evidence-backed triage verdict. No implementation in this tracker triage.

  14. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 6855 (triage, repo-health-code-pilot; lane opencode)
    state: triaged
    checked_at: 2026-11-03T22:54:48Z
    worker: repo-worker-code
    session_id: ses_e5e5c6fa906ffeBFjYWRK6noer

    Verdict

    #1894 remains a valid ordering tracker and stays open; it is not a standalone implementation task. The packet premise that it was blocked with “no path forward” is stale: work is routed through its child issues. No duplicate tracker packet or competing PR is appropriate.

    Revalidated against current main

    Main is 5c53272ff83bdf1ddffea2fb188c7d714182c9ab (AGENTS.md blob b7ef1f4da6882edb7449e21b9b2719cdf26e54d8).

    Disposition: leave #1894 open as the umbrella. No new follow-up packet: the remaining work already has child owners (#1881, #1874/#4901, #1876); #1881 is explicitly blocked/escalated, so this triage does not fork it. Follow-up docs verification should run nix build .#mcpx-docs --print-build-logs (the current mcpx-docs.yml PR build) and recheck release assets/container status against the install table. Triage required no tests.

  15. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 6855
    state: revalidated
    checked_at: 2026-11-03T22:57:00Z
    worker: repo-worker-code
    session_id: ses_e5e5c6fa906ffeBFjYWRK6noer

    Main advanced to 7a8500417188465deea72339db81fcf1a92c8448 after the verdict comment. Fresh compare from 5c53272 shows no changed pkgs/mcpx/docs/**, AGENTS.md or docs workflow files, so the cited docs/route findings stand. Freshly reconfirmed #1874 PR #4901 is still OPEN, Drew-assigned; its basic production-line check passes. Release mcpx/v0.1.0 remains published.

  16. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 6855
    state: completed
    outcome: triaged
    checked_at: 2026-11-03T23:00:05Z
    worker: repo-worker-code
    session_id: ses_e5e5c6fa906ffeBFjYWRK6noer

    Queue task 6855 is complete. #1894 remains open as the tracker; the in-flight queue/status/work labels from this claim were removed. No duplicate child task or PR was created.

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

Metadata

Metadata

Assignees

Labels

source/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions