@access-mcp/announcements 0.3.0 → 0.3.1

package/dist/server.d.ts

@@ -9,6 +9,10 @@ export declare class AnnouncementsServer extends BaseAccessServer {
     /**
      * Get or create the Drupal auth provider for JSON:API write operations.
      * Requires DRUPAL_API_URL, DRUPAL_USERNAME, and DRUPAL_PASSWORD env vars.
+     *
+     * Acting user is determined in priority order:
+     * 1. X-Acting-User header (from request context)
+     * 2. ACTING_USER environment variable (fallback)
      */
     private getDrupalAuth;
     protected getTools(): Tool[];
@@ -28,12 +32,20 @@ export declare class AnnouncementsServer extends BaseAccessServer {
     private enhanceAnnouncements;
     private searchAnnouncements;
     /**
-     * Get the acting user's UID from environment variable.
-     * This identifies who the announcement should be attributed to.
+     * Get the acting user's ACCESS ID for content attribution.
+     *
+     * Priority order:
+     * 1. X-Acting-User header (from request context)
+     * 2. ACTING_USER environment variable (fallback)
+     *
+     * Returns the ACCESS ID (e.g., "username@access-ci.org")
      */
-    private getActingUserUid;
+    private getActingUserAccessId;
     /**
      * Create a new announcement via Drupal JSON:API
+     *
+     * The X-Acting-User header (set by DrupalAuthProvider) tells Drupal which
+     * ACCESS user is creating the content. Drupal handles user resolution.
      */
     private createAnnouncement;
     /**
@@ -49,9 +61,11 @@ export declare class AnnouncementsServer extends BaseAccessServer {
      */
     private getMyAnnouncements;
     /**
-     * Get a user's UUID by their Drupal user ID (internal helper)
+     * Get a user's UUID by their ACCESS ID (e.g., "user@access-ci.org").
+     *
+     * The Drupal username should match the full ACCESS ID.
      */
-    private getUserUuidByUid;
+    private getUserUuidByAccessId;
     /**
      * Get announcement context - tags, affinity groups, and options for creating announcements
      */