fix: 포트 충돌 회피 — note_bridge 8098, intent_service 8099

Jellyfin(8096), OrbStack(8097) 포트 충돌으로 변경.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/INSTALLER

@@ -0,0 +1 @@
+pip

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/LICENSE

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/METADATA

@@ -0,0 +1,345 @@
+Metadata-Version: 2.1
+Name: x-wr-timezone
+Version: 2.0.1
+Summary: Repair Google Calendar - This Python module and program makes ICS/iCalendar files using X-WR-TIMEZONE compatible with the RFC 5545 standard.
+Home-page: https://github.com/niccokunzmann/x-wr-timezone
+Author: Nicco Kunzmann
+Author-email: niccokunzmann@rambler.ru
+License: LGPL-3.0-or-later
+Keywords: icalendar
+Platform: UNKNOWN
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Utilities
+Classifier: Intended Audience :: Developers
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Development Status :: 5 - Production/Stable
+License-File: LICENSE
+Requires-Dist: icalendar>=6.1.0
+Requires-Dist: tzdata
+Requires-Dist: click
+
+X-WR-TIMEZONE
+=============
+
+.. image:: https://github.com/niccokunzmann/x-wr-timezone/actions/workflows/tests.yml/badge.svg
+   :target: https://github.com/niccokunzmann/x-wr-timezone/actions/workflows/tests.yml
+   :alt: CI build and test status
+
+.. image:: https://badge.fury.io/py/x-wr-timezone.svg
+   :target: https://pypi.python.org/pypi/x-wr-timezone
+   :alt: Python Package Version on Pypi
+
+.. image:: https://img.shields.io/pypi/dm/x-wr-timezone.svg
+   :target: https://pypi.python.org/pypi/x-wr-timezone#downloads
+   :alt: Downloads from Pypi
+
+.. image:: https://img.shields.io/opencollective/all/open-web-calendar?label=support%20on%20open%20collective
+   :target: https://opencollective.com/open-web-calendar/
+   :alt: Support on Open Collective
+
+
+Some calendar creators such as Google Calendar
+introduce the non-standard ``X-WR-TIMEZONE`` parameter
+to ICS calendar files to change the timezone.
+Strict interpretations according to RFC 5545 ignore the ``X-WR-TIMEZONE``
+parameter.
+This causes the times of the events to differ from those
+which make use of ``X-WR-TIMEZONE``.
+
+This module aims to bridge the gap by converting calendars
+using ``X-WR-TIMEZONE`` to a strict RFC 5545 calendars.
+So, let's put our heads together and solve this problem for everyone!
+
+Some features of the module are:
+
+- Easy install with Python's ``pip``.
+- Command line conversion of calendars.
+- Piping of calendar files with ``wget`` or ``curl``.
+
+Some of the requirements are:
+
+- Calendars without ``X-WR-TIMEZONE`` are kept unchanged.
+- Passing calendars twice to this module does not change them.
+
+Install
+-------
+
+Install using ``pip``:
+
+.. code:: shell
+
+    python3 -m pip install x-wr-timezone
+
+Install with ``apt``:
+
+.. code:: shell
+
+    sudo apt-get install python-x-wr-timezone
+
+Support
+-------
+
+- `Fund with GitHub Sponsors <https://github.com/sponsors/niccokunzmann>`_
+- `Fund on Open Collective <https://opencollective.com/open-web-calendar/>`_
+- `Fund with thanks.dev <https://thanks.dev>`_
+- `Fund on Tidelift <https://tidelift.com/lifter/search/pypi/x-wr-timezone>`_
+
+Command Line Usage
+------------------
+
+You can standardize the calendars using your command line interface.
+The examples assume that ``in.ics`` is a calendar which may use
+``X-WR-TIMEZONE``, whereas ``out.ics`` does not require ``X-WR-TIMEZONE``
+for proper display.
+
+.. code-block:: shell
+
+    cat in.is | x-wr-timezone > out.ics
+    x-wr-timezone in.ics out.ics
+    curl https://example.org/in.ics | x-wr-timezone > out.ics
+    wget -O- https://example.org/in.ics | x-wr-timezone > out.ics
+
+You can get usage help on the command line:
+
+.. code-block:: shell
+
+    x-wr-timezone --help
+
+Python
+------
+
+After you have installed the library, you can import it.
+
+.. code:: python
+
+    import x_wr_timezone
+
+The function ``to_standard()`` converts an `icalendar.Calendar
+<https://icalendar.readthedocs.io/en/latest/api.html#icalendar.cal.Calendar>`_.
+
+.. code:: python
+
+    x_wr_timezone.to_standard(an_icalendar)
+
+Here is a full example which does about as much as this module is supposed to do:
+
+.. code-block:: python
+
+    import icalendar # installed with x_wr_timezone
+    import x_wr_timezone
+
+    with open("in.ics", 'rb') as file:
+        calendar = icalendar.from_ical(file.read())
+    new_calendar = x_wr_timezone.to_standard(calendar)
+    # you could use the new_calendar variable now
+    with open('out.ics', 'wb') as file:
+        file.write(new_calendar.to_ical())
+
+
+``to_standard(calendar, timezone=None)`` has these parameters:
+
+- ``calendar`` is the ``icalendar.Calendar`` object.
+- ``timezone`` is an optional time zone. By default, the time zone in
+  ``calendar['X-WR-TIMEZONE']`` is used to check if the calendar needs
+  changing.
+  When ``timezone`` is not ``None`` however, ``calendar['X-WR-TIMEZONE']``
+  will not be tested and it is assumed that the ``calendar`` should be
+  changed as if ``calendar['X-WR-TIMEZONE']`` had the value of ``timezone``.
+  This does not add or change the value of ``calendar['X-WR-TIMEZONE']``.
+  You would need to do that yourself.
+  ``timezone`` can be a string like ``"UTC"`` or ``"Europe/Berlin"`` or
+  a ``pytz.timezone`` or something that ``datetime`` accepts as a time zone..
+- Return value: The ``calendar`` argument is not modified at all. The calendar
+  returned has the attributes and subcomponents of the ``calendar`` only
+  changed and copied where needed to return the proper value. As such,
+  the returned calendar might be identical to the one passed to the
+  function as the ``calendar`` argument. Keep that in mind if you modify the
+  return value.
+
+
+Development
+-----------
+
+1. Clone the `repository <https://github.com/niccokunzmann/x-wr-timezone>`_ or its fork and ``cd x-wr-timezone``.
+2. Optional: Install virtualenv and Python3 and create a virtual environment:
+
+   .. code-block:: shell
+
+       pip install virtualenv
+       virtualenv -p python3 ENV
+       source ENV/bin/activate # you need to do this for each shell
+
+3. Install the packages and this module so it can be edited:
+
+   .. code-block:: shell
+
+       pip install -r test-requirements.txt -e .
+
+4. Run the tests:
+
+   .. code-block:: shell
+
+       pytest
+
+To test all functions:
+
+.. code-block:: shell
+
+    pytest --x-wr-timezone all
+
+Testing with ``tox``
+********************
+
+You can use ``tox`` to test the package in different Python versions.
+
+.. code:: shell
+
+    tox
+
+This tests all the different functionalities:
+
+.. code:: shell
+
+    tox -- --x-wr-timezone all
+
+New Releases
+------------
+
+To release new versions,
+
+1. edit the Changelog Section
+2. edit setup.py, the ``__version__`` variable
+3. create a commit and push it
+4. Wait for `CI tests <https://github.com/niccokunzmann/x-wr-timezone/actions/workflows/tests.yml>`_ to finish the build.
+5. run
+
+   .. code-block:: shell
+
+       python3 setup.py tag_and_deploy
+6. notify the issues about their release
+
+Add/Remove a Python Version
+---------------------------
+
+
+If you need to add or remove a Python version, you need to modify these files:
+
+- ... README.rst in the changelog section
+- ... setup.py
+- ... tox.ini
+- ... tests.yml
+
+Testing
+*******
+
+This project's development is driven by tests.
+Tests assure a consistent interface and less knowledge lost over time.
+If you like to change the code, tests help that nothing breaks in the future.
+They are required in that sense.
+Example code and ics files can be transferred into tests and speed up fixing bugs.
+
+You can view the tests in the `test folder
+<https://github.com/niccokunzmann/x-wr-timezones/tree/main/test>`_.
+If you have a calendar ICS file for which this library does not
+generate the desired output, you can add it to the ``test/calendars``
+folder and write tests for what you expect.
+If you like, `open an issue <https://github.com/niccokunzmann/x-wr-timezone/issues>`_ first, e.g. to discuss the changes and
+how to go about it.
+
+Changelog
+---------
+
+- v2.0.1
+
+  - Reuse the generated timezone component because that takes a long time.
+  - Fix bug where the timezone was not changed in the result if you add the component.
+
+- v2.0.0
+
+  - Add VTIMEZONE component by default to ``x-wr-timezone`` command.
+  - Add ``--no-timezone`` parameter to skip adding the VTIMEZONE component.
+  - Add ``add_timezone_component=False`` parameter to ``to_standard()`` to optionally add a timezone component in the resulting ``icalendar.Calendar``.
+  - Add ``click`` dependency.
+
+- v1.0.2
+
+  - Add support for Python 3.13
+
+- v1.0.1
+
+  - Use `zoneinfo` instead of `pytz`
+  - Test compatibility with `pytz` and `zoneinfo` as argument to `to_standard`
+  - Remove `pytz` as a dependency
+  - Add `tzdata` as a dependency
+  - Add typing
+  - Update Python versions
+
+- v0.0.7
+
+  - Rename master branch to main
+  - Use proper SPDX license ID
+  - Test Python 3.12
+
+- v0.0.6
+
+  - Obsolete Python 3.7
+  - Support Python 3.11
+  - Fix localization issue for pytz when datetime has no timezone
+  - Run tests on GitHub Actions
+  - Require icalendar 5.0.11 for tests
+  - Fix pytz localization issue when dateime is not in UTC and has no time zone.
+
+- v0.0.5
+
+  - Revisit README and CLI and fix spelling mistakes.
+  - Modified behavior to treat events without time zone found in a calendar using the X-WR-TIMEZONE property, see `Pull Request 7 <https://github.com/niccokunzmann/x-wr-timezone/pull/7>`__
+- v0.0.4
+
+  - Test automatic deployment with Gitlab CI.
+- v0.0.3
+
+  - Use ``tzname()`` function of ``datetime`` to test for UTC. This helps support zoneinfo time zones.
+  - Split up visitor class and rename it to walker.
+- v0.0.2
+
+  - Implement the ``timezone`` argument.
+  - Do not modify the value of the ``calendar`` argument and only copy it where needed.
+- v0.0.1
+
+  - Initial release supports DTSTART, DTEND, EXDATE, RDATE, RECURRENCE-ID attributes of events.
+  - Command line interface as ``x-wr-timezone``.
+
+Security Policy
+---------------
+
+We have a `Security Policy <https://github.com/niccokunzmann/x-wr-timezone/security/policy>`__ in place.
+
+Related Work
+------------
+
+This module was reated beause of these issues:
+
+- `icalendar#343 <https://github.com/collective/icalendar/issues/343>`__
+- `python-recurring-ical-events#71 <https://github.com/niccokunzmann/python-recurring-ical-events/issues/71>`__
+
+Related Software
+----------------
+
+This module uses the ``icalendar`` library for parsing calendars.
+This library is used by ``python-recurring-ical-events``
+to get events at specific dates.
+
+License
+-------
+
+This software is licensed under LGPLv3, see the LICENSE file.
+
+

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/RECORD

@@ -0,0 +1,11 @@
+../../../../../../../Library/Caches/com.apple.python/Users/hyungiahn/Documents/code/syn-chat-bot/.venv/lib/python3.9/site-packages/x_wr_timezone.cpython-39.pyc,,
+../../../bin/x-wr-timezone,sha256=4_ZNWLl1XuaWisIjXQfw0Rv4uj0cQY6-_Hw4-t9Hemo,258
+x_wr_timezone-2.0.1.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
+x_wr_timezone-2.0.1.dist-info/LICENSE,sha256=46mU2C5kSwOnkqkw9XQAJlhBL2JAf1_uCD8lVcXyMRg,7652
+x_wr_timezone-2.0.1.dist-info/METADATA,sha256=PPFsJIs3aSI1en_3HcRNl1uYJWCFzB0BDEckNk5tJFU,10669
+x_wr_timezone-2.0.1.dist-info/RECORD,,
+x_wr_timezone-2.0.1.dist-info/WHEEL,sha256=tZoeGjtWxWRfdplE7E3d45VPlLNQnvbKiYnx7gwAy8A,92
+x_wr_timezone-2.0.1.dist-info/entry_points.txt,sha256=cxpRLqTaOwI6Z1E9rcQ9hV9w-VXAg--s8tKIwfBR3wc,52
+x_wr_timezone-2.0.1.dist-info/top_level.txt,sha256=4MahgANH6X4qFRCde-3V__4gFNI8ucc_JEHzanndZEo,14
+x_wr_timezone-2.0.1.dist-info/zip-safe,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
+x_wr_timezone.py,sha256=dyUlBHTklelLAK5Hkf6X3vKWrkNCkgQhUoWiWHEU4bA,8569

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: bdist_wheel (0.45.1)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+x-wr-timezone = x_wr_timezone:main

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/top_level.txt

@@ -0,0 +1 @@
+x_wr_timezone

.venv/lib/python3.9/site-packages/x_wr_timezone-2.0.1.dist-info/zip-safe

@@ -0,0 +1 @@
+