pycforge-sdk 0.6.3__tar.gz

pycforge_sdk-0.6.3/AGENTS.md

@@ -0,0 +1,54 @@
+# PyCForge SDK project directives
+
+This is a separate product from PyCForge. CC alone decides and performs PyPI
+publication. Do not add GitHub hosting or publish from an assistant environment.
+
+Read `PyCForge-SDK-README-Guidelines.txt` before changing the SDK README or preparing
+distributions. Keep its prose focused on product use, human and AI clients, and
+capabilities supplied by PyCForge. Keep development-cycle status in separate
+engineering records, and align the README embedded in both distribution files.
+Preserve the approved public banner above the version heading and carry the
+plain-text guideline into every source archive. `docs/README-GUIDELINES.md`
+retains the earlier editorial context.
+
+Read docs/FRAMEWORK.md before changing the architecture. Keep the SDK backend
+independent of Qt and of engine imports in its own Python process. Console,
+Python and GUI clients must use the same public SDK service. The selected
+engine is authoritative for conversion semantics; use supported public engine
+services, never private compiler adapters or a copied converter.
+
+Preserve old project inputs and successful package artifacts on failure. Do not
+skip required fixtures, accept stale evidence, interpret offline data as execution
+authority, execute examples during browsing, or silently change conversion routes.
+
+Use explicit native verification and package registration commands. Keep all
+unmet array/resource/general-plugin requirements visible. Review installed
+artifacts in separate SDK and engine environments before delivery. Retain these
+directives, the original requirements/roadmap and reproducible verification.
+
+
+Conversion imports are an ongoing product capability; the user removed the
+previous two-library limit on 2026-10-28. Follow docs/FRAMEWORK.md, including
+contract evolution, coverage limits and old-engine/project/package qualification.
+
+The optional desktop in src/pycforge_sdk/gui uses the same headless service.
+Read revision 0.6 before altering readiness, worker lifetime or editor saves.
+Keep visual-provenance.json accurate; copied presentation assets do not authorize
+copying engine conversion logic. Run headless tests and tests_gui in separate
+SDK environments, with the selected engine installed independently.
+
+Read `docs/UI-0.6.1.md` before changing file selection or the desktop's visual
+controls. Retain custom titlebars, drive navigation, explicit interpreter
+guidance, and icon-with-text actions. Keep SDK and distribution versions aligned.
+
+The SDK uses the original code-bracket mark and copper-orange accents from its
+approved banner. Keep this identity in gui/identity.py and resources/sdk-mark.png;
+do not recolor the preserved shared visual files. See docs/UI-0.6.1.md.
+
+Read docs/UI-0.6.2.md before changing startup discovery. Keep discovery headless, bounded and cache-preserving; keep user choice and cancellation explicit. Only a successful live connection updates the saved interpreter. Retain the original banner icon on startup, main window and dialogs.
+
+Read docs/Workbench-1.0.md before changing engine-driven forms or Help. Preserve compatibility for additive workbench metadata; reject unknown required semantics before cache replacement. No library-name dispatch belongs in the SDK.
+
+For SDK 0.6.3, read the structured-value section of docs/FRAMEWORK.md. Preserve
+engine-owned forms and report the actual engine-produced package format. New
+library support must not add library-name or conversion dispatch to this SDK.