What shipped

This correction completes the July 30 release record. The earlier entries about application-status reconstruction and the connected CuriousCirkits workspace remain unchanged; this record adds five other production-verified improvements that were omitted from the original summary.

• Career materials now use structured résumé and cover-letter data, with user-supplied external links supported when a reference is needed. CuriousCirkits no longer generates, uploads, previews, downloads, or manages PDF and Word files. This keeps the authoritative content inspectable, avoids competing file copies, and still supports recording an application from structured data or an external material link.
• Verified jobs now connect to the correct canonical Company record when there is one unambiguous exact name or trusted alias match. Users can also supply the intended Company explicitly. Ambiguous or inaccessible matches stop safely instead of creating a false relationship, and repeating the same completed request does not create another link.
• Company intelligence is more reliable through the connected experience. Saved monitoring sources now return consistently, including a clear empty result when none exist. Intelligence-profile writes now distinguish complete success, safe replay, partial completion, and failure, so previously committed Company or relationship work is not hidden or falsely rolled back.
• The CuriousCirkits connection now exposes a smaller, more intentional capability set across Goals, Contacts, Companies, Jobs and Applications, Résumés, and Cover Letters. Redundant legacy operations were retired while distinct safety steps—such as preview and commit, submission, lifecycle changes, merging, and deletion—remain separate. Existing records, receipts, and tenant boundaries were preserved.
• Private Career records now have stronger layered access protection, and releases include an automated security check that blocks unexpected weakening of those safeguards. The release also tightened privileged access paths and verified that supported Goals, Contacts, Companies, and Jobs workflows continued to work after the change.

Application views can now be rebuilt from authoritative history and compared with stored summaries before a correction is made. This helps CuriousCirkits detect stale or inconsistent status information without rewriting the underlying journey or hiding unresolved evidence conflicts.

• Application status summaries are reconstructed consistently from preserved lifecycle history and evidence.
• Stale derived views and factual conflicts are distinguished instead of being treated as the same problem.
• Safe corrections reject stale or conflicting changes while preserving the original history.

Goals, Contacts, Companies, Jobs, Résumés, Cover Letters, and Workout now open through one canonical CuriousCirkits workspace while familiar module links remain usable. This reduces inconsistent behavior across product areas and gives each area a clearer, more resilient path.

• Existing module addresses now open the matching area in the main CuriousCirkits workspace.
• Supported record links continue to reach the intended detail view.
• Retired data and connection paths return clear guidance to the current application and connection.
• An issue in one product area is less likely to prevent unrelated areas from loading.

The existing /api/mcp endpoint now publishes a non-null contract and schema version, exact outputs for Contact, application-material, cover-letter, and résumé reads and exports, stable typed missing-record errors, per-tool capability and compatibility metadata, and a retained release artifact that blocks schema drift. Every successful tool response also includes a canonical CuriousCirkits permalink generated from one validated provider-level app origin, so administrators can change the application domain without changing individual tools or records.

• Canonical responses now carry stable contracts and direct links back to the relevant CuriousCirkits record.

Contacts now distinguish a person’s identity from their relationship to a company or opportunity. This keeps useful relationship history while preventing uncertain or conflicting evidence from becoming a confident fact.

• Relationship labels now communicate whether a role is verified, user supplied, inferred, unresolved, or conflicting.
• Updates can close or supersede an earlier relationship without deleting its history.
• Conflicting company or role evidence stops the entire save before a false relationship is created.
• Repeated requests return the original result instead of creating duplicate active relationships.

Contact saves, bulk saves, links, and lifecycle writes now compare verified employer and role evidence with the selected company or opportunity before commit. Contradictions return a typed identity conflict and atomically preserve the prior Career graph.

• Conflicting identity evidence stops the change and preserves the existing relationship history.

CuriousCirkits can now preserve an ordered set of next actions when a conversation moves across contacts, companies, goals, and jobs.

• The first recommendation in a new workspace can be saved and read back reliably.
• Natural cross-app requests reuse existing records and connect relevant work to the right goal.
• Retries do not duplicate recommendations or relationships.
• Draft outreach remains a draft until the user explicitly approves sending it.

Contact relationships now expose stable current and historical state, support previewed create, update, close, and supersede operations, and reject stale versions, cross-tenant targets, overlapping validity windows, and conflicting retries without partial writes.

• Relationship changes retain history and reject unsafe or conflicting updates without partial writes.

Completed actions can now return a direct link to the relevant CuriousCirkits record or workspace, making it easier to move from a conversation into the product.

• Supported results link to the relevant goal, contact, company, job, résumé, or workspace.
• Response structures are versioned so clients and skills can detect incompatible changes safely.
• Missing records and failed actions return clear non-success results instead of ambiguous output.

Contact confidence now accepts either percentage points or model-friendly fractions without dropping verification or provenance. Recommendation modules are normalized to stable slugs, and constraint failures return the exact invalid field instead of being mislabeled as identifier or lifecycle errors.

• Proactive actions preserve verification context and return clearer correction guidance when an input is invalid.

Product feedback now preserves useful diagnostics while keeping tenant identity and private product data out of provider-facing views.

• Names, contact details, private records, tenant identifiers, and private links are removed at the feedback boundary.
• Safe diagnostic details such as timing, error type, retryability, and committed state remain available for investigation.
• A feedback submission returns a durable receipt so the user can tell whether it was recorded.

jobs_set_next_action now requires a caller-controlled clientRequestId. Identical retries return the original committed result without a duplicate update, while changed payloads using the same request ID fail closed.

• Repeated next-action requests return the original result instead of creating duplicate changes.

Application submissions, confirmations, employer responses, evidence, and current state now come from one connected lifecycle instead of competing fields.

• A submission updates the timeline, evidence, and current application state together.
• Later employer responses retain the earlier submission and confirmation history.
• Repeated evidence does not create duplicate events.
• Contradictory legacy information is shown as requiring review instead of being simplified to Not Applied.

Preparation items, interview questions, demos, and networking targets can now be linked to one exact tracked opportunity. Resource writes validate each kind, preserve partial-update semantics, return durable replay receipts, and expose typed non-commit errors for invalid references or payloads.

• Preparation work can stay connected to the exact opportunity it supports.

Submitted feedback now enters a durable, privacy-aware triage flow and remains connected to the product work that owns the underlying improvement.

• Each report remains individually traceable even when several reports share one underlying problem.
• Retries do not create duplicate tracking records.
• A report is closed only after the original behavior is verified in production.
• The full history is retained when feedback is triaged, resolved, closed, or reopened.

Application submissions, timeline events, linked evidence, opportunity projections, and replay-safe receipts now commit as one transaction. Ordered lifecycle reads include deterministic projection versions, while contradictory legacy history remains preserved as an explicit conflict.

• Submission history, evidence, and current application state now change together as one consistent lifecycle.

Fresh connections, reconnects, and longer multi-step workflows are more dependable, with clearer recovery when an authorization or service interruption occurs.

• A new ChatGPT connection can complete authorization and load the current CuriousCirkits capabilities.
• A failure in one action no longer makes unrelated capabilities disappear.
• Interrupted workflows can identify what committed and resume only the unfinished work.
• Authentication problems return a clear reauthorization path.

Actions that change data now follow one consistent success, failure, and retry contract across CuriousCirkits.

• Success is reported only after the change is committed.
• Failures identify what needs correction without exposing private system details.
• Repeating the same request returns the original committed result.
• Reusing a request for different data is stopped as a conflict without changing the saved record.

Fresh connections now discover the current supported CuriousCirkits actions without duplicate legacy operations or provider-only capabilities.

• The connected catalog and the published platform catalog now follow the same supported contract.
• Older duplicate résumé actions were retired in favor of the canonical résumé workflow.
• Unauthorized and provider-only actions remain hidden from normal user connections.

Consolidated MCP and OAuth on the Developers Site at the canonical endpoint. Retired both legacy MCP URLs and removed refresh-token and OpenID behavior from the recovery contract.

• Connections now use one supported endpoint with a clearer recovery path.

Published the live tools and workflows across five focused apps and shared platform services. Added standalone Companies and Goals tools, independent Resume scopes, and a machine-readable catalog. The provider admin and this portal now consume that contract instead of copied counts.

• The connected capability catalog, provider admin, and developer portal now share one live source.