Repository navigation
ProcessForge 1.3.0-beta2
Pre-releaseProcessForge 1.3.0-beta2 repairs context and process catalog access to private project/workplace YAML definitions under processes/user/ and processes/custom/. Private definitions remain outside the public Core payload. The accepted Core byte image and read/write protections remain enforced.
It also fixes a Windows Python 3.11 temporary-file identity mismatch and two existing worker-input callers after their provider-adapter owner moved.
Source: 7448472aa1c1d48f02fd66fd0cae7c7d51c1e53c.
ZIP SHA-256: bb27bbe9ed5ec64c870c178e52d051ed89273e156dbdce2b001f0249b65bad1a.
Qualification: independent review; 91 focused tests passed with 2 Windows symlink-privilege skips; 6 immutable-image tests passed; all 150 temporary-disposal tests passed; conversation smoke passed; sealed archive quick checks passed using the supported timeout multiplier 4. Changed product files passed focused lint, formatting and typing checks.
Limits: Windows qualification only. General Core assurance remains open; existing broader typing diagnostics are retained. This beta does not establish POSIX, RC or stable acceptance. Installation and actual connected-host acceptance are recorded separately. Stable remains 1.2.0.
По-русски: исправлено чтение приватных проектных процессов при получении контекста PF. Они сохраняются как данные проекта или рабочего места и не включаются в публичный Core. Также исправлены ложный отказ очистки временных файлов на Windows/Python 3.11 и обращения к прежнему владельцу обработки входных данных worker.
Полные контрольные файлы доступны в GitHub release. GitVerse содержит тот же ZIP; JSON-файлы повторно не загружаются из-за ограничения вложений провайдера.
Known installation qualification limit: the beta1 updater refuses targets without native enrollment. An existing installation upgraded by the legacy updater was observed with an accepted Core image but no bound native control; its beta2 update refused before payload replacement with plan_blocked (qualified installation exclusion). No public CLI recovery command has been identified; recovery requires a supported owner handoff or cold-controller bootstrap with live authority. Installed Core, App Server restart and actual connected-host acceptance remain pending for this scenario.