Pepperminty-Wiki

A wiki in a box

Runssource: GitHubhomepagePHPMPL-2.0commit 7c5062727234

PHP, MPL-2.0 licensed. The project labels itself: collaborative, knowledge, lightweight, modular, php, self hosted, selfhosted and wiki.

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

Pepperminty Wiki v0.25-dev built from source on PHP 8.3.29 in this container; the CLI version/help and search-rebuild commands run cleanly, and a fresh wiki installed via the HTTP first-run wizard served pages, handled login and page save, answered the search and status APIs, and exported a valid zip containing the created page.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.23 (measured)
recorded runs
1
last tested
stars
208
forks
22
open issues
38
watchers
6
size
9 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 Pepperminty-Wiki, 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.

  • php binary and composer missing from container; npm deps only4 minutes
  • PHP 8.3 E_DEPRECATED from ${ex_error} string interpolation printed into response body, breaking header()/http_response_code() output on CLI and web; firstrun/CLI output polluted4 minutes
  • php -S dev server backgrounded by a normal shell exited after first request2 minutes
  • php index.php exec version exits 1 (upstream behavior: version is a shell command whose return value is swallowed by the exec dispatch)
  • php index.php and php index.php exec help on a fresh dir are swallowed by the firstrun 307 redirect until firstrun_complete is set
Install time
12 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
curl -w %{http_code} http://127.0.0.1:18081/ and ?action=firstrun, ?action=firstrun-complete, ?action=checklogin, ?action=save, ?action=view, ?action=search returned 307/200/201/307/201/200/200; ?action=status&minified=true returned 200 {"status":"ok"}; export zip decoded valid; php index.php version printed v0.25-dev-7c50627 (exit 0)
Model tokens used
1,138,900
Exact commit tested
7c5062727234
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.

- `php index.php exec help` printed a PHP 8.3 deprecation (`${var}` interpolation) plus "headers al…
- Server stability: first `php -S` server died after the first request, so I wrapped server startup…
- `exec version` returning exit 1 is upstream-style behavior (`version` is a shell command whose re…
**Verified**
- Build: `./build.sh setup build` completed (42 modules, `build/index.php`).
- `composer install` exit 0 (luminous v0.7.0).
- `php index.php version` → `v0.25-dev-7c50627`, exit 0; `php index.php exec search rebuild` → `Sea…
- Web: `curl` sequence root 307→firstrun, firstrun 200, wizard POST 201, login 307, save 201, view …
- No test suite in the repo (`package.json` test script is a stub; no PHPUnit/phpunit config), so e…
**Repository changes (2 files)**
- `core/00-beginning.php` — error handler so PHP 8.x deprecations/warnings go to the log instead of…
- `core/07-unpack.php` — fixed deprecated `${ex_error}` string interpolation.

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 12 minutes.
  • Recovered from all 5 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 Runner1/3Runs100.000.23

Topics (from GitHub)

collaborativeknowledgelightweightmodularphpself-hostedselfhostedwikiwiki-engine

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/Pepperminty-Wiki.svg)](https://argusic.com/subject/pepperminty-wiki)

Questions

Does Pepperminty-Wiki run?
Yes. Pepperminty-Wiki runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test Pepperminty-Wiki?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7c5062727234. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test Pepperminty-Wiki?
The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Pepperminty-Wiki take to install?
12 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 Pepperminty-Wiki need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Pepperminty-Wiki?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for Pepperminty-Wiki?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion