// ============================================================
// Two cross-job takes on Action needed.
//
// Both exist because of one finding in the call corpus: the attention
// problem often isn't *inside* the panel — it's that the recruiter isn't in
// the panel at all. Steris, unprompted:
//
// "We'll have it open as one of the tabs, and we're going back and forth…
// we have our ATS, we have Indeed… it just keeps me lost. [A candidate]
// will reply back to me and I get the email — but if I don't look, it
// might be two hours."
//
// Reorganising one job's candidate list does nothing for that. Both layouts
// below attack the cross-job version of the problem instead.
//
// LayoutAllJobs (#all-jobs) — one queue spanning every job
// LayoutActivity (#activity) — today's activity feed, made robust
//
// Both reuse atTrigger() so the ladder stays single-sourced.
// ============================================================
const { color: XJ } = window.FF;
const xjJob = (id) => (window.__JOBS__ || []).find(j => j.id === id) || { title:'—' };
const xjShort = (t) => (t.length > 26 ? t.slice(0, 25) + '…' : t);
const xjInit = (n) => n.split(' ').map(s => s[0]).slice(0, 2).join('');
const xjSorted = (list) => list
.map(c => ({ c, t: atTrigger(c) })).filter(x => x.t)
.sort((a, b) => a.t.rank - b.t.rank || a.t.sort - b.t.sort || (b.c.score || 0) - (a.c.score || 0));
/* ============================================================
ALL JOBS — a full-width takeover, NOT a candidates-panel layout.
The candidates panel is scoped to whatever job is selected in the rail, so
a cross-job list can't live there without contradicting the shell: you'd be
looking at another req's candidates under this req's header. Production
already has the right precedent — Candidate Archive is a nav-level view
where "candidates aren't scoped to a specific job".
So this replaces panels 2+3 entirely. Entered from the aggregate row at the
top of the jobs rail, exited back to where you were.
Distinct from #activity on purpose: the feed is an inbox you check and
leave, this is a working surface you sit and grind through — job is a
column, rows are wider, wait-age is explicit.
============================================================ */
function LayoutAllJobsTakeover({ candidates, onExit }) {
const [jobFilter, setJobFilter] = React.useState('all');
const [done, setDone] = React.useState({});
const all = xjSorted(candidates).filter(x => !done[x.c.id]);
const items = jobFilter === 'all' ? all : all.filter(x => x.c.jobId === jobFilter);
const byJob = {};
all.forEach(x => { byJob[x.c.jobId] = (byJob[x.c.jobId] || 0) + 1; });
const age = (t) => {
const h = Math.abs(Math.round(t.sort));
return t.rank === 4 ? `${h}d` : h ? `${h}h` : 'now';
};
return (
{/* Header */}
Needs you
{all.length}
Every job, most urgent first. Work top to bottom — this is the whole list.
);
}
/* ============================================================
ACTIVITY — today's feed, made robust.
Today it's one row per unread candidate conversation, newest first.
That only ever surfaces ONE trigger type (a candidate messaged you) and
only clears by reading. Two consequences: the scheduling failure, the
finished screening and the going-stale candidate never appear at all; and
"read" is not the same as "handled", so the badge lies.
This version keeps the shape recruiters already know — bell, count, panel,
Mark all as read — and widens the contract from "unread messages" to
"unhandled work", bucketed by what's being asked of you.
============================================================ */
const XJ_BUCKETS = [
{ cats:['Waiting on us'], label:'Replies waiting on you' },
{ cats:['Needs your help','Decision needed'], label:'Needs a decision or a hand' },
{ cats:['New application','Screened'], label:'Ready for review' },
{ cats:['Stale'], label:'Going cold' },
];
function LayoutActivity({ candidates, selectedId, onSelect }) {
const [read, setRead] = React.useState({});
const all = xjSorted(candidates).filter(x => !read[x.c.id]);
const open = XJ_BUCKETS.map(b => ({ ...b, items: all.filter(x => b.cats.includes(x.t.cat)) })).filter(b => b.items.length);
return (
Activity
{all.length}
{open.map(b => (
{b.label} {b.items.length}
{b.items.map(({ c, t }) => {
const on = c.id === selectedId;
return (