Resolve lab cancellations, moved sessions and conflicting evidence

Open
  • Is something wrong?
#33 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js
Domain
backend-api-design

Research direction

Read the forum evidence model, occurrence resolver, and src/labs.js, along with AGENTS.md and docs/PROJECT_CONTEXT.md. First review dependencies #29 and #32 and discuss the authority and applicability design with the maintainer before implementation. Done means the listed evidence cases are covered, partial evidence never confirms an absence, moved sessions retain stable identities, and the required checks are reported.

Written by the indexing model from the issue text.

Description

area:backend area:docs priority:high status:blocked type:feature

Part of #28 · Target: Scheduling / v0.5

Goal and scope

Apply explicitly dated/group-scoped cancellation or move evidence to occurrences. Preserve original and replacement references, publication/effective dates and unresolved conflicts. Establish authority/applicability rules with a reviewed design.

Implementation starting points

forum evidence model, occurrence resolver, src/labs.js. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Depends on #29, #32. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No interpreting unrelated announcements as cancellation, silent evidence precedence or notifications.

Acceptance criteria and test plan

Tests cover one-group cancellation, moved room/day/time, superseded timetable, unrelated post, conflicting updates and failed announcement refresh. Partial evidence never becomes confirmed absence; stable identities avoid duplicated moved sessions.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
1h 25m
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mahmutmft/courses-mcp

All issues in mahmutmft/courses-mcp

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.