Greenhorn / literal onboarding audit

Leaflet-040c0b8b

DEAD END
Leaflet/Leaflet @ 300cce51 2026-07-18 15:50:18 UTC Codex · gpt-5.6-terra (build default) GPT-5.6 Luna · Azure AI Foundry (build default) Transcript JSON

Documentation finding

The literal path stopped here.

No documentation sentence licensed a next action.
No further command proposed

I expected README.md to document a next development command; it provides project information and directs contributors to the contribution guide, but states no shell command to run.

NO FURTHER COMMAND REACHED THE SHELL

Evidence, in order

Command lifecycles

A proposed command, its independent ruling, and its Docker result share one step. Nothing is silently skipped.

  1. 1

    Documentation scope

    Greenhorn loaded docs

    Documentation scope

    Loaded 1 documentation files (depth ≤2, cap 6; external links disabled).

  2. 2

    Literal stop

    Codex stopped

    Literal stop

    I expected README.md to document a next development command; it provides project information and directs contributors to the contribution guide, but states no shell command to run.

Documentation corpus

What the newcomer could read

  • README.mdlocal
Depth cap
≤2 links
Document cap
6 files
External links
Disabled
Corpus limit hit
No

Environment & boundary

How the run was contained

Source
https://github.com/Leaflet/Leaflet
Revision
300cce51fed23ac5c2dbc7491b02cfc84e3393fc
Executor
docker
Contract enforcer
GPT-5.6 Luna · Azure AI Foundry (build default)
Read the isolation statement

Ubuntu 24.04 container, new filesystem state, source copied inside at run start. Codex reasons in a separate empty host scratch directory; the Azure GPT-5.6 key stays on the host. Only accepted commands reach the container shell.

The no-peeking constraint is enforced by per-command rulings, not a filesystem barrier — an adversarial agent could read files via licensed commands. Greenhorn's agent is cooperative by construction and every command it ran is in the transcript.

Read the newcomer contract
You are a brand-new developer on your first day. You are literate, careful,
and completely unfamiliar with this project and its ecosystem's conventions.
1. Only run a command the documentation explicitly states, or the single
   unambiguous literal reading of an instruction.
2. Ambiguous instruction (multiple reasonable readings)? Do not choose.
   Halt that path and record every reading you see.
3. On failure: read the error, re-read the docs for a documented remedy.
   Never debug from your own knowledge.
4. Never install/configure/invoke anything the docs never mentioned.
5. When stuck, say plainly what you expected, what you got, and which
   sentence failed you.
6. Undocumented environment values (keys, URLs) = dead end. Never invent.
Inspect the container Dockerfile
# Deliberately small and inspectable: no project state, dotfiles, or cached package manager data.
FROM ubuntu:24.04

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update \
 && apt-get install -y --no-install-recommends ca-certificates curl git \
 && curl -fsSL https://deb.nodesource.com/setup_22.x | bash - \
 && apt-get install -y --no-install-recommends nodejs \
 && rm -rf /var/lib/apt/lists/* /root/.npm

WORKDIR /workspace
ENTRYPOINT []