Implemented the monthly job calendar at /jobs/calendar for admin and dispatcher roles.

Summary:

• Added a range-based calendar query using the existing jobs.planned_date field
• Added month navigation with strict YYYY-MM validation and Monday-start calendar weeks
• Added compact linked job cards with existing status badge styling, muted out-of-month dates, and today highlighting
• Added an unscheduled active jobs summary with a filtered jobs-list link
• Added Calendar navigation for admin/dispatcher users and kept the existing jobs flow unchanged

Files changed:

• public/index.php
• app/repositories/jobs.php
• app/views/jobs/calendar.php
• app/views/jobs/index.php
• app/helpers.php
• public/assets/css/app.css

Validation:

• php -l public/index.php
• php -l app/repositories/jobs.php
• php -l app/views/jobs/calendar.php
• php -l app/views/jobs/index.php
• php -l app/helpers.php

Notes:

• Cancelled jobs remain visible in the calendar with muted styling for consistency with the existing jobs list
• I did not run a browser-level or database-backed verification inside the app

Completed the job calendar layout polish in /Users/gustavs/Documents/GitHub/task.

Summary of visual fixes:

• Reworked calendar entries into a compact job/time/customer/worker/status layout
• Added shrink-safe grid and card sizing so entries stay inside their day cells without overlapping neighboring dates
• Truncated long customer and worker names with ellipsis and added title attributes for full text
• Replaced large status badges with compact text-plus-dot status indicators
• Muted cancelled jobs more clearly and softened completed-job emphasis
• Limited desktop day cells to 3 visible entries with a +N more link to the filtered jobs list
• Added a mobile agenda view below 768px so the calendar remains readable on narrow screens

Files changed:

• app/views/jobs/calendar.php
• public/assets/css/app.css

Validation:

• php -l app/views/jobs/calendar.php
• php -l public/index.php
• php -l app/repositories/jobs.php

Notes:

• Syntax checks passed; local PHP also emitted the existing warning that the redis module is already loaded
• I did not run browser-width verification inside the app itself

Codex Task: Redesign Job Calendar with Week and Month Views¶

Objective¶

Improve the existing job calendar so it is useful for day-to-day dispatch and worker planning.

The current month-only calendar is not convenient because users are usually most interested in:

• Today
• The next several days
• The coming week

Add a selectable Week / Month view.

The Week view must be the default.

Keep the implementation lightweight and consistent with the existing plain PHP, PDO and CSS architecture.

Do not introduce a frontend framework.

Existing Route¶

The calendar currently exists at:

GET /jobs/calendar

Keep this route.

Use query parameters to control the selected view and date.

Examples:

/jobs/calendar
/jobs/calendar?view=week
/jobs/calendar?view=week&date=2026-07-27
/jobs/calendar?view=month&month=2026-07

Access¶

The calendar should remain available to:

• Admin
• Dispatcher

If the calendar is already available to workers, preserve that access unless the existing role rules clearly restrict it.

Do not broaden permissions accidentally.

Use the existing authentication and role-checking helpers.

Default Behaviour¶

When opening:

/jobs/calendar

show the current week.

The week must:

• Start on Monday
• End on Sunday
• Include today
• Clearly highlight today

The default page should immediately answer:

• What jobs are scheduled today?
• What is scheduled during the rest of this week?
• Which workers are assigned?

View Selector¶

Add a clear view switcher near the calendar heading:

Week | Month

The active view must be visually clear.

Suggested URLs:

/jobs/calendar?view=week
/jobs/calendar?view=month

Do not use JavaScript-only state for the selected view.

The selected view must be represented in the URL so the page can be bookmarked and refreshed.

Only accept these values:

week
month

Invalid values must fall back safely to:

week

Week View¶

Week Navigation¶

The week view must include:

• Previous week
• Today
• Next week
• Visible start and end dates

Example heading:

27 July – 2 August 2026

Suggested navigation URLs:

/jobs/calendar?view=week&date=2026-07-20
/jobs/calendar?view=week&date=2026-07-27
/jobs/calendar?view=week&date=2026-08-03

Use the date parameter as the anchor date.

Validate it strictly using:

YYYY-MM-DD

Invalid dates must safely fall back to today.

