WikiDocs

📗 Just a databaseless markdown flat-file wiki

Runssource: GitHubhomepageTypeScriptMITcommit 7fd85bf834d5

TypeScript, MIT licensed. The project labels itself: angular, cms, databaseless, electron, flat file, markdown, nestjs and sync.

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

Backend NestJS API boots and serves at port 4321 on http://[::1]:4321; all 30 backend e2e tests pass; document CRUD, tree, search, auth, accounts, settings, and guest endpoints all respond correctly with real datasets on disk.

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.08 (measured)
recorded runs
1
last tested
stars
534
forks
64
open issues
10
watchers
16
size
19 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 WikiDocs, 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.

  • Angular CLI requires Node.js v22.22.3+ but container has v18.19.11 minute
  • Desktop Electron requires --no-sandbox flag and dbus is unavailable in container
Install time
7 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
curl http://localhost:4321/api/health returned 200, POST /api/initialize returned 204, POST /api/authenticate returned JWT, POST /api/document?path=/test-page returned 204, GET /api/document?path=/test-page returned full document, GET /api/tree?path=/ returned tree with 1 leaf, GET /api/search?query=Hello returned 1 result, GET /api/settings returned settings
Model tokens used
99,348
Exact commit tested
7fd85bf834d5
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.

Ran all test suites.
=== Frontend Tests: Full output ===
> [email protected] test
> ng test
❯ Building...
✔ Building...
Application bundle generation complete. [0.856 seconds] - 2026-10-18T22:22:41.639Z
 RUN  v4.1.9 /work/repo/frontend
Here is my final report. I have observed everything directly — no assumptions.
tokens used
99,348
Here is my final report. I have observed everything directly — no assumptions.

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.
  • Recovered from all 2 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 MIT, as reported by its host.

What did not, or is not known

  • Took 7 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 10 angular projects Argusic has installed and timed, WikiDocs was the 7th fastest to reach a running state, and 10 of 10 reached one at all.

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

Topics (from GitHub)

angularcmsdatabaselesselectronflat-filemarkdownnestjssynctypescriptwikiwiki-enginewysiwyg

Embed the badge

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

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

Questions

Does WikiDocs run?
Yes. WikiDocs runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test WikiDocs?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7fd85bf834d5. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test WikiDocs?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does WikiDocs take to install?
7 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 WikiDocs need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing WikiDocs?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does WikiDocs compare with the alternatives?
Of the 10 angular projects Argusic has installed and timed, WikiDocs was the 7th fastest to reach a running state, and 10 of 10 reached one at all.
Where is the evidence for WikiDocs?
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