revisions

Reviewed-on: kjannette/deClawed-Assity-Kitty#5

.gitignore

@@ -10,3 +10,5 @@ accountsAndCredentials/token.json.bak
 
 # Runtime output
 mailSummaries/
+
+// revised Aug 31

README.md

@@ -488,3 +488,4 @@ deClawed-Assity-Kitty/
 ├── .gitignore
 └── README.md
 ```
+// revised Aug 31

accountsAndCredentials/credentials.example.json

@@ -6,6 +6,8 @@
         "token_uri": "https://oauth2.googleapis.com/token",
         "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
         "client_secret": "",
-    "redirect_uris": ["http://localhost"]
+        "redirect_uris": [
+            "http://localhost"
+        ]
     }
 }

src/McpServer.ts

@@ -4,3 +4,5 @@ export const server = new McpServer({
   name: "assistant",
   version: "1.0.0",
 });
+
+// revised Aug 31

src/auth.ts

@@ -117,3 +117,5 @@ authorize().catch((err) => {
   console.error("Authorization failed:", err);
   process.exit(1);
 });
+
+// revised Aug 31

src/index.ts

@@ -18,3 +18,5 @@ main().catch((error) => {
   console.error("Fatal error in main():", error);
   process.exit(1);
 });
+
+// revised Aug 31

src/loaders/prompt-config-loaders.ts

@@ -149,3 +149,5 @@ export const getSpreadsheetId = (account: string): string => {
 
 export const getCalendarId = (account: string): string =>
     accounts[account]?.calendarId ?? "primary";
+
+// revised Aug 31

src/prompt-controller-service/prompt-controller-service.ts

@@ -54,3 +54,5 @@ server.registerPrompt(
         };
     }
 );
+
+// revised Aug 31

src/prompts/classify-emails.txt

@@ -11,6 +11,7 @@ The employer confirms receipt of my application but requires no action from me.
 
 Category B - Advancement to Next Step
 The employer wants to move forward. This includes: invitations to schedule a phone screen or interview, requests to complete an assessment or assignment, requests for additional information or documents, or any communication that requires a response or action from me. If an email both acknowledges receipt AND requests action, classify it as B.
+This does *not* include Greenhouse "security code" emails, other "confirm identity codes" or "identity-confirmation" type emails, "verify candidate account" type emails, 
 
 Category C - Rejection
 The employer declines to move forward. Typical language: "We have decided to pursue other candidates," "Unfortunately, you were not selected," "We will not be moving forward with your application."
@@ -21,12 +22,41 @@ The email does not fit into categories A, B, or C. This includes non-job-applica
 STEP 3: STAR REVIEWED EMAILS
 - For EVERY single email processed and reviewed in this run (Categories A, B, C, and D), apply the Gmail "STARRED" system label or use your email tool to add a star to the message. 
 
-STEP 4: Confirm, via natural language output in the chat window, the total number of emails fetched for review and successfully starred.
+STEP 4: Confirm, via natural language output in the chat window, the total number of emails fetched for review and starred.
 
-STEP 5: SUMMARIZE emails classified as Category B and Category D.
+STEP 5: SUMMARIZE emails classified as Category B and Category D, under separate headers, in the chat.
 For each, state:
 1. Sender name and email address
 2. Email subject line
 3. Date and time received
 4. Category (B or D)
 5. Suggested action I should take
+
+STEP 6: **STRICT COMPLIANCE REQUIRED** **DO NOT FORGET***:
+Summarize all "Category B" emails in the chat. 
+Star all reviewed email
+
+Next,  perform the following actions for each "Category B" email:
+
+STEP 7: CREATE CALENDAR EVENTS
+Immediately after logging to the spreadsheet, check whether ANY of these fields were populated or updated:
+- Recruiter Call Scheduled
+- Company First Interview
+- Company Second Interview
+
+For EACH of the above fields that contains a date/time, create a Google Calendar event using the create_calendar_event tool:
+- Title format: "[<Recruiter Name> Call] Company - Role" or "[First Interview] Company - Role" or "[Second Interview] Company - Role"
+- Start date/time: extracted from the email (convert to ISO 8601)
+- Duration: 30 minutes unless otherwise specified in the email
+- Location: the video meeting link, phone number, or platform name
+- Description: include recruiter or company contact name/email/phone, and note whether they have your cell number
+
+STRICT CONSTRAINTS:
+- Do not make up phone numbers, links, dates, or anything at all. If it does not exist in text within a verifiable email, IT DOES NOT EXIST.
+- PAST-DATE CHECK: Before creating a calendar event: 1) verify today's date from an external, reliable source; 2) compare the proposed meeting date/time against today's date; 3) if the meeting date has already passed, do NOT create a calendar event for it. Still log it to the spreadsheet, but skip the calendar step. The tool will also enforce this server-side.
+- As described in more detail below, each new date/time value in a scheduling column = one new calendar event. Never skip this.
+- Always use the same account for calendar events as was used for email fetching.
+- Do not create duplicate calendar events for the same meeting (same company representative && same job description | same company && same date time)
+- If information is not present in the email, leave that field empty (it's OK!) - do not guess or make up information.
+
+// revised Aug 31

src/prompts/take-action-on-emails.txt

@@ -1,20 +1,7 @@
 PHASE 2: TAKE ACTION ON CATEGORY B EMAILS
 After completing classification (Phase 1), perform the following actions for each email classified as Category B (Advancement to Next Step).
 
-STEP 1: LOG TO SPREADSHEET
-For each Category B email, extract as much of the following information as possible from the email contents and log it using the log_recruiter_contact tool:
-A column exists for:
-- Recruiter Name
-- Recruiter Email
-- Recruiter Phone/Tel
-- Company/Role the recruiter seeks to fill
-- First Contact: the date and time the email was received
-- Subsequent Contacts: any follow-up communication with this recruiter about this role
-- Recruiter Call Scheduled: if the email contains scheduling information, extract ALL details — date, time, platform (Zoom, MS Teams, Google Meet, etc.), meeting link, phone number to call — and note whether they confirm having your cell number or might not have it
-
-If a row already exists for the same recruiter email + company/role combination (from a previous email), the tool will UPDATE the existing row. Provide all available fields and the tool handles merging.
-
-STEP 2: CREATE CALENDAR EVENTS
+STEP 1: CREATE CALENDAR EVENTS
 Immediately after logging to the spreadsheet, check whether ANY of these fields were populated or updated:
 - Recruiter Call Scheduled
 - Company First Interview
@@ -27,12 +14,6 @@ For EACH of the above fields that contains a date/time, create a Google Calendar
 - Location: the video meeting link, phone number, or platform name
 - Description: include recruiter or company contact name/email/phone, and note whether they have your cell number
 
-STEP 3: COMPANY INTERVIEW TRACKING
-When an email indicates advancement beyond the recruiter screen to a company interview:
-- Populate the Company First Interview or Company Second Interview field with details
-- Those details should include company contact info (interviewer name, email, phone)
-- Then immediately create a calendar event for the new interview date/time including interviewer name, email, phone
-
 STRICT CONSTRAINTS:
 - Do not make up phone numbers, links, dates, or anything at all. If it does not exist in text within a verifiable email, IT DOES NOT EXIST.
 - PAST-DATE CHECK: Before creating a calendar event: 1) verify today's date from an external, reliable source; 2) compare the proposed meeting date/time against today's date; 3) if the meeting date has already passed, do NOT create a calendar event for it. Still log it to the spreadsheet, but skip the calendar step. The tool will also enforce this server-side.
@@ -40,3 +21,5 @@ STRICT CONSTRAINTS:
 - Always use the same account for calendar events as was used for email fetching.
 - Do not create duplicate calendar events for the same meeting (same company representative && same job description | same company && same date time)
 - If information is not present in the email, leave that field empty (it's OK!) - do not guess or make up information.
+
+// revised Aug 31

src/tools/tools-calendar.ts

@@ -109,3 +109,5 @@ server.registerTool(
     }
   }
 );
+
+// revised Aug 31

src/tools/tools-email.ts

@@ -358,3 +358,5 @@ server.registerTool(
         }
     }
 );
+
+// revised Aug 31

src/tools/tools-spreadsheet.ts

@@ -177,3 +177,5 @@ server.registerTool(
     }
   }
 );
+
+// revised Aug 31

test/fixtures/mock-emails.ts

@@ -165,3 +165,5 @@ export const RAW_BODIES = {
   "msg-cat-c-001": catCBody,
   "msg-cat-d-001": catDBody,
 };
+
+// revised Aug 31

test/integration/email-workflow.test.ts

@@ -285,3 +285,5 @@ describe("Phase 1: Email Review Workflow", () => {
     });
   });
 });
+
+// revised Aug 31

test/unit/email-parsing.test.ts

@@ -84,3 +84,5 @@ describe("decodeBody", () => {
     expect(decodeBody(msg)).toBe(htmlContent);
   });
 });
+
+// revised Aug 31

tsconfig.json

@@ -10,6 +10,12 @@
         "skipLibCheck": true,
         "forceConsistentCasingInFileNames": true
     },
-  "include": ["src/**/*"],
-  "exclude": ["node_modules", "test", "vitest.config.ts"]
+    "include": [
+        "src/**/*"
+    ],
+    "exclude": [
+        "node_modules",
+        "test",
+        "vitest.config.ts"
+    ]
 }

vitest.config.ts

@@ -6,3 +6,5 @@ export default defineConfig({
     globals: true,
   },
 });
+
+// revised Aug 31