4 Commits

Include renames

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	e35aea5045	Test levels: smoke e2e on PRs, the full set on e2e:full and before a release ... - Every PR: lint, unit tests across the runner's cores (pytest-xdist), 16 property walks from a seed that moves with the run number, integration tests, and the end-to-end smoke tests (the slice, a conversation filed as work, a question; `smoke` marker). - A PR labelled e2e:full, a push to main, or a manual run: all 48 walks and the whole end-to-end suite. Adding e2e:full to a PR runs it; any other label runs nothing. - A published release runs the full set before its image is built. - The walk's seeds come from NISSE_WALK_SEEDS / NISSE_WALK_FIRST (48 from 0 by default). Measured here: the unit tier on 2 workers took 3m49s against 6-8 minutes serially. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-07 22:29:41 +00:00
dongarandClaude Opus 5.5	679ace1fd8	A repository per test run instead of the shared sandbox ... Every live test that touches a repository gets one of its own from e2e_support.fresh_repo, made by the test operator as an operator makes a project's (D4, D8): seeded from tests/integration/seed/ (the sandbox's package, without past runs' leftovers), the agent's account a collaborator with write access, main protected (pushes only by the owner, an approval to merge), and a deploy key generated for the run. It is deleted afterwards (NISSE_E2E_KEEP_REPOS keeps it); scripts/e2e-cleanup.sh deletes leftovers. - Both e2e fixtures use it; per-run base branches are gone. The merge helper approves first, as the protection now requires. - test_gitea_live uses it, so CI needs NISSE_OPERATOR_TOKEN and no longer writes the sandbox deploy key (NISSE_PUSH_KEY). - A live test of the helper: seeded, shared with the agent, protected against it, deleted. - nisse-test.yaml's project entry is a placeholder; pytest and ruff skip the seed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-06 05:10:27 +00:00
dongarandClaude Opus 5.5	b9f52be42c	Add the end-to-end test, run after each milestone (M1.6) ... tests/integration/test_end_to_end.py drives the whole assembled agent (real models, the Gitea sandbox, a real build host) through a milestone with a scripted operator, and checks what bring-up run 3 checked by hand: a PR holding only the work, pushed with the push credential; no credential in the clone; the planner's view carrying facts, not the executor's turns. It cleans up after itself on the sandbox and the build host. scripts/e2e.sh runs it on the bring-up build VM (or --local). It has its own marker, e2e, kept out of check.sh and CI since it spends tokens. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-02 22:59:13 +00:00
dongarandClaude Fable 5	c1041a5ba1	Scaffold hello-world apps, test frameworks, and Gitea CI ... - uv workspace tying nisse-core, nisse-dev, nisse-ops together (src layouts, workspace-sourced nisse-core dependency) - Placeholder hello-world entry points for both agents, calling through nisse-core to exercise the package boundary - pytest unit tests per package; integration tests (marker-gated) running the installed console scripts as subprocesses - ruff lint + format, nisse_* declared first-party - Gitea Actions workflow running lint, format check, unit and integration tests; scripts/check.sh mirrors it locally Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-09-05 18:48:51 +00:00