feat(workspace): interview and follow-up workflow
Phase 5.5. Completes the lifecycle after submission: prepare, communicate, chase. Interview preparation gets a durable, user-owned store. There were already two per-application AI stores, InterviewPrepNote and AiWorkspaceNote, but both are caches that regenerate when their context signature changes — anything a user typed into them would eventually be overwritten. InterviewPrepItem is the side nothing regenerates, covering company research, technical notes, behavioural answers, STAR examples and the user's own questions in one table, because those categories differ only by label and adding one must not need a migration. Each item records whether the user wrote it or accepted a suggestion, and an IsPrepared flag makes the section double as the preparation checklist. Generation stays in the existing AiWorkspaceService "interview" module, appended to AiInteraction as before. A suggestion is history until the user adds it as a prep item; opening the section generates nothing. Follow-up reuses what exists rather than adding a tracker. The date is JobApplication.FollowUpAt, the same field RulesEngine and the reminder hosted service already act on, so reminders keep working with no new wiring. The task stays an ApplicationChecklistItem in the follow-up category — the section counts open tasks without owning them. The record is a FollowUpSet JobEvent, the same type the rest of the app emits. Communication is untouched: Correspondence already owns recruiter contacts, history and notes, and the workspace already mounted it. The timeline interpreter learned five more types — InterviewScheduled, InterviewCompleted and OfferReceived as milestones, FollowUpCreated and FollowUpCompleted as routine, deliberately outside the milestone spine so it stays a summary of what actually happened. JobEvent remains the history source. InterviewPrepItems is reconciler-owned with a no-op migration, guarded on JobApplications, and verified on a fresh MariaDB 11: int AUTO_INCREMENT primary key, varchar owner and title, tinyint flag, datetime(6), composite index inside the key limit. 371 backend tests, 128 frontend tests, Release build and the production build all pass locally. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -94,6 +94,13 @@ public sealed class ApplicationTimelineService : IApplicationTimelineService
|
||||
"Restored" => (CategoryLifecycle, "Application restored from trash", false),
|
||||
"Undo" => (CategoryLifecycle, "Change undone", false),
|
||||
"StatusChanged" => (CategoryStage, StatusSummary(e), IsMilestoneStatus(e.NewValue)),
|
||||
// Phase 5.5 lifecycle events. Interviews and offers are milestones; scheduling and
|
||||
// completing a follow-up is routine, so it stays out of the milestone spine.
|
||||
"InterviewScheduled" => (CategoryStage, InterviewSummary(e, "Interview scheduled"), true),
|
||||
"InterviewCompleted" => (CategoryStage, InterviewSummary(e, "Interview completed"), true),
|
||||
"OfferReceived" => (CategoryStage, "Offer received", true),
|
||||
"FollowUpCreated" => (CategoryFollowUp, FollowUpSummary(e), false),
|
||||
"FollowUpCompleted" => (CategoryFollowUp, "Follow-up completed", false),
|
||||
"FollowUpSet" => (CategoryFollowUp, FollowUpSummary(e), false),
|
||||
"ResponseUpdated" => (CategoryCommunication, ResponseSummary(e), false),
|
||||
"ReplyReceived" => (CategoryCommunication, "Reply received", true),
|
||||
@@ -115,6 +122,15 @@ public sealed class ApplicationTimelineService : IApplicationTimelineService
|
||||
return from is null ? $"Moved to {to}" : $"Moved from {from} to {to}";
|
||||
}
|
||||
|
||||
private static string InterviewSummary(JobEvent e, string prefix)
|
||||
{
|
||||
var detail = Clean(e.NewValue);
|
||||
if (detail is null) return prefix;
|
||||
return DateTime.TryParse(detail, out var parsed)
|
||||
? $"{prefix} for {parsed:d MMMM yyyy}"
|
||||
: $"{prefix} — {detail}";
|
||||
}
|
||||
|
||||
private static string FollowUpSummary(JobEvent e)
|
||||
{
|
||||
var to = Clean(e.NewValue);
|
||||
|
||||
Reference in New Issue
Block a user