Skip to content

WORKLOG.md

Latest commit

 

History

History
executable file
·
153 lines (136 loc) · 22.5 KB

WORKLOG.md

File metadata and controls

executable file
·
153 lines (136 loc) · 22.5 KB
Raw

Developer Worklog

Status: Active
Updated: 2026-06-14
Owner: Core
Purpose: Keeps track of changes and upcoming tasks.

Important: Create a log entry for every commit, describing what's been done and tracking to-dos and follow-up tasks.
ALWAYS KEEP UP-TO-DATE!

Roadmap

Usage: Use as guidance on what major changes to implement next. Keep the list up-to-date while proceeding.

  • 0.1.x Foundation

  • 0.2.x Security and extension baseline

    • Admin interface
    • Setup UI

  • 0.3.x Structured authoring and resolver foundation

    • Schema-driven content fields
    • Structured editor experience
    • Draft and publish workflow
    • Diff and review tools
    • Media library and file management
    • Navigation and sitemap builder
    • Cross-reference index and resolver foundation
    • Open: content/schema storage baseline exists; first minimal field type UI, autosave/draft storage, commit vs publish separation, media MIME/upload/thumbnail defaults and exact private-delivery strategy, menu types/depth/sitemap formats, resolver-token/query syntax, depth, loop protection, ACL behavior, and export/import normalization remain open.

  • 0.4.x External interfaces and operations

    • Operational security and audit coverage
    • API layer
    • Frontend delivery and caching
    • Operational admin workflows
    • Scheduler
    • Import/export and LLM collaboration
    • Backup and restore
    • Contact, mail, logging, and statistics
    • IconCaptcha integration
    • Open: ActionLog live-operation foundation exists; finish durable audit retention, API write scope, public delivery snapshot vs cache-backed read model, backup/log/submission retention defaults, Scheduler execution implementation, IconCaptcha provider interface, broader secret-rotation policy, and asset policy details.
    • Logging and statistics
      • Decide long-term statistic-event compaction after the final reporting dimensions are known; granular anonymized events remain intentionally un-compacted for now.

  • 0.5.x Release lifecycle

    • Self-update and release workflow
    • Open: package signature/checksum strategy; direct vs staged updates; rollback scope.

  • Future

    • Neural-like index and semantic resolver
    • First-party modules and admin add-ons
      • Referrer/promo system with reusable tokens
      • CommunityHub
      • Inline frontpage editor
      • REI3 tickets integration

To-Do

Usage: Track deferred tasks and keep the list up-to-date.

  • ! Keep roadmap sub-items aligned with feature drafts when implementation changes scope, order, or dependencies. Last reviewed: 2026-06-06.
  • ! Before the first stable 1.0.0 release, keep Doctrine migrations consolidated into one current baseline migration.
  • ! Prefer repository/database queries over full-table PHP filtering for lists, pagination, ACL impact checks, and other scalable read paths.
  • Keep database-prefix coverage hardened by keeping Doctrine metadata self-checked against TablePrefix::TABLES, validating prefixed ORM metadata, and covering raw DBAL insert/update/join/delete prefix rewriting.
  • ! Keep Symfony service discovery narrow so DTOs, value objects, messages, events, enums, and other non-services do not bloat the container.
  • Finish the visual design-system pass and first release-readiness verification shape in the UI/UX follow-up.
  • Add portable read-model/index strategy when JSON-held values such as localized titles need frequent list-view filtering or sorting across MariaDB/MySQL, SQLite, and PostgreSQL.
  • Editor/API follow-up: when the final content/editor model lands, replace provisional API content list filtering with a domain-owned actor-aware content list/read resolver covering canonical paths, language, variants, optional version selection, pagination, filtering, and sorting.
  • Before production readiness, review public package/developer-facing class, interface, function, and Twig helper names for clarity and ergonomics; decide whether to rename directly or provide stable aliases so extension APIs read as intentional rather than provisional.
  • Audit follow-up: add a durable package lifecycle operation journal/coordinator for multi-step activation, deactivation, install, rollback, and cleanup flows.
  • Audit follow-up: design copied-session plus copied-visitor-cookie risk scoring in the Security branch; current hard session binding intentionally covers visitor changes, not complete cookie-pair duplication.
  • Audit follow-up: implement remember-me with Symfony-style persistent server-side tokens, visitor binding, explicit revocation, token rotation, and audit signals in the Security branch.
  • Audit follow-up: replace the debug account-link mail/message-log delivery stub with the real Mailer delivery contract and a dedicated Mail Message/API catalogue.
  • Audit follow-up: decide whether optional branding packages need capabilities beyond system-template; package CSS class namespace validation is now enforced for package-owned selectors.
  • Evaluate whether the documented minimum memory requirement should become 256M after PHPUnit 13.2/full-suite runs needed a higher CLI memory limit; do not fix this requirement until setup/init/lint/runtime memory behavior has been reviewed across target hosting platforms.

Branch Logs

Usage: Keep concise session notes in the active worklog and include the current branch in headings, using the form ### YYYY-MM-DD branch-name. Place new entries chronologically under the matching branch/date heading so reviewers can follow the PR context without reading full verification transcripts. Record meaningful committed or completed changes, decisions, blockers, and follow-ups; keep detailed verification in PR notes unless a result materially affects the worklog context. When switching to a different branch or after a PR is merged, compact the completed branch entry into WORKLOG_HISTORY.md, then create the new branch entry at the top.

2026-06-13 feat-symfony-ux-integration

  • Added namespace-aware Twig component primitives for root, frontend, backend, and package-adjacent UI surfaces, then wired shared alert stacks, buttons, page headers, empty states, chart/map wrappers, and form field enhancements without removing the override-friendly partial entry points.
  • Added reusable Stimulus/JS foundations for live polling, filter forms, dialog, clipboard, disclosure, tabs, notification-center behavior, Mercure alert streams, and manual one-shot polls; applied the filter/dialog/clipboard pieces to existing Admin logs/statistics/users/package/API-key surfaces where useful.
  • Reworked UI alerts into a unified dispatcher and notification center with direct, queued, and low-level push delivery modes; request-time alerts, DB-backed inbox fallback, Mercure best-effort push, polling fallback, titles, actions, loading state, and auto/hidden/persistent presentation now share one public addAlert() path.
  • Added a package-owned /api/live/{package_slug}/... endpoint registry and dispatch boundary for lightweight GET-only polling/manual interactions such as future captcha seed reloads.
  • Added a package-extendable cookie-consent foundation with duplicate-name rejection, stateless public CSRF, consent-aware cookie helpers, optional-cookie withdrawal expiry, DNT/GPC-aware defaults, and a reusable overlay that can be reopened from later privacy/footer links.
  • Added optional local Mercure tooling with installer/start/stop/health/check commands, fixed versioned Caddy-based release assets, var/mercure storage, read-only diagnostics, public subscribe probes, publish probes, setup seeding, scheduler health refresh, and graceful polling fallback when Push is unavailable.
  • Switched local Mercure signing to derive from the validated/generated APP_SECRET by default, moved local hub secrets out of process arguments, required a 32-byte APP_SECRET, and made unsupported short app secrets fail before the app-secret rotation recovery flow can mark them as healed.
  • Removed unused Alpine and ApexCharts wiring now covered by Symfony UX packages, kept UX assets lazy, repaired demo package/theme CSS validation, and clarified that asset-map:compile is production/release-only.
  • Bounded large log reading from the end of the file to avoid Admin log timeouts on large application logs.
  • Updated the design-system draft, Mercure web-server notes, class map, and related translation/catalogue entries for the new UI alert, live polling, component, cookie-consent, Mercure, and Symfony UX foundations.

2026-06-14 feat-symfony-ux-integration

  • Addressed review findings around live endpoint access and registration by making package live endpoints GET-only, enforcing minimum access levels before handler dispatch, reserving system live slugs, and preferring exact endpoint paths before broad pattern matches.
  • Applied the same exact-before-pattern selection to regular API endpoint dispatch and split the oversized API class-map entry into focused API foundation/security, endpoint registry/documentation, admin/settings, content, and package/user rows.
  • Folded ui_alert_inbox into the pre-1.0.0 baseline migration and hardened prefixed index/constraint naming for alert-inbox schema objects.
  • Hardened alert delivery and storage by scoping notification-center storage by user/session/surface, preserving closed-alert dedupe, giving queued/pushed alerts stable fallback IDs, and making explicit alert-inbox cleanup failures return a failing command status.
  • Tightened cookie consent behavior by making rejection work without JavaScript, avoiding anonymous session creation from hidden CSRF tokens, rejecting duplicate consent definitions, and expiring withdrawn optional cookies.
  • Kept profile views on cached Mercure availability only, required authenticated publish success for Mercure health, and kept setup/profile paths from starting or installing Mercure implicitly.
  • Switched local Mercure downloads from deprecated legacy assets to the Caddy-based mercure_{OS}_{ARCH} archives, used the release Caddyfile plus protected env file for secrets, normalized Windows paths, and kept PID plus exact-binary process detection for start/stop/check diagnostics.
  • Clarified Mercure public URL/reverse-proxy expectations in the web-server manual while keeping local checks precise enough to distinguish Symfony fallback responses from real Mercure SSE endpoints.
  • Replaced committed Mercure JWT defaults with ${APP_SECRET}, removed setup-time MERCURE_JWT_SECRET generation, and kept app-secret rotation naturally coupled to the default Mercure JWT key unless an operator explicitly configures a dedicated JWT secret.
  • Deferred Mercure startup out of bin/init, made setup stop stale local hubs before health recovery starts them with persisted setup secrets, and coupled app-secret rotation recovery to Mercure stop/health refresh so local hubs do not keep stale signing keys.
  • Stripped diagnostic message context from UI alert serialization so UI payloads expose only display-safe alert fields.
  • Bound cookie-consent CSRF tokens to the existing visitor identity and hardened package live/API path-pattern guards plus live dispatch route-slug checks so package-owned endpoints cannot escape their namespace through broad regex patterns.
  • Hardened late review edge cases for UI alerts, Mercure health, and setup copy by notifying only for newly created alerts, keeping server-rendered flashes visible during storage hydration, retrying transient alert-poll failures, treating disabled Mercure health as a configured success, and deriving setup secret browser constraints from the shared validator.
  • Hardened queued alert fallback by including existing session-cookie topics in /api/live/alerts without starting anonymous sessions.
  • Hardened follow-up review edges by removing PostgreSQL-sensitive lastInsertId() dependency from queued alert appends, making initial server-rendered alerts visible without JavaScript, normalizing colon-only Mercure listen addresses for local probes, and restoring timed removal of transient auto alerts without marking them as manually closed.
  • Extended the Mercure colon-only listen hardening to configured hub URLs so .env-derived http://:3000/.well-known/mercure values normalize before publish/public probes.
  • Hardened cookie consent and alert dispatch follow-up edges by clearing all rejected optional cookies even without stored consent, preserving clear-cookie response headers for rejected cookies, enforcing registered cookie identity in the consent jar, skipping topic-specific Mercure publishes while unavailable, and adding a root Twig-component namespace smoke test for root:* components.
  • Tightened production-readiness edges by SHA256-pinning Mercure release archive downloads, rejecting custom consent cookies that change registered security attributes, signing and TTL-validating consent cookies, and covering safe relative consent redirects.
  • Added lightweight native node --test JavaScript behavior testing through bin/jstest without a node_modules dependency tree, with first coverage for alert payload normalization and live polling cursor/retry/error behavior.
  • Expanded JavaScript behavior coverage with a small test-only fake DOM and Stimulus controller loader for stable controller contract tests around clipboard/dialog/disclosure/tabs/filter forms, cookie consent, alert stack behavior, alert polling, and Mercure stream reconnect handling.
  • Hardened final review edges by verifying stored Mercure PIDs against the exact binary before termination, avoiding parallel alert stream/poll delivery while adding one-shot stream catch-up from the inbox and stable Mercure event IDs, remembering auto-dismissed alert IDs, constraining package-owned necessary cookies to package-scoped host-only names, and marking Mercure unavailable when app-secret rotation cannot safely stop the local hub.
  • Hardened cookie-consent package review edges by rejecting duplicate or core-reserved package cookie definitions during package loading and validating optional-cookie privacy links before they can render in the public consent UI.
  • Hardened follow-up setup, redirect, alert-inbox, and naming edges by passing the persisted setup APP_SECRET as the Mercure setup health JWT secret, rejecting backslash/control-character local redirect targets, storing queued alert topics as bounded HMAC keys, and renaming the consent cookie to a system-owned name.
  • Replaced host-derived UI-alert Mercure topic URLs with system-owned URN topics so alert transport identifiers no longer consume HTTP route namespace or depend on DEFAULT_URI length.
  • Hardened additional review edges by running consent cookie filtering after response cookie writers, standardizing queued user alert topics on canonical account UIDs with username-to-UID normalization when resolvable, and rejecting package live endpoint root paths that cannot be routed by /api/live/{packageSlug}/{resourcePath}.
  • Hardened follow-up alert edges by preserving username case during username-to-UID topic resolution.
  • Removed the native browser notification opt-in and symfony/ux-notify dependency because UX Notify only works while a page keeps an active Mercure/EventSource stream; real closed-browser notifications need a separate future Web Push design.
  • Completed another broad review pass across URL/link sinks, browser storage naming, and Mercure secret-file handling; hardened alert action links, package metadata URLs, content redirect targets, filter-form storage names, and protected Mercure env-file rewrites.
  • Hardened the alert stream fallback so browsers without EventSource support or streams that fail before their first open switch to inbox polling without enabling parallel normal stream/poll delivery.
  • Kept operation detail overlays dismissible during running operations by showing close controls in non-terminal states and hiding details without stopping the live poller.
  • Hardened additional alert/CSS review edges by draining paginated queued-alert catch-up pages after Mercure stream opens, authorizing rendered stream subscriptions for private alert pushes, and suppressing strict-parser CSS limitations for Tailwind directives, generated modern group at-rules, and empty custom-property fallbacks only when a normalized second parse finds no adjacent syntax error.
  • Follow-up hardening pass: removed unused legacy CSS-linter wrapper names after broadening the parser-normalization scope, made the generic live poller drain has_more pages immediately when cursors advance so polling fallback behaves like stream catch-up, and made Mercure stream views drain queued alerts before connecting while queuing a follow-up drain when the stream opens mid-catch-up.
  • Follow-up: when the next feature branch starts, evaluate focused controller foundations for public consent/privacy settings, package live endpoint documentation/navigation, captcha provider/live seed flows, notification preference detail settings, and package-owned webhook/job callback endpoints before adding more broad UI surface.
  • Follow-up: add a public privacy/footer trigger for cookie_consent_trigger_attributes() so visitors with stored consent can reopen cookie preferences and withdraw or adjust optional-cookie consent.
  • Follow-up: evaluate converting high-use backend filters from GET-refresh enhancement to Symfony UX LiveComponent slices with URL-bound writable LiveProps so filter input updates can re-render only the list component while keeping shareable query parameters.
  • Follow-up: revisit the full operation overlay controller after the first real UI/UX feature slice; the polling core is now shared, but renderer/storage responsibilities can still be split further when more live consumers exist.

2026-06-12 docs-cleanup

  • Refreshed the .codex context inventory: marked the branding-neutral naming migration and first readiness audit as completed/historical, removed the obsolete standalone Symfony docs notes, made the framework recap the version-pinned dependency documentation cache, and updated it with current installed-dependency guidance for Symfony 8.1, Doctrine ORM/DBAL, Twig 3.27, Tailwind v4/TailwindBundle, Symfony UX, CommonMark, and PHPUnit 13.
  • Extended bin/lint into the all-in-one diff linting entry point: it now supports --diff, --diff=<target..source>, and --diff:<target..source>, collects staged/unstaged or explicit Git diff files when Git is available, lints extensionless PHP scripts such as bin/lint, and runs a non-Markdown Git whitespace check that preserves intentional Markdown hard line breaks.
  • Added Markdown parse coverage to bin/lint using the existing League CommonMark/GFM dependency so Markdown targets produce a real parse/render smoke-check instead of being reported as unsupported.
  • Documented the Git whitespace/Markdown hard-break rule in AGENTS.md, updated the .codex tool index and class map for the new lint modes, and compacted the old 2026-06-07 API session into dev/WORKLOG_HISTORY.md.
  • Moved the binding project rules from .codex/PROJECT_RULES.md into AGENTS.md so architecture, naming, pre-1.0.0, database, content-revision, security, and audit rules remain available when Codex project context changes or the .codex notes are not loaded.
  • Removed the obsolete .codex/PROJECT_RULES.md duplicate, updated .codex/ENVIRONMENT.md for the new /Volumes/Projekte/studio checkout path, and refreshed .codex/README.md with active context, historical audit, tool, and cleanup guidance.
  • Verified .codex/resolve_cloud_artifacts.php reports no cloud conflict artifacts; .codex/clean_ignored_artifacts.php dry-run still lists normal ignored generated/dependency directories such as vendor/, var/, assets/vendor/, translations/runtime/, and package build outputs, so no deletion was applied.

2026-06-13 docs-cleanup

  • Moved route rendering from the .codex helper into project code with php bin/console render:route /path, including optional debug role, existing user, method, host, HTTPS, setup-completion, browser-auth, and API debug context support; removed the obsolete .codex/render.php helper and updated render-review references.
  • Extended bin/lint with --staged and --changed=<target..source> while keeping Git-dependent target collection and whitespace checks graceful when Git or a work tree is unavailable.
  • Reviewed the newly installed Symfony UX package set, kept optional UX Stimulus controllers lazy, removed generated React/Vue/Icon demo files, and tied committed Mercure defaults to DEFAULT_URI and APP_SECRET for development while documenting production override expectations.
  • Updated the class map, dependency recap, local agent tooling notes, and active worklog/history to reflect the render command, lint modes, Symfony UX baseline, and branch-oriented worklog boundary.
  • Changed worklog retention from per-session compaction to branch-scoped archival, restored the current docs-cleanup branch context from history, and mirrored the rule in AGENTS.md.
  • Added Symfony UX icon locking to bin/init and the package-aware asset rebuild queue as non-blocking dependency steps, and registered active package template paths for icon/AssetMapper console scans so core and package icon references can be imported locally when Iconify is reachable without breaking offline CI or admin rebuilds.
  • Added a local-only Symfony UX icon reference check to bin/lint so static Twig icon references fail when the required locked SVG is missing, without running the mutating network-backed ux:icons:lock command.
  • Documented that locked SVGs in assets/icons should be committed as reviewable dependency snapshots while avoiding bulk-locking complete upstream icon sets by default.
  • Declared ext-sodium as a direct Composer platform requirement and added it to the PR verification runner because the Symfony Mercure/JWT dependency chain requires lcobucci/jwt, which requires Sodium.
  • Clarified AGENTS.md wording around session notes with branch/PR context and the boundary between agent-only .codex helpers and project-wide tooling.
  • Normalized AGENTS.md wording so the document reads as a standalone first-version guide rather than as a patch over earlier agent habits.
  • Disabled UX Translator TypeScript type dumps in production because the current AssetMapper setup uses JavaScript, not TypeScript, and recorded the UX Turbo 3.1 stream-listen deprecation in the dependency recap.
  • Added cache warmup to bin/init and ux:translator:warm-cache to the package-aware asset rebuild queue so var/translations/index.js exists before AssetMapper resolves assets/translator.js.

Archived Compacted Branch History