Librian

【Librian】簡明強大的 Galgame | Visual Novel 引擎

Runssource: GitHubhomepagePythonMPL-2.0commit 4c8fd4168793

Python, MPL-2.0 licensed. The project labels itself: galgame, game engine, python3 and visual novel.

Librian runs. An Argusic agent installed it in 8 minutes and hit 12 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Librian Galgame engine package installs successfully and all 11 tests pass: 5 webview unit tests, 1 JS bridge test, and 5 integration tests covering liber compilation, script execution, window launch, and HTTP listen mode API. The listen-mode HTTP server accepts liber scripts via POST /liber and returns 200 OK.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.16 (measured)
recorded runs
2
last tested
stars
788
forks
42
open issues
4
watchers
7
size
90 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing Librian, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • pywebview橋.js navigation did not preserve _librian_webview param2 minutes
  • _窗口尺寸 method tried to call ctypes.windll on Linux under mock1 minute
  • pywebview橋.js 退出() handler missing1 minute
  • Missing librian面板 template dependency1 minute
  • ctypes.windll used on non-Windows platform0.5 minutes
  • _注入橋 did not check for _librian_exit=1 URL param0.5 minutes
Install time
8 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
12 hit, 12 fixed with no human help
How the result was proved
python -m unittest tests/test_webview.py -v exited 0 (5/5 passed), node tests/test_pywebview_bridge.js printed 'pywebview bridge tests passed', python 測試.py ran 4/4 tests OK (test_編譯, test_劇本, test_main, test_port), curl -X POST http://localhost:8000/liber returned HTTP 200 with {"status": "ok"}
Model tokens used
312,935
Exact commit tested
4c8fd4168793
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

10. `測試.py/test_port` no server startup wait → added retry loop
11. `山彥.js` crashes on JS evaluation when page not loaded → wrapped in try/except
12. `Qt` xcb plugin requires display → used `QT_QPA_PLATFORM=offscreen`
**Verification**: All tests pass: 5 Python unit tests, 1 JS bridge test, and 4 integration tests (c…
exec
/bin/sh -lc "cat << 'ENDJSON'
{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 8, \"errors\": [{\"m…
ENDJSON" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8, "errors": [{"msg": "cty…
tokens used
312,935

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 8 minutes.
  • Recovered from all 12 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MPL-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 8 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.16
Argusic Runner1/3Runs with mocks92.000.13

Topics (from GitHub)

galgamegame-enginepython3visual-novel

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Librian.svg)](https://argusic.com/subject/librian)

Questions

Does Librian run?
Yes. Librian runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 12 errors on the way, and recorded the session.
How did Argusic test Librian?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4c8fd4168793. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Librian?
The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Librian take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does Librian need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Librian?
12 things broke in the recorded run, and 12 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for Librian?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion