v3.5.4 — FactorForge

Changed

• Made shared PostgreSQL persistence explicit and lazy so standalone package imports,
  CLI use, and CDS design do not require database dependencies or a running server.
• Removed credential-bearing PostgreSQL defaults and added redacted persistence status
  metadata for diagnostics.
• Added role-qualified input/output sequence identity for persisted campaigns through
  the eijex-db-core schema, without storing raw sequence text in campaign rows.

Fixed

• Fixed web initialization after removed manual controls and unscoped result
  provenance references; retained upload-first policies with collapsed advanced
  settings. The incomplete modal builder is withheld from the verified runtime.
• Made private suite-schema tests explicitly opt-in instead of requiring a
  developer's absolute Windows workspace path on public CI runners.
• Removed the misplaced daily AgentOS learning schedule from this public repository;
  retained manual dispatch with an explicit missing-runner diagnostic. This does
  not enable, train, or certify an AgentOS learning service.
• Preserved private batch sequence previews using verified, explicitly configured
  sequence artifacts; included canonical sequence IDs and SHA-256 identities.
• Serialized integrated writes and reject retries with conflicting sequence or metric
  provenance rather than silently retaining a different result.
• Restricted wheel discovery to FactorForge modules and pinned the declared PostgreSQL
  driver explicitly across supported SQLAlchemy versions.
• Removed shadowed CLI audit registration and unused imports without changing engine
  scoring or codon-reference data. Versioned reproducibility deposits remain immutable.

Deployment boundary

• Public design remains stateless and database-free. Shared persistence is separately
  provisioned and experimental; this release performs no production database migration
  and does not automatically migrate legacy batch or campaign records.