qiksy 1.3.0 → 1.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qiksy",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "description": "Qiksy \u2014 one local engine for every Qiksy tool (Work Finder, Travel Assistant, Client Finder). Runs on your own Claude; nothing leaves your machine.",
   "type": "module",
   "bin": {

package/tools/work-finder/vendor/lib/prompts.mjs

@@ -54,7 +54,16 @@ export function searchPrompt(position, profile, excludeCompanies, settings, pass
 POSITION: ${position.title}
 KEYWORDS / STACK: ${position.keywords || '—'}
 ENGAGEMENT: ${ENGAGEMENT_TEXT[position.engagement] || ENGAGEMENT_TEXT.both}
-CANDIDATE LOCATION: ${profile?.location || 'Ukraine'} — works remotely from there (or B2B contract)
+CANDIDATE LOCATION: ${profile?.location || 'Ukraine'}
+WHERE THEY CAN WORK: ${
+  settings.workMode === 'onsite'
+    ? `ON SITE, in or near ${profile?.location || 'Ukraine'}. Look for office roles there — commuting distance, not another country. A remote-only posting is NOT a match unless it also offers an office in that area.`
+    : settings.workMode === 'hybrid'
+      ? `HYBRID — an office in or near ${profile?.location || 'Ukraine'} with some days from home. Fully remote is acceptable only if the company also has an office there.`
+      : settings.workMode === 'any'
+        ? `EITHER — remote from ${profile?.location || 'Ukraine'} (or B2B contract), or an office role in or near ${profile?.location || 'Ukraine'}. Both count; say which one each posting is.`
+        : `REMOTELY from ${profile?.location || 'Ukraine'} (or B2B contract).`
+}
 ${settings.searchExtra ? `EXTRA INSTRUCTIONS FROM USER: ${settings.searchExtra}\n` : ''}
 CANDIDATE (for relevance filtering):
 ${resumeExcerpt(profile, 1200)}
@@ -78,11 +87,12 @@ RULES:
 - Skip these companies (already found earlier): ${excludeCompanies.length ? excludeCompanies.join(', ') : 'none'}.
 - Find AT LEAST ${n} distinct openings at distinct companies — more is better. There is no upper limit: return every match you can confirm in this pass.
 - SCORE THE FIT: for every vacancy set "match" to an INTEGER 0-100 — how well THIS role fits the candidate above (stack & seniority overlap, remote eligibility from ${profile?.location || 'Ukraine'}, engagement type). Be honest and discriminating: reserve 90+ for a strong direct match, 60-75 for a plausible partial fit, below 50 for a stretch. The "notes" field should justify the number in one line.
+- FIRST FIVE, ONE AT A TIME. Do not gather a batch before reporting. Take the first promising link, WebFetch it, and the MOMENT it checks out print its VACANCY line — before you open the next one. Repeat until five are out. Only after that may you work in parallel and report in groups. The person is watching an empty screen until the first line appears, and five minutes of nothing reads as broken (measured 2026-07-26: first results at ~7 min).
 - WORK FAST but do not stop early: broad WebSearch queries first, then WebFetch the promising pages. Streaming a confirmed find costs nothing extra, so stream as you go.
 - TIME BUDGET: up to ~12 minutes for this pass. Stop when you genuinely run out of NEW companies, not when you reach a number.
 ${wave > 1 ? `- THIS IS SWEEP #${wave}. Everything the earlier sweeps found is in the exclusion list above and must not come back. Asking the same question again returns the same answers, so change the ANGLE: different search phrasings and role synonyms, different ATS hosts, different regions and countries, smaller and less-known companies, older-but-still-open postings, adjacent titles the candidate also fits. If a whole angle turns up nothing new, say so and finish the pass — an honest empty sweep ends the search cleanly.` : ''}
 
-PROGRESS STREAMING: the user watches results arrive live. As soon as you have CONFIRMED one vacancy (page fetched, fresh, geography checked), immediately print a single line:
+PROGRESS STREAMING — THIS IS NOT OPTIONAL AND NOT A SUMMARY STEP: the user is watching a live screen and sees nothing until you print. Never hold findings back to report them together at the end; a vacancy you confirmed but have not printed is invisible to them. As soon as you have CONFIRMED one vacancy (page fetched, fresh, geography checked), immediately print a single line:
 VACANCY: {"company":...}   ← one-line JSON, exact same fields as the array items below
 …then continue searching. Stream every confirmed finding this way.
 

package/tools/work-finder/vendor/lib/store.mjs

@@ -22,6 +22,11 @@ function defaults() {
       model: 'sonnet',
       autoSubmit: false,
       searchViaBrowser: false,
+      /* Where the person can actually work: 'remote' (default, what the agent always
+         silently assumed) | 'onsite' | 'hybrid' | 'any'. Not everyone can work from
+         home — some need an office in their own city, and until now the product had
+         nothing to offer them (owner, 2026-07-26). */
+      workMode: 'remote',
       searchExtra: '',
       /* Per SWEEP, and a FLOOR, not a ceiling — the search runs sweep after sweep
          until one turns up nothing new (server.mjs startSearch). It used to be a