Skip to content

CONTEXT.md

Latest commit

 

History

History
119 lines (103 loc) · 7.99 KB

CONTEXT.md

File metadata and controls

119 lines (103 loc) · 7.99 KB
Raw

Current context

Updated: 2026-10-23. Workspace: X:\ai-github.

Resume

Read this file, run git status --short and npm run doctor, then follow the user's current request. Use npm run map -- for entry points and focused tests. Development, architecture, API and design own their contracts. Preserve local changes and history.

Direction and preferences

The user selected a complete LOCAL application and authorized AGPL-3.0 source publication at antropos17/commit-zero. The core is an agent workspace: projects, files, issues, PRs, forks, stars, versions, general/project chats and live attributable history. Preserve the existing GitHub-like UI; improve UX without restyling. No More menus or accordions. UI is English; chat Russian; documentation English. Subagents and external AI CLIs require a direct user request. Never merge old work implicitly.

Local product

  • Agent workspace uses real local Builder and separate Reviewer calls. Projects can be created, forked independently, filtered, archived and exported. New source starts explicitly empty until an agent implements it. Retained history remains.
  • Issues have comments and open/closed state. Tasks link to issues, chat messages and previous PRs. Merging closes a linked issue transactionally. PRs support discussion, close/reopen and revision tasks; duplicate retained code is rejected.
  • Saved local agents can author proposals through owner-checked profile lookup. Read-only discovery preserves selected IDs and offers explicit retry. Project scope, local provider/model, propose/discuss/star capabilities and duration are enforced. Reviewer is host-controlled: new findings require bug, file/line, evidence, consequence and minimal fix; uncertainty is separate. Contract. Merge remains explicit.
  • Source changes modify or add one bounded JavaScript file; parser checks never execute it. Existing permissions do not authorize arbitrary host execution.
  • Versions reconstruct exact merged source, including files added by a PR. Git fast-import exports those versions to ordinary Git. No remote clone/push server.
  • ai-git/1 and npm run aigit provide explicit revision-checked Commons operations. The older cz-agent/1 scenario query contract remains read-only and compatible.
  • General/project timeline filters expose real author and project activity. Polling preserves drafts, reading state and focus; navigation does not hide sections.
  • Model inset links open scenario profiles or /model/ for actual Commons work. Profiles/projects separate creation, merged improvements, forks and unmerged PRs; contribution rows link to exact changes and versions. Accepted means merged. Scenario creation labels its unavailable initial diff. Project timelines expose model roles, operator decisions, timestamps and exact PR links; queued updates retain reading position. Fresh links reset scroll; Back restores it.
  • Layout uses a main work area and supporting column, with permanently open sections. Mobile keeps three navigation groups and local code/feed scrolling. DESIGN.md owns the composition; cross-page evidence is in runtime/verification/compact-pages-2026-10-19.json. Commons caches one run snapshot.
  • Language lab uses actual inference and a bounded host interpreter for evolving games/strategies, loss feedback, specialists and live spectator replays. It is not arbitrary native/JavaScript execution or model-weight training.
  • Original repositories, rankings and scenario participants remain a separate deterministic simulation. Never attribute that activity to real model execution.

Storage and operations

  • Migrations 004/005 normalize projects, jobs, events and issues. Every mutation checks its expected revision inside a transaction. Only changed records are written; issues do not rewrite project source. Events remain append-only.
  • Commons/lab ETags skip unchanged hydration and response bodies. Event cursor pages use a matching index; the current UI still loads full changed snapshots.
  • npm run db:snapshot requires stopped embedded stores, takes exclusive locks and copies workspace plus identity with SHA-256 manifests. db:verify-snapshot checks every file. Snapshots, credentials, databases and receipts are never pruned.
  • Applied SQL is immutable. Add migrations; never edit checksummed SQL or remove a store lock to force access. Rehearse migration/restore on separate copies.
  • Release owns the complete matrix, limits and recovery procedure; performance owns the earlier synthetic measurements.

Runtime and evidence

  • Compiled gateway 4173, development gateway 4174, dependencies 4185-4187. Services start identity before workspace so owned-agent resolution uses its actual port. Avoid simultaneous supervisors. npm start serves dist; build after UI edits.

  • Local dev restarted on 4173 for the current UX pass; service health passed. No inference was started.

  • Stores: runtime/database and runtime/identity. Preserve .env, accounts, runs, backups and verification receipts. .env is not automatically read.

  • Local llama.cpp 8199: cz-local-coder, Qwen2.5-Coder 7B Q4_K_M. Model readiness is distinct from HTTP health. No paid keys are required for local proposal work.

  • Existing Commons run 49092854-f9bd-4b7a-8d12-4ac5ea0e5f70 retains the approved, unmerged safe-timer change from job 811bdb98-bcbb-4b65-80b9-f19693aef6b4. Preserve it. 29 earlier lab experiments were verified before this release work.

  • Public source: antropos17/commit-zero. The current handoff and evidence:status resolve exact checked commits/CI; preserve separate histories. README GIF is a 15.8s condensed walkthrough of retained Sequence Kit work, not a continuous live recording. Static fallback included; desktop/mobile and all three CI jobs passed. Evidence: runtime/verification/github-readme-gif-2026-10-19.json.

  • Signal Kit: four tasks/seven calls, no merge; archived v0. Preserve failed attempts. Temporary GIF copies remain after policy-blocked cleanup; see today's history.

  • Arbitrary-code execution remains unavailable. OAuth needs the user's app settings.

  • Public TLS, shared-write account authorization, external PostgreSQL load/HA and remote Git hosting are outside the explicitly selected local release.

  • Workspace UX preserves GitHub styling: All projects replaces the repeated catalog; New task opens a dedicated main composer, retains drafts and returns to the source section/PR/task/version. Tabs retain viewport position; Back/Forward and Chat restore reading. Project filters, task next actions, pending-message drafts and recovery focus improved; receipts: runtime/verification/workspace-improvements-2026-10-23 (prior: ux-scroll-2026-10-21). Earlier real inference journey and limits.

Verification

Use fast/focused suites while editing. npm run check remains mandatory: lint, repository integrity, Node tests, build, compiled DOM/axe and HTTP serving. Only a passed stable-source report in .cache/verification/latest-full.json applies to the indexed hash. Freeze source during the final gate; keep immutable receipts under runtime/verification. Mocked tests never count as actual inference. Full/browser receipts stay separate; npm run evidence:status binds current source. Run diagnostics before/after heavy batches; keep temporary output in .cache/tmp. Retention applies only to disposable qa-* diagnostic files (7 days / 50 MB).

Mission: 18 disabled proposed roles, concrete host fixtures, provider drafts and seeded reproductions; no inference or code sandbox qualified in this pass. Current checkpoint and dated log.

Historical context

Dot continuation has both source locations and restart steps. Publication/GIF history and earlier history preserve evidence and prior experiments. Release operations take precedence.