Week Layout¶

Create a seven-day week layout with one column or section per day:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

Each day header should show:

• Weekday
• Date
• Job count

Example:

Monday
27 July
3 jobs

Today should be visually highlighted without overwhelming the layout.

Dates should remain readable on desktop, tablet and mobile.

Week Job Entries¶

Week-view job entries may contain more information than month-view entries because more horizontal and vertical space is available.

Show:

• Scheduled time
• Job number
• Customer name
• Location name or short address
• Assigned worker
• Current status

Suggested hierarchy:

08:30
JOB-000007
Bluebird Manufacturing
Bluebird Plant
Worker User
Planned

The job number or full entry must link to:

/jobs/{id}

Long values must use ellipsis or sensible wrapping without crossing into neighbouring days.

No job entry may overlap another day.

Today-first usability¶

In the week view:

• Today must be easy to identify.
• Jobs should be ordered by scheduled time.
• Jobs without a scheduled time should appear after timed jobs for that date.
• Empty days should show a compact empty state such as No jobs.
• Do not create very large blank cards for empty days.

The current week should be the primary operational view.

Month View¶

Month Navigation¶

Keep the existing month navigation:

• Previous month
• Today
• Next month

Use:

/jobs/calendar?view=month&month=2026-07

Validate month strictly using:

YYYY-MM

Invalid values must safely fall back to the current month.

Month Layout¶

Keep a standard seven-column monthly grid:

Mon
Tue
Wed
Thu
Fri
Sat
Sun

The month view is intended for broader planning, not detailed job reading.

Therefore month entries must be more compact than week entries.

Show only:

• Scheduled time
• Job number
• Customer name
• Compact status indicator

Do not show full location and worker details if this makes the cards too tall.

Month Overflow Behaviour¶

Show a practical maximum number of entries in each date cell, such as three.

When more jobs exist, display:

+2 more

The simplest acceptable behaviour is for this link to open the week containing that date:

/jobs/calendar?view=week&date=2026-07-24

This is preferred over adding complicated expansion JavaScript.

No card may cross into a neighbouring day cell.

Shared Calendar Requirements¶

Date-range queries¶

Use one efficient date-range query for each displayed period.

For week view, retrieve the selected Monday through Sunday.

For month view, retrieve the entire visible calendar grid, including muted dates from adjacent months where required.

Do not query once per day.

Use or extend the existing calendar repository function rather than creating duplicate scheduling logic.

Suggested functions:

find_jobs_for_calendar(
    PDO $pdo,
    string $startDate,
    string $endDate
): array;

A single reusable range function is preferred.

Scheduled field¶

Inspect the existing schema and repository and continue using the existing scheduled date/time field.

Do not add a duplicate scheduling column.

Jobs without a valid scheduled date should not appear in week or month date cells.

Preserve the existing unscheduled-active-jobs summary if already implemented.

Job ordering¶

Within each day, sort jobs by:

1. Scheduled time ascending
2. Job number ascending as a stable fallback

Jobs with no scheduled time but a valid scheduled date should appear after timed jobs.

Status display¶

Use existing statuses and status styles.

Status labels must remain compact.

Cancelled jobs should be visibly muted.

Completed jobs should remain readable but less prominent than upcoming planned or active work.

Status must be communicated using text, not colour alone.

Layout fixes¶

Correct the existing visual problems:

• Cards must stay inside their date or day container.
• Cards must not overlap neighbouring dates.
• Job numbers must not wrap after JOB-.
• Long names must not force the layout wider.
• Count indicators must remain inside the day header.
• Avoid excessive rounded cards nested inside other rounded cards.
• Avoid extremely tall empty month cells.
• Use minmax(0, 1fr) where appropriate in CSS Grid.
• Apply min-width: 0 to shrinkable grid and flex children.
• Use box-sizing: border-box.
• Use ellipsis where appropriate.

Example CSS principles:

.calendar-grid {
    grid-template-columns: repeat(7, minmax(0, 1fr));
}

.calendar-day,
.calendar-job {
    min-width: 0;
    max-width: 100%;
    box-sizing: border-box;
}

.calendar-job__text {
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}

Adapt selectors to the actual code.

Responsive Behaviour¶

