You’re viewing Paradaux’s public workspaceSign in to vote Get taskl.ie for your team

PAR-416

Loading issues

PAR-416 · D3 · Comments and activity domain: unified timeline… · Paradaux · taskl.ie

PAR-416

D3 · Comments and activity domain: unified timeline, comment edit/delete/reactions, readable event formatting

Domain migration. Depends on D1. Backend for PAR-370.

New domain activity (rename or absorb the current activity package):
- ListTimeline(ctx, issueRef, filter) merges comments and events chronologically.
- AddComment, EditComment, DeleteComment and React.
Event formatting (the PAR-370 copy fixes): produce structured events (from → to, added/removed labels) instead of preformatted strings. The UI renders the sentence, so the backend stops emitting strings like "moved to Moved to".
REST endpoints, OpenAPI, and web domains/activity/data. Replace the Kysely timeline reads.
Mentions: @user mentions in comments create notification outbox rows (Discord DM / email). There is no in-app inbox; it was canceled in PAR-376.

Acceptance

Tests pass, and the ArchUnit store and ESLint suppressions shrink.

Activity

taskl.ie created the issue 6d ago
taskl.ie set status to In Progress 5d ago
taskl.ie5d ago
Plan (branch par-416-activity, from rebuild):
- Backend io.paradaux.tasklie.activity behind ActivityFacade (model / usecase / persistence / api / mcp / job): timeline (comments + events merged, keyset cursor), comments, addComment, editComment, deleteComment, react / unreact, workspaceActivity. The existing issue.activity outbox handler/sinks stay in the package.
- Events become structured: new issue_event.data jsonb (from/to, labels added/removed) written by the issues write use cases through IssueEvents; the server renders a sentence-case summary (backend, so web, MCP and Discord share one formatter; legacy rows without data fall back to parsing detail).
- Comment side effects go through the outbox in the same transaction (comment event -> issue.activity, @mentions -> comment.mention rows). New table for reactions (new migration, tenant-scoped).
- Provenance stays with issues (issue source data, members-only per PAR-414); activity stamps it only for comments added over MCP/Discord triage.
- REST under /api/public/w/{slug}/issues/{ref}/timeline|comments..., reads @GuestReadable, MCP tools (same names/shapes) as a McpToolProvider in activity/mcp. Remove comment/activity/provenance code and ThreadLocal use from PostgresTaskSystem, TaskMcpTools, ReportMcpTools, IssueApiController.
- Web domains/activity (data/server, hooks, timeline components) replacing the issue page Discussion/Activity sections and lib/actions comment code.
taskl.ie5d ago
PR open: https://github.com/ParadauxIO/taskl.ie/pull/57 (against rebuild). Backend, MCP, web and the ratchet numbers are in the PR body.
taskl.ie set status to Pending Release 5d ago
taskl.ie5d ago
Merged into rebuild as #57.

What's in it
- New activity domain:
  
  The timeline is @GuestReadable, and the comments list is @MembersOnly.
  
  Comments can be edited by their author only. They can be deleted by the author or an admin (never by an API key).
  
  Reactions are added.
  
  Mentions go through the outbox and are logged only until a notifier exists.
- Event summaries are written by the backend (EventSummary) and shared by the web, MCP and Discord.
Ratchet
- ArchUnit store: 679 → 567 distinct entries. A normalised diff shows nothing added. Six legacy entries were re-keyed, and the proof is in the PR body.
- ESLint suppressions are unchanged.
Handoffs
- PAR-420: ActivityFacade.addComment with a Discord context.
- PAR-370: render summary, reactions and the canEdit / canDelete flags.
- PAR-422 follow-up: add summary to the workspace activity feed.
taskl.ie changed status from Pending release to Done 5d ago

Workspace permission required to comment

Comments and reactions require workspace permission. Ask a workspace owner or admin for access. You can sign in to vote.