[MarkusNeusinger]

Summary

Package E of the portfolio framing, plus B-03. It shows what the human behind anyplot does, in the owner's own wording, and backs every claim with a link to code or docs.

• README. A "How I build anyplot" section on the first screen (the owner's approved text, verbatim). "Engineering highlights" lists seven decisions, each with its reason and the code that carries it out. "Architecture" has two Mermaid diagrams: the services, and the pipeline.

• Docs page docs/concepts/ai-workflow.md, "How anyplot is built with AI agents". It covers:

  • who does what;
  • what the owner brings, built on facts confirmed from his CV;
  • the path of a change;
  • how a repeated mistake becomes a rule, with three dated cases from .claude/guardrails.md;
  • the feat(agent-chat): .create_plot() confirms and plots in one click #12557 timeline;
  • the limits.

  It's registered in all three parts of docs/index.md, and the README links it.

• Site. The About page gets one short section each on the review, "Use with my data" and MCP, linked to /stats, /plots and /mcp. The bot HTML of /about (_ABOUT_BOT_BODY) carries the same sections. The landing page's plot of the day gets .use_my_data() beside github.open(). It shows only when useAgentEligibility names a lane for its pair, with one request per view. The chat records the new source agent_open{source: plot_of_the_day}: one line in OPEN_SOURCES, documented in plausible.md and in the design doc's entry points.

Plan

The draft the owner reviewed lives outside the repository. Where the build departs from it:

• Two diagrams instead of one. On GitHub the single diagram came out 1,674 px tall in a frame capped at 1,383 px, which cut off anyplot-renderer. GitHub's Mermaid ignores a subgraph's direction once its nodes link outside it, and it wraps long labels. The services and the pipeline share only the storage, so each gets its own diagram. Both now fit their frames at scale 1 with 16 px text, measured on the pushed branch.
• The edge api -- … --> chat targets the subgraph on purpose. An edge to the node agents would make GitHub ignore the subgraph's left-to-right direction, and that inherited direction is what stacked the boxes into the tall, clipped layout. A pre-PR check noted that some older Mermaid renderers reject edges to a subgraph. GitHub renders it, and the README is read there.
• "the stats page shows the score distribution per library". The draft said "every score is on the stats page", but the page shows the average, the distribution per library and the top 8, not every score.
• 869 merged pull requests, re-counted on 2026-11-04 (gh pr list --state merged --author MarkusNeusinger): 866 into main and 3 into other branches. The approved text said 864.
• plot_of_the_day is a new source rather than a reuse of landing, which is documented as the 2026-11-02 hero line.
• On a phone, the plot of the day's two actions take their own line below the filename, right-aligned, so the filename keeps its width. From 600 px up, and whenever the entry is absent, the header stays on one line as before.

Texts to read

The README's "How I build anyplot" section is the owner's approved text, verbatim, with 869 in place of 864. Everything else this PR adds that a visitor or reader sees follows.

About page (AboutPage.tsx, house style)

• ❯ review: every implementation is scored before it ships. automated checks come first: the code runs, the image isn't blank, the canvas has its size. then an ai reviewer scores the render on a 100-point rubric of 24 criteria — visual quality, design, spec compliance, data quality, code quality, and library mastery — blind to any earlier score. a first review needs 90; below that, ai repairs the defects the review named and the plot is reviewed again, up to four times. the [stats page] shows the score distribution per library.
• ❯ use with my data: experimental, open to everyone since 2 november 2026. [pick any plot], choose .use_my_data(), and paste your data. an agent adapts that plot's code to your columns, renders it in a sandbox with no network access, reviews the render against the catalogue's rubric, repairs it once if needed, and hands back the image and the code. your chat and data live only in server memory and are deleted after an hour idle, unless you send feedback.
• ❯ mcp: the same catalogue, served to ai coding assistants over the model context protocol. six tools search specs by tag, return a spec with its implementations, and fetch one library's code, so your assistant starts from code that already rendered and passed review. setup on the [mcp page].
• ❯ origin, changed: built in Visp, a small town in the Swiss Alps, by a physicist and data analyst looking for one place to find the right plot for the data in front of him — and a way to explore what each library does best. (It said "by a data scientist". The new wording matches the README's "physicist" and the style guide's "data analyst" in §3.8. The bot HTML has no origin section, so there's nothing to mirror.)

Bot HTML of /about (api/routers/seo.py): the same three new paragraphs in sentence case, under <h2>Review</h2>, <h2>Use with my data</h2> and <h2>MCP server</h2>.

Plot of the day (PlotOfTheDayTerminal.tsx): the visible label .use_my_data() and the accessible name Use with my data (the existing USE_MY_DATA_LABEL).

README "Engineering highlights" and "Architecture"; docs/concepts/ai-workflow.md: as in the draft the owner reviewed, with the deltas listed under Plan. "What I bring" uses only the CV facts the owner confirmed:

• an apprenticeship as an energy electronics technician;
• a physics Diplom from Heidelberg University (2012) and its thesis;
• data analyst, then senior data analyst, in steering system development since 2013;
• defichain-data (2022 to 2024), built and run largely without AI.

It names no employer and claims no security experience.

Test plan

• App: yarn lint, fm:check, type-check, test (1,654 passed), build.
• Backend: ruff check ., ruff format --check ., mypy api core, and pytest tests/unit tests/integration -n auto (26,834 passed, 176 skipped).
• uv run python -m tools.changelog check --base origin/main
• Browser, headless playwright-core on a local dev server against the public API, with the chat build flag on. /agent/lane and /agent/eligibility were mocked, and every /agent/sessions request was aborted, so no session opened.
  • At 1440 and 390 px, light and dark: the plot of the day's link is 12 px MonoLisa, the same colour as github.open(), with no page overflow. The click opens /agent?spec=…&library=…&language=…&source=plot_of_the_day. The About sections render with their three router links.
  • Console: only the known font-CORS noise from a localhost origin. No 4xx or 5xx.
• The plot of the day's header, measured with the entry shown:
  • 390 px: the actions on their own line, with 274 of the filename's 307 px visible (before, it shrank to plot…);
  • 360 px: 244 px visible;
  • 600 px and 1440 px: one line;
  • without the entry at 390 px: one line, as before.
• GitHub rendering on the pushed branch: the headings are in order, the #engineering-highlights anchor resolves, and both Mermaid frames fit (899 and 712 px, scale 1, 16 px text).
• Unit tests:
  • the plot of the day shows no entry without a lane; on the public lane it links through the router, on the admin lane with a full page load;
  • the About page's three links go through the router;
  • the bot page carries the three sections and their links.
• Pre-PR Gemini 3.8 Flash check on 10b83612: nothing blocking. Its one low finding, the subgraph edge target, is kept on purpose (see Plan).

https://claude.ai/code/session_01H7HSkGyea1k2v293XiAMo8

[Copilot]

🟡 Changes recommended

Approval is blocked by two active nit findings: missing page-level analytics coverage for the new allowlisted source and a missing required status line at the start of the new concept page.

2 open issues

• Test plot_of_the_day analytics on AgentChatPage · New
• Add the required dated status block below the H1 · New

What changed in this PR

This pull request adds portfolio framing for anyplot, documents its human-led AI development workflow, expands the About and SEO pages, and introduces an eligibility-aware .use_my_data() entry point for the plot of the day.

Changes:

• Adds README engineering highlights, architecture diagrams, and AI workflow documentation.
• Expands About-page, bot-rendered SEO, analytics, and agent-network content.
• Adds plot-of-the-day agent routing, responsive actions, source attribution, and tests.

File	Description
tests/​unit/​api/​test_routers.py	Verifies the SEO About page contains the new sections and links.
README.md	Adds owner perspective, engineering highlights, architecture diagrams, and documentation links.
docs/​reference/​plausible.md	Documents the new analytics source and About-page destinations.
docs/​index.md	Registers the AI workflow documentation throughout the index.
docs/​concepts/​ai-workflow.md	Documents roles, development flow, guardrails, timeline, and limitations.
docs/​concepts/​agent-network.md	Documents the plot-of-the-day agent entry point.
changelog.d/​portfolio-framing.md	Records the user-facing portfolio and landing-page changes.
app/​src/​sections/​landing/​PlotOfTheDayTerminal.tsx	Adds the eligibility-aware .use_my_data() action and responsive layout.
app/​src/​sections/​landing/​PlotOfTheDayTerminal.test.tsx	Tests eligibility behavior and public/admin routing.
app/​src/​pages/​AgentChatPage.tsx	Accepts plot_of_the_day as an analytics source.
app/​src/​pages/​AboutPage.tsx	Adds review, agent-chat, MCP, and updated origin content.
app/​src/​pages/​AboutPage.test.tsx	Tests the new About-page links.
app/​src/​hooks/​useAgentLaneOpen.ts	Updates entry-point documentation for the plot-of-the-day action.
api/​routers/​seo.py	Mirrors the About-page additions in bot-optimized HTML.

_{Review effort: Lite}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!