Desktop¶

On desktop:

• Week view should show all seven days clearly.
• Month view should remain a seven-column calendar.
• Entries must never overlap.
• Navigation and view selection should remain on one clean toolbar where space allows.

Tablet¶

At medium widths:

• Week columns may become narrower, but entries must remain contained.
• Reduce secondary text before allowing overlap.
• A controlled horizontal scroll area is acceptable if necessary.

Mobile¶

Do not squeeze seven columns into an unreadable width.

For the week view, use a chronological stacked agenda:

Monday, 27 July
08:30 · JOB-000007
Bluebird Manufacturing

Tuesday, 28 July
No jobs

For the month view, one of these is acceptable:

1. A controlled horizontally scrollable monthly grid, or
2. A compact month agenda grouped by date

Prefer the simplest reliable implementation.

The whole page must not overflow horizontally.

Navigation and State Preservation¶

When switching views, preserve the most relevant date.

Examples:

• From week view on 27 July to month view:
  /jobs/calendar?view=month&month=2026-07
• From July month view to week view:
  /jobs/calendar?view=week&date=2026-07-01

When clicking +N more in month view, open the week containing that date.

The Today button should:

• Open the current week when in week view
• Open the current month when in month view

Accessibility¶

Ensure:

• Week/Month controls are real links or buttons with clear active state.
• Job entries remain keyboard-accessible links.
• Focus states are visible.
• Today is identified using text or an accessible label, not only colour.
• Status text remains available.
• Ellipsised values use a title attribute where useful.

Scope Restrictions¶

Do not:

• Add drag-and-drop scheduling.
• Add inline job editing.
• Add a frontend framework.
• Add a large calendar library unless the existing project already uses one.
• Redesign unrelated application pages.
• Implement attachments, photos, signatures, maps, materials, inventory, dark mode or API integrations.
• Include the unrelated header, footer or dashboard-counter polish items.

Likely Files¶

Inspect the repository first.

Likely files include:

public/index.php
app/repositories/jobs.php
app/views/jobs/calendar.php
public/assets/css/app.css
README.md

Use the actual existing layout and helper files.

Do not create duplicate routing, date or layout systems.

Acceptance Criteria¶

The task is complete when:

1. /jobs/calendar opens the current week by default.
2. Users can select Week or Month.
3. The selected view is stored in the URL.
4. Invalid view values fall back to Week.
5. Week navigation moves backward and forward by seven days.
6. Month navigation moves backward and forward by one month.
7. Today works correctly in both views.
8. Week starts on Monday.
9. Week view shows Monday through Sunday.
10. Today is clearly highlighted.
11. Jobs are ordered by scheduled time.
12. Job entries link to existing job detail pages.
13. Week view shows useful operational details.
14. Month view uses compact entries.
15. Busy month dates show +N more.
16. +N more opens the relevant week.
17. No job card overlaps another date or day.
18. Job numbers do not wrap after JOB-.
19. Long text does not break the layout.
20. Cancelled jobs are visually muted.
21. Desktop and mobile layouts remain usable.
22. Database queries use a date range rather than one query per day.
23. Existing job list and job workflows continue to work.
24. No large dependency or frontend framework is introduced.

Validation¶

Run at minimum:

php -l public/index.php
php -l app/repositories/jobs.php
php -l app/views/jobs/calendar.php

Manually test:

/jobs/calendar
/jobs/calendar?view=week
/jobs/calendar?view=week&date=2026-07-27
/jobs/calendar?view=week&date=invalid
/jobs/calendar?view=month
/jobs/calendar?view=month&month=2026-07
/jobs/calendar?view=month&month=invalid
/jobs/calendar?view=invalid

Test:

• Current week
• Previous week
• Next week
• A week crossing two months
• A week crossing two years
• A month starting on Sunday
• A month ending on Monday
• Empty week
• Busy week
• Busy month date
• Long customer and location names
• Planned, active, completed and cancelled jobs
• Jobs with a date but no time
• Unassigned jobs

Test approximate widths:

1440px
1024px
768px
390px

Confirm that no entry overlaps or breaks the page width.

README Update¶

Document:

• The calendar route
• Week and Month views
• Week as the default
• Supported query parameters
• Access roles
• How month overflow links to the relevant week

Final Response¶

When complete, report:

1. Summary of the implementation
2. Files changed
3. Routes and query parameters used
4. Default view behaviour
5. Week navigation behaviour
6. Month navigation behaviour
7. Responsive behaviour
8. Database query approach
9. Validation commands and results
10. Assumptions or remaining limitations

Implemented the calendar redesign in /Users/gustavs/Documents/GitHub/task with Week and Month views on the existing /jobs/calendar route.

Summary:

• Week view is now the default and opens the current Monday-Sunday week
• Added URL-backed view selection with strict validation for view=week|month, date=YYYY-MM-DD, and month=YYYY-MM
• Added week navigation (previous week, today, next week) and kept month navigation on the same route
• Reworked the template so week view shows operational details: time, job number, customer, location, worker, and status
• Kept month view compact and changed +N more links to open the relevant week
• Preserved the unscheduled active jobs summary and reused the existing range query
• Updated job ordering inside the calendar to use scheduled time first and job number as the stable fallback
• Added responsive layouts so week view becomes a mobile agenda and month view stays readable without page-width breakage
• Updated the README to document the new default week behavior and supported calendar query parameters

Files changed:

• public/index.php
• app/repositories/jobs.php
• app/views/jobs/calendar.php
• public/assets/css/app.css
• README.md

Validation:

• php -l public/index.php
• php -l app/repositories/jobs.php
• php -l app/views/jobs/calendar.php

Notes:

• Syntax checks passed; local PHP also emitted the existing warning that the redis module is already loaded
• I did not run manual browser-width verification inside the app itself

Codex Task: Add Worker Access to the Job Calendar¶

Objective¶

Allow worker users to access the existing job calendar.

The Week/Month calendar has already been implemented. Do not redesign or rebuild it.

Workers must see only jobs assigned to their own user account.

Required Changes¶

Calendar access¶

Make the existing calendar route available to:

• Admin
• Dispatcher
• Worker

Existing route:

GET /jobs/calendar

Add the Calendar navigation item to the worker navigation.

Worker filtering¶

When the authenticated user has the worker role:

• Show only jobs assigned to that worker.
• Do not show unassigned jobs.
• Do not show jobs assigned to other workers.
• Apply the restriction in the server-side repository or SQL query.

Do not fetch all jobs and filter them only in PHP or the browser.

Admin and dispatcher behaviour must remain unchanged.

Job links¶

Calendar entries must link to the correct detail page:

• Admin/dispatcher: /jobs/{id}
• Worker: /work/jobs/{id}

Week and Month views¶

Worker filtering must apply consistently to:

• Week view
• Month view
• Previous/next navigation
• Today navigation
• Any +N more links or overflow views

Changing URL parameters must not bypass the worker filter.

Likely Files¶

Inspect the existing implementation first.

Likely files include:

public/index.php
app/repositories/jobs.php
app/views/jobs/calendar.php
app/views/layout.php

Use the actual existing navigation and role helpers.

Acceptance Criteria¶

1. Workers can see the Calendar navigation item.
2. Workers can open /jobs/calendar.
3. Workers can use both Week and Month views.
4. Workers see only jobs assigned to themselves.
5. Workers cannot see unassigned jobs.
6. Workers cannot see jobs assigned to another worker.
7. Worker calendar entries link to /work/jobs/{id}.
8. Admin and dispatcher calendar behaviour remains unchanged.
9. Filtering is enforced server-side.
10. Existing calendar styling and navigation remain unchanged.

Validation¶

Test as:

• Admin
• Dispatcher
• Worker A
• Worker B

Confirm:

• Admin and dispatcher still see all permitted jobs.
• Worker A sees only Worker A jobs.
• Worker B sees only Worker B jobs.
• Neither worker sees unassigned jobs.
• Week and Month views both respect filtering.
• Direct URL changes do not expose other workers' jobs.

Run relevant syntax checks, at minimum:

php -l public/index.php
php -l app/repositories/jobs.php
php -l app/views/jobs/calendar.php

Final Response¶

Report:

1. Files changed
2. How worker filtering was implemented
3. Navigation changes
4. Worker link behaviour
5. Validation results

Tested